通过JGroups协议在Artemis集群中实现共享存储HA策略的高可用性和故障转移

Question

但是在共享存储中，没有group-name这样的概念。我很困惑。如果我必须通过JGroups中的共享存储来实现高可用性，那么该如何实现。

再次，当我尝试通过提供group-name的复制HA策略执行此操作时，集群已经形成，故障转移正在工作，但我得到警告：

2020-10-02 16:35:21,517 WARN  [org.apache.activemq.artemis.core.client] AMQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=220da24b-049c-11eb-8da6-0050569b585d
2020-10-02 16:35:21,517 WARN  [org.apache.activemq.artemis.core.client] AMQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=220da24b-049c-11eb-8da6-0050569b585d
2020-10-02 16:35:25,350 WARN  [org.apache.activemq.artemis.core.server] AMQ224078: The size of duplicate cache detection (<id_cache-size/>) appears to be too large 20,000. It should be no greater than the number of messages that can be squeezed into confirmation window buffer (<confirmation-window-size/>) 32,000.

Answer 1

正如名称“shared-store”所示，实时代理和备份代理成为一个逻辑对，可以支持高可用性和故障转移，因为它们共享相同的数据存储。因为它们共享相同的数据存储，所以不需要任何类型的group-name配置。这样的选择将是混乱的、多余的，最终是无用的。

JGroups配置（以及cluster-connection)的存在，是因为这两个代理需要相互交换关于各自网络位置的信息，以便在发生故障时live broker可以通知客户端如何连接到备份。

关于网络上重复节点ID的warn消息...在故障转移或故障返回期间，您可能会收到一次或两次警告消息，但如果您看到的次数超过这个次数，那么就有问题了。如果您使用的是shared-store，则表示共享文件系统上的锁有问题。如果你使用复制，那么这表明潜在的配置错误或可能是大脑分裂。