我在Helm中建立了因果群集，并正在尝试实施helm升级。在这种情况下，将添加环境变量。依次重新启动每个节点，并使用旧的neo4j实例进行软终止，并删除容器。然后，在应用更改后启动一个新容器，并为其指定一个新IP地址。
例如，对于一个具有IP 192.168.1.139的旧容器，给新的容器赋予192.168.1.140，在用新IP调出该容器后，我会在其他一个容器的日志中连续获取该容器： / p>
2018-07-24 19:34:43.181+0000 WARN [o.n.c.m.SenderService] Failed to connect to: /192.168.1.139:7000. Retrying in 1600 ms
2018-07-24 19:34:44.783+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:35:04.786+0000 WARN [o.n.c.p.h.HandshakeClientInitializer] Failed handshake after timeout
2018-07-24 19:35:14.785+0000 WARN [o.n.c.m.SenderService] Failed to connect to: /192.168.1.139:7000. Retrying in 1600 ms
2018-07-24 19:35:16.388+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:35:36.390+0000 WARN [o.n.c.p.h.HandshakeClientInitializer] Failed handshake after timeout
地址为.139的节点较早从集群中删除：
2018-07-24 19:19:21.927+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:19:21.928+0000 WARN [o.n.c.m.SenderService] Failed to connect to: /192.168.1.139:7000. Retrying in 100 ms
2018-07-24 19:19:22.030+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:19:22.236+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:19:22.640+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:19:23.443+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:19:24.542+0000 INFO [c.n.c.d.SslHazelcastCoreTopologyService] Core member removed MembershipEvent {member=Member [192.168.1.139]:5000 - 4b302f05-b964-4cfc-a646-e505a6c76aff,type=removed}
2018-07-24 19:19:25.046+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:19:25.047+0000 INFO [c.n.c.d.SslHazelcastCoreTopologyService] Core topology changed {added=[], removed=[{memberId=MemberId{1849ed7b}, info=CoreServerInfo{raftServer=192.168.1.139:7000, catchupServer=192.168.1.139:6000, clientConnectorAddresses=bolt://neo5-core-0.neo5.default.svc.cluster.local:7687,http://neo5-core-0.neo5.default.svc.cluster.local:7474,https://neo5-core-0.neo5.default.svc.cluster.local:7473, groups=[]}}]}
2018-07-24 19:19:25.047+0000 INFO [o.n.c.c.c.m.RaftMembershipManager] Target membership: [MemberId{e1f45e9f}, MemberId{b53b715b}]
2018-07-24 19:19:25.048+0000 INFO [o.n.c.c.c.m.RaftMembershipManager] Not safe to remove member [MemberId{1849ed7b}] because it would reduce the number of voting members below the expected cluster size of 3. Voting members: [MemberId{1849ed7b}, MemberId{e1f45e9f}, MemberId{b53b715b}]
2018-07-24 19:19:26.653+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:19:28.256+0000 INFO [o.n.c.p.h.HandshakeClientInitializer] Scheduling handshake (and timeout) local null remote null
2018-07-24 19:19:32.560+0000 INFO [o.n.c.c.c.RaftMachine] Election timeout triggered
重新启动neo4j实例可解决此问题。有办法解决吗？