Active MQ 版本从 5.5.1 迁移到 5.11.2 [英] Migration of Active MQ version from 5.5.1 to 5.11.2

问题描述

计划将 Active MQ 版本从 5.5.1 迁移到 5.11.2 如何将现有消息从旧版本 (5.5.1) 迁移到新版本 (5.11.2)

Planning to migrate Active MQ version form 5.5.1 to 5.11.2 how to migrate the existing messages from older version(5.5.1) to newer version(5.11.2)

提前致谢.

推荐答案

这里假设您已经处理了从 5.6.0 到 5.11.2 的每个发行说明中提到的任何迁移问题.

This assumes you have already taken care of any migration issues noted in each release note from 5.6.0 to 5.11.2.

基本上有两种方法可以升级/迁移代理.

There are essentially two ways to upgrade/migrate a broker.

1. 只需安装新代理并指出旧(kahaDB)数据库.这将自动升级到新版本.这可能会导致商店升级期间出现一些停机时间(至少在商店中有大量消息的情况下).

1. Simply install the new broker and point out the old (kahaDB) database. This will automatically upgrade to a new version. This may cause some downtime during store upgrade (at least if there are a lot of messages in the store).

同时运行两个并行代理，让旧的淡出".您可以并排设置一个闪亮的新 5.11 代理.这也使得迁移到其他存储类型(JDBC 或 LevelDB)成为可能.这是一个多一点的工作，但会让你的正常运行时间最大化.如果你依赖消息顺序，我不推荐这种方法.

Have two parallell brokers running at once and let the old "fade out". You can setup a shiny new 5.11 broker side by side. This also makes it possible to migrate to other store types (JDBC or LevelDB). It's a little more work but will keep you uptime maximized. If you depend on message order, I would not recommend this method.

1. 设置新代理.
2. 从旧代理中移除 transportConnector，并添加一个从旧到新的网络连接器.
3. 停止旧的，开始新的，开始旧的.
4. 现在，只要所有队列上都有连接的消费者，客户端(使用故障转移，对吗?)将故障转移到新代理，并且来自旧代理的消息将被复制到新代理.
5. 当旧代理上没有更多消息时，将其关闭并卸载.

与所有升级一样，绕过很多版本会降低升级的可靠性.我会尝试对生产副本进行一些试运行升级，以确保一切按计划进行.

As with all upgrades, bypassing a lot of versions will make the upgrade less reliable. I would try some dry run upgrade of a production replica to ensure that everything goes as planned.

这篇关于Active MQ 版本从 5.5.1 迁移到 5.11.2的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！