如果未启动主人
我们有一个具有共享存储策略的主/从设置。 我们观察到，如果我们在主机下降时启动从属，我们会有以下消息：
AMQ221032: Waiting to become backup node
并且服务器不会实现。
因此，这意味着奴隶要求主人在给定的时间上起来才能进行操作。 这是预期的行为吗？如果主人失望，有没有办法让奴隶在创业公司中实现？
We have a master/slave setup with the shared storage strategy.
We observed that if we start the slave when the master is down, we have the following message:
AMQ221032: Waiting to become backup node
And the server does not become live.
So it means that the slave requires the master to be up at a given time to become operational.
Is this the expected behavior? Is there a way to let the slave become live at startup if the master is down?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
一般而言，您所看到的是不是 使用共享存储的主人/从属的预期行为。如果未启动主机并启动从设备开始，则从属应在共享存储中获取锁并开始。我刚刚使用
交易范围输入示例对此进行了测试，该示例用ActiveMQ Artemis发货，而备份开始时，备份开始时正常。这是我在启动主人启动时启动备份时看到的记录：您看到的行为表明可能已经启动了另一个备份，并且已经在日记帐上获得了备份锁定。很难说提供的信息。
Generally speaking what you're seeing is not the expected behavior for master/slave using shared storage. If the master is not started and the slave is started then the slave should acquire the lock on the shared storage and start. I just tested this out using the
transaction-failoverexample which is shipped with ActiveMQ Artemis and the backup started just fine when the master wasn't started. Here's the logging I saw when starting the backup when the master wasn't started:The behavior you're seeing indicates that perhaps another backup is already started and has acquired the backup lock on the journal. It's hard to say with the information you're provided.