[
https://issues.apache.org/jira/browse/ARTEMIS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram closed ARTEMIS-2660.
-----------------------------------
Resolution: Information Provided
Please send questions like to the [ActiveMQ User Mailing
List|http://activemq.apache.org/contact/#mailing].
> Kubernetes Master/Slave Rolling update
> --------------------------------------
>
> Key: ARTEMIS-2660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2660
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.11.0
> Reporter: Yasin Koyuncu
> Priority: Major
>
> Hi,
>
> We've a setup in kubernetes cluster having master/slave with two distinct
> statefulsets for each one of them. This setup is working alright, however
> during rolling updates since the current pods are being terminated and
> replaced by the new deployment, the clients get disconnected for a brief
> moment. This leads ultimately to failure of some of the messages being send
> to the broker.
>
> My question is, has anyone managed to make it work for a master/slave setup
> for rolling update in kubernetes?
>
> Thx,
> Yasin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
