我有两个运行Debian Linux的控制器。 我想在这两个控制器上支持Hot Standby数据库。 在任何给定时间，一个控制器将处于活动状态，而另一控制器将处于活动状态 成为热备用，即如果重新启动/卸下/停止活动控制器，则备用控制器将变为活动控制器。
我希望数据库（neo4j）存在于组成单个群集的两个控制器（即Active和Standby）上。
群集的领导者始终来自活动控制器。
每当活动控制器被卸下/停止时，备用控制器就会变为活动控制器，并且该控制器中的一台核心服务器应成为领导服务器。
每当重新启动活动控制器（例如A）时，备用控制器（例如B）将变为活动状态，并且该控制器中的一台核心服务器应成为领导者，而控制器A变为待机。
首先，我创建了4个核心服务器，每个活动和备用控制器上都有两个核心（总共4个核心）。最后是Neo4j.conf设置。
当同时存在主控制器和备用控制器并且所有4个内核都已启动时，一切正常。 当我做活动控制器时问题就开始了，然后备用的两个核心都变成了“跟随者”，而“领导者”没有仲裁 即将卸任的领导者没有获得足够的选票来成为领导者，因为一位控制器被撤职（夺走了两个核心）。
即使删除了我的活动控制器，如何进行领导者选择？ 有人可以在这里帮我吗？
当活动状态关闭时，这是在备用控制器上登录CORE之一
[SenderService] Failed to connect to: /192.168.56.102:7002. Retrying in 1600 ms
[c.RaftMachine] Failed to get elected. Got votes from: [MemberId{66fce96a}]
[c.RaftMachine] Election started with vote request: Vote.Request from MemberId{705ea752} {term=19, candidate=MemberId{705ea752}, lastAppended=3, lastLogTerm=1} and members: [MemberId{705ea752}, MemberId{70db66c7}, MemberId{66fce96a}, MemberId{b8233ff8}]
[RaftOutbound] No address found for MemberId{70db66c7}, probably because the member has been shut down.
[RaftOutbound] No address found for MemberId{b8233ff8}, probably because the member has been shut down.
[SenderService] Failed to connect to: /192.168.56.102:7003. Retrying in 1600 ms
[c.RaftMachine] Failed to get elected. Got votes from: [MemberId{66fce96a}]
[c.RaftMachine] Election started with vote request: Vote.Request from MemberId{705ea752} {term=20, candidate=MemberId{705ea752}, lastAppended=3, lastLogTerm=1} and members: [MemberId{705ea752}, MemberId{70db66c7}, MemberId{66fce96a}, MemberId{b8233ff8}]
配置文件的一些重要内容
Controller-1：Core-1 IP：端口= 192.168.56.102：5003
causal_clustering.refuse_to_be_leader=true
dbms.mode=CORE
causal_clustering.minimum_core_cluster_size_at_formation=2
causal_clustering.minimum_core_cluster_size_at_runtime=2
causal_clustering.initial_discovery_members=192.168.56.152:5000, 192.168.56.152:5001, 192.168.56.102:5002, 192.168.56.102:5003
causal_clustering.discovery_listen_address=192.168.56.102:5003
causal_clustering.transaction_listen_address=192.168.56.102:6003
causal_clustering.raft_listen_address=192.168.56.102:7003
dbms.connector.bolt.listen_address=192.168.56.102:7690
dbms.connector.http.listen_address=192.168.56.102:7477
dbms.connector.https.listen_address=192.168.56.102:6477
dbms.backup.address=192.168.56.102:6365
dbms.connectors.default_advertised_address=192.168.56.102
Controller-1：Core-2 IP：端口= 192.168.56.102：5002
dbms.mode=CORE
causal_clustering.minimum_core_cluster_size_at_formation=2
causal_clustering.minimum_core_cluster_size_at_runtime=2
causal_clustering.initial_discovery_members=192.168.56.102:5000, 192.168.56.102:5001, 192.168.56.102:5002,192.168.56.102:5003
causal_clustering.discovery_listen_address=192.168.56.102:5002
causal_clustering.transaction_listen_address=192.168.56.102:6002
causal_clustering.raft_listen_address=192.168.56.102:7002
dbms.connector.bolt.listen_address=192.168.56.102:7689
dbms.connector.http.listen_address=192.168.56.102:7476
dbms.connector.https.listen_address=192.168.56.102:6476
dbms.backup.address=192.168.56.102:6364
dbms.connectors.default_advertised_address=192.168.56.102
Controller-2：Core-1 IP：端口= 192.168.56.152：5001
dbms.mode=CORE
causal_clustering.minimum_core_cluster_size_at_formation=2
causal_clustering.minimum_core_cluster_size_at_runtime=2
causal_clustering.initial_discovery_members=192.168.56.152:5000, 192.168.56.152:5001,192.168.56.102:5002,192.168.56.102:5003
causal_clustering.discovery_listen_address=192.168.56.152:5001
causal_clustering.transaction_listen_address=192.168.56.152:6001
causal_clustering.raft_listen_address=192.168.56.152:7001
dbms.connector.bolt.listen_address=192.168.56.152:7688
dbms.connector.http.listen_address=192.168.56.152:7475
dbms.connector.https.listen_address=192.168.56.152:6475
dbms.backup.address=192.168.56.152:6363
dbms.connectors.default_advertised_address=192.168.56.152
Controller-2：Core-2 IP：端口= 192.168.56.152：5000
dbms.mode=CORE
causal_clustering.minimum_core_cluster_size_at_formation=2
causal_clustering.minimum_core_cluster_size_at_runtime=2
causal_clustering.initial_discovery_members=192.168.56.152:5000, 192.168.56.15 2:5001,192.168.56.102:5002,192.168.56.102:5003
causal_clustering.discovery_listen_address=192.168.56.152:5000
causal_clustering.transaction_listen_address=192.168.56.152:6000
causal_clustering.raft_listen_address=192.168.56.152:7000
dbms.connector.bolt.listen_address=192.168.56.152:7687
dbms.connector.http.listen_address=192.168.56.152:7474
dbms.connector.https.listen_address=192.168.56.152:6474
dbms.backup.address=192.168.56.152:6362
dbms.connectors.default_advertised_address=192.168.56.152