Re: Configuring two activemqs on docker as primary and secondary
Did the input you got from the Docker forum give you an answer that works
for you? If not, keep asking them further questions.
To me, without knowing all that much about Docker, the second option sounds
pretty straightforward on the ActiveMQ side; you'd have two config files,
one for activemq-0 with a network connector to activemq-1, and one for
activemq-1 with a network connector to activemq-0. But if the Docker
aspects of the solution aren't clear or that's not the path you want to go
down, keep asking questions on the Docker forum.
On Tue, Oct 30, 2018, 1:02 AM abhilash128 <abhilash.kyatham@xxxxxxxxx>
> Thanks for your input guys,
> I posted this question on docker discussion forum as well. I got below
> inputs :
> 1.Your best bet would be to change the file in a new docker image. Without
> being able to do that you could use a volume and mount in your changes.
> I’m sure (most of) the configuration can be set by environment variables.
> Have you looked into this?
> 2.One other option would be to use a StatefulSet since their pod identity
> predictable. rabbitmq-0 could be primary with rabbitmq-1 could be
> Sent from: