-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S01E01: How to upgrade from RabbitMQ 3.7 to 3.8? #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
gerhard
commented
Jan 6, 2020
•
edited
Loading
edited
- Proposed by @dlresende via rabbitmq/tgir#2
- Hosted by @gerhardlazu
- Published on: 2020-01-31
How to upgrade RabbitMQ 3.7 to 3.8 in prod? Proposed by @dlresende via #2 [#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
gerhard
changed the title
How to upgrade RabbitMQ 3.7 to 3.8 in prod? 2020-01-31
How to upgrade from RabbitMQ 3.7 to 3.8 in prod? 2020-01-31
Jan 6, 2020
gerhard
changed the title
How to upgrade from RabbitMQ 3.7 to 3.8 in prod? 2020-01-31
How to upgrade from RabbitMQ 3.7 to 3.8 in prod?
Jan 6, 2020
gerhard
changed the title
How to upgrade from RabbitMQ 3.7 to 3.8 in prod?
How to upgrade from RabbitMQ 3.7 to 3.8 in prod? - 2020-01-31
Jan 6, 2020
gerhard
changed the title
How to upgrade from RabbitMQ 3.7 to 3.8 in prod? - 2020-01-31
How to upgrade from RabbitMQ 3.7 to 3.8? - 2020-01-31
Jan 6, 2020
gerhard
changed the title
How to upgrade from RabbitMQ 3.7 to 3.8? - 2020-01-31
S01E01 How to upgrade from RabbitMQ 3.7 to 3.8?
Jan 6, 2020
gerhard
changed the title
S01E01 How to upgrade from RabbitMQ 3.7 to 3.8?
S01E01: How to upgrade from RabbitMQ 3.7 to 3.8?
Jan 17, 2020
[#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
[#170545354] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
We want to start with backlog & focus on upgrading the cluster while consumers are making progress on draining the queues. Ideally, we would like to see queues with very little message backlog by the time we finish upgrading all nodes. Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
To reproduce, start a broker in one session by running: make 3-nodes-production-rmq1-server And run the following command in a different session: make 3-nodes-production-rmq1-backlog PerfTest crashes with the following exception within 10 seconds: /usr/local/bin/docker run --rm --interactive --tty \ --hostname tgir-s01e01-rmq1-backlog \ --name tgir-s01e01-rmq1-backlog \ --network tgir-s01e01 \ pivotalrabbitmq/perf-test:2.10.0-ubuntu \ --auto-delete false \ --confirm 100 \ --confirm-timeout 10 \ --consumers 0 \ --flag persistent \ --pmessages 1000 \ --producers 1 \ --queue-args 'x-max-length=1000' \ --queue-pattern 'tgir-s01e01-rmq1-q%d' \ --queue-pattern-from 1 \ --queue-pattern-to 2000 \ --servers-startup-timeout 60 \ --size 1000 \ --type 'fanout' \ --uri "amqp://guest:guest@tgir-s01e01-rmq1:5672/%2f" id: test-102849-029, starting producer #0 id: test-102849-029, starting producer #0, channel #0 id: test-102849-029, time: 7.178s, sent: 0.14 msg/s, confirmed: 0 msg/s, nacked: 0 msg/s, min/median/75th/95th/99th confirm latency: 0/0/0/0/0 ?s test stopped (Error in producer) id: test-102849-029, sending rate avg: 4.9 msg/s id: test-102849-029, receiving rate avg: 0 msg/s Exception in thread "AMQP Connection 172.26.0.2:5672" java.util.concurrent.RejectedExecutionException: Task com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable@394d1b4f rejected from java.util.concurrent.ThreadPoolExecutor@1314c64d[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2055) at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825) at java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1355) at java.base/java.util.concurrent.Executors$DelegatedExecutorService.execute(Executors.java:687) at com.rabbitmq.client.impl.ConsumerWorkService.addWork(ConsumerWorkService.java:81) at com.rabbitmq.client.impl.ConsumerDispatcher.execute(ConsumerDispatcher.java:214) at com.rabbitmq.client.impl.ConsumerDispatcher.handleShutdownSignal(ConsumerDispatcher.java:173) at com.rabbitmq.client.impl.ChannelN.broadcastShutdownSignal(ChannelN.java:283) at com.rabbitmq.client.impl.ChannelN.finishProcessShutdownSignal(ChannelN.java:301) at com.rabbitmq.client.impl.ChannelN.processShutdownSignal(ChannelN.java:317) at com.rabbitmq.client.impl.ChannelManager$1.run(ChannelManager.java:117) at com.rabbitmq.client.impl.ChannelManager.handleSignal(ChannelManager.java:121) at com.rabbitmq.client.impl.AMQConnection.finishShutdown(AMQConnection.java:982) at com.rabbitmq.client.impl.AMQConnection.shutdown(AMQConnection.java:956) at com.rabbitmq.client.impl.AMQConnection.handleFailure(AMQConnection.java:759) at com.rabbitmq.client.impl.AMQConnection.access$400(AMQConnection.java:48) at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:654) at java.base/java.lang.Thread.run(Thread.java:834) [#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
[#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
[#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
[#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Disable publisher confirms, publish 5 msg/s/producer to backfill quicker [#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
rabbitmq/rabbitmq-perf-test#236 [#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
[#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
They are quick to deploy & upgrade and only depend on the gcloud CLI - no K8S, BOSH, Ansible, Terraform etc. Another nice feature is that they can sustain production loads with no degradation, not even NAT penalty, as observed when using Docker's bridged network, the default in K8S 🤔 Adding DNS would be nice, as would better memory & disk limits for RabbitMQ nodes + clustering. [#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
[#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
[#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Need to edit & upload the video, then add the outline before this can be finished. [#170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Closes #2 [finishes #170544206] Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.