由于未知的复制策略,Neo4j 2.3.2群集无法启动

由于未知的复制策略,Neo4j 2.3.2群集无法启动,neo4j,Neo4j,升级到2.3.2后,我在启动集群时遇到以下错误 在2.3.2升级中开始获得此功能,neo4j群集无法启动: 2016-01-22 00:54:42.499+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@483013b3' was successfully initialized, but failed t

升级到2.3.2后,我在启动集群时遇到以下错误

在2.3.2升级中开始获得此功能,neo4j群集无法启动:

2016-01-22 00:54:42.499+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@483013b3' was successfully initialized, but failed to start. Please see attached cause exception. Starting Neo4j failed: Component 
Caused by: java.lang.RuntimeException: Unknown replication strategy
at org.neo4j.kernel.ha.transaction.TransactionPropagator$1.getReplicationStrategy(TransactionPropagator.java:115)
at org.neo4j.kernel.ha.transaction.TransactionPropagator.start(TransactionPropagator.java:175)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:452)
... 14 more

此问题似乎与conf/neo4j.properties中ha.tx_push_策略设置的更新有关。使用ha.tx\u push\u strategy=的此设置,会发生错误。当选择更具体的策略时,即ha.tx\u push\u strategy=fixed\u ascending,错误消失,集群正确形成

推送策略确定一个平局断路器,如果tx id相同,则推送到下一个服务器id。新的策略是固定下降和固定上升。虽然此版本的默认值为fixed_descending,但fixed_Suscending是更好的选择,因为选择策略在确定哪个实例被选为下一个主实例时使用升序。因此,在某些情况下,使用fixed_升序可以减少分支数据的机会