Donc je viens de configurer un environnement HA où j'ai un serveur maître et des instances d'une application utilisant Neo4J embarqué parlant à ce cluster. Tout semble fonctionner si l'état des deux bases de données est le même. Toutefois, si je supprime toutes les données de mon instance esclave et que je les joigne au cluster, les données du cluster doivent se propager dans l'instance esclave. Au lieu de cela, je reçois des erreurs avec ce qui semble être spatial Neo4J. J'ai Neo4J spatial dans mon application, et le plugin du serveur installé dans le côté du serveur maître.Neo4J HA avec Neo4J Spatial
Un exemple de la trace de la pile je reçois:
2015-10-19 15:10:27.096+0000 ERROR [org.neo4j]: Exception when stopping [email protected] org.neo4j.gis.spatial.indexprovider.SpatialIndexImplementation.stop()V java.lang.AbstractMethodError: org.neo4j.gis.spatial.indexprovider.SpatialIndexImplementation.stop()V at org.neo4j.kernel.lifecycle.Lifecycles$1.stop(Lifecycles.java:55) at org.neo4j.kernel.lifecycle.Lifecycle$Delegate.stop(Lifecycle.java:75) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.stop(LifeSupport.java:527) at org.neo4j.kernel.lifecycle.LifeSupport.stop(LifeSupport.java:155) at org.neo4j.kernel.lifecycle.LifeSupport.shutdown(LifeSupport.java:185) at org.neo4j.kernel.NeoStoreDataSource.stop(NeoStoreDataSource.java:1160) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.stop(LifeSupport.java:527) at org.neo4j.kernel.lifecycle.LifeSupport.stop(LifeSupport.java:155) at org.neo4j.kernel.impl.transaction.state.DataSourceManager.stop(DataSourceManager.java:137) at org.neo4j.kernel.ha.cluster.SwitchToSlave.stopServicesAndHandleBranchedStore(SwitchToSlave.java:521) at org.neo4j.kernel.ha.cluster.SwitchToSlave.checkDataConsistency(SwitchToSlave.java:357) at org.neo4j.kernel.ha.cluster.SwitchToSlave.executeConsistencyChecks(SwitchToSlave.java:316) at org.neo4j.kernel.ha.cluster.SwitchToSlave.switchToSlave(SwitchToSlave.java:219) at org.neo4j.kernel.ha.cluster.HighAvailabilityModeSwitcher$2.run(HighAvailabilityModeSwitcher.java:328) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) at org.neo4j.helpers.NamedThreadFactory$2.run(NamedThreadFactory.java:99) 2015-10-19 15:10:27.102+0000 ERROR [org.neo4j]: Lifecycle exception Failed to transition component 'org.neo4j.kernel.lifecy[email protected]' from STOPPED to SHUTTING_DOWN. Please see attached cause exception org.neo4j.kernel.lifecycle.LifecycleException: Failed to transition component '[email protected]' from STOPPED to SHUTTING_DOWN. Please see attached cause exception at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.shutdown(LifeSupport.java:559) at org.neo4j.kernel.lifecycle.LifeSupport.shutdown(LifeSupport.java:200) at org.neo4j.kernel.NeoStoreDataSource.stop(NeoStoreDataSource.java:1160) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.stop(LifeSupport.java:527) at org.neo4j.kernel.lifecycle.LifeSupport.stop(LifeSupport.java:155) at org.neo4j.kernel.impl.transaction.state.DataSourceManager.stop(DataSourceManager.java:137) at org.neo4j.kernel.ha.cluster.SwitchToSlave.stopServicesAndHandleBranchedStore(SwitchToSlave.java:521) at org.neo4j.kernel.ha.cluster.SwitchToSlave.checkDataConsistency(SwitchToSlave.java:357) at org.neo4j.kernel.ha.cluster.SwitchToSlave.executeConsistencyChecks(SwitchToSlave.java:316) at org.neo4j.kernel.ha.cluster.SwitchToSlave.switchToSlave(SwitchToSlave.java:219) at org.neo4j.kernel.ha.cluster.HighAvailabilityModeSwitcher$2.run(HighAvailabilityModeSwitcher.java:328) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) at org.neo4j.helpers.NamedThreadFactory$2.run(NamedThreadFactory.java:99) Caused by: java.lang.AbstractMethodError: org.neo4j.gis.spatial.indexprovider.SpatialIndexImplementation.shutdown()V at org.neo4j.kernel.lifecycle.Lifecycles$1.shutdown(Lifecycles.java:64) at org.neo4j.kernel.lifecycle.Lifecycle$Delegate.shutdown(Lifecycle.java:81) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.shutdown(LifeSupport.java:555) ... 18 more 2015-10-19 15:10:27.103+0000 ERROR [org.neo4j]: Chained lifecycle exception Component '[email protected]' failed to stop. Please see attached cause exception. org.neo4j.kernel.lifecycle.LifecycleException: Component '[email protected]' failed to stop. Please see attached cause exception. at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.stop(LifeSupport.java:532) at org.neo4j.kernel.lifecycle.LifeSupport.stop(LifeSupport.java:155) at org.neo4j.kernel.lifecycle.LifeSupport.shutdown(LifeSupport.java:185) at org.neo4j.kernel.NeoStoreDataSource.stop(NeoStoreDataSource.java:1160) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.stop(LifeSupport.java:527) at org.neo4j.kernel.lifecycle.LifeSupport.stop(LifeSupport.java:155) at org.neo4j.kernel.impl.transaction.state.DataSourceManager.stop(DataSourceManager.java:137) at org.neo4j.kernel.ha.cluster.SwitchToSlave.stopServicesAndHandleBranchedStore(SwitchToSlave.java:521) at org.neo4j.kernel.ha.cluster.SwitchToSlave.checkDataConsistency(SwitchToSlave.java:357) at org.neo4j.kernel.ha.cluster.SwitchToSlave.executeConsistencyChecks(SwitchToSlave.java:316) at org.neo4j.kernel.ha.cluster.SwitchToSlave.switchToSlave(SwitchToSlave.java:219) at org.neo4j.kernel.ha.cluster.HighAvailabilityModeSwitcher$2.run(HighAvailabilityModeSwitcher.java:328) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) at org.neo4j.helpers.NamedThreadFactory$2.run(NamedThreadFactory.java:99) Caused by: java.lang.AbstractMethodError: org.neo4j.gis.spatial.indexprovider.SpatialIndexImplementation.stop()V at org.neo4j.kernel.lifecycle.Lifecycles$1.stop(Lifecycles.java:55) at org.neo4j.kernel.lifecycle.Lifecycle$Delegate.stop(Lifecycle.java:75) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.stop(LifeSupport.java:527) ... 19 more
Est-ce que Neo4j réplication de soutien spatial à travers les instances? Ou plus précisément restaurer l'index spatial à une nouvelle instance vide qui rejoint le cluster pour la première fois?
Cela ressemble à un problème de version. S'il vous plaît assurez-vous que vous êtes la version de Neo4j et l'extension Spatial s'emboîtent. –
Donc j'utilise Neo4J 2.2.5 et la version 0.14-neo4j-2.2.3 pour neo4j spatial. J'ai essayé de mettre 0.14-neo4j-2.2.5 spatial sur le maître et dans mon application mais j'ai la même erreur. C'est seulement quand j'ai une application vide qui rejoint un cluster existant. Si le maître et l'esclave sont vides, ou si le maître et l'esclave ont la même base de données, cela semble fonctionner correctement. – lordmj
Je suppose que cela vaut la peine de déposer un problème avec Neo4j spatial pour cela: https://github.com/neo4j-contrib/spatial/issues/new –