2016-05-11 1 views
3

J'ai essayé de passer de Neo4j 2.3.3 à 3.0.0 en utilisant la fonction d'auto-migration en définissant "dbms.allow_format_migration = true" dans neo4j.conf (comme pour tous les 2.x mises à niveau).Migration de données Neo4j 3.0.0

Malheureusement j'obtenir quelques erreurs sans la possibilité d'accéder à mes données:

2016-05-11 16:32:15.684+0000 INFO Starting... 
2016-05-11 16:32:16.576+0000 INFO Bolt enabled on localhost:7687. 
2016-05-11 16:32:16.724+0000 INFO Starting upgrade of database 
2016-05-11 16:32:16.942+0000 INFO Migrating Indexes (1/3): 
2016-05-11 16:32:16.947+0000 INFO 10% completed 
2016-05-11 16:32:16.948+0000 INFO 20% completed 
2016-05-11 16:32:16.948+0000 INFO 30% completed 
2016-05-11 16:32:16.948+0000 INFO 40% completed 
2016-05-11 16:32:16.948+0000 INFO 50% completed 
2016-05-11 16:32:16.948+0000 INFO 60% completed 
2016-05-11 16:32:16.949+0000 INFO 70% completed 
2016-05-11 16:32:16.949+0000 INFO 80% completed 
2016-05-11 16:32:16.949+0000 INFO 90% completed 
2016-05-11 16:32:16.949+0000 INFO 100% completed 
2016-05-11 16:32:16.949+0000 INFO Migrating Legacy indexes (2/3): 
2016-05-11 16:32:17.616+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component '[email protected]' was successfully initialized, but failed to start. Please see attached cause exception. Starting Neo4j failed: Component '[email protected]' was successfully initialized, but failed to start. Please see attached cause exception. 
org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component '[email protected]' was successfully initialized, but failed to start. Please see attached cause exception. 
     at org.neo4j.server.exception.ServerStartupErrors.translateToServerStartupError(ServerStartupErrors.java:68) 
     at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:217) 
     at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:81) 
     at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:60) 
     at org.neo4j.server.CommunityEntryPoint.main(CommunityEntryPoint.java:28) 
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component '[email protected]' was successfully initialized, but failed to start. Please see attached cause exception. 
     at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:444) 
     at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) 
     at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:189) 
     ... 3 more 
Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.CommunityFacadeFactory, /usr/local/Cellar/neo4j/3.0.0/libexec/data/databases/graph_ito.db 
     at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:144) 
     at org.neo4j.kernel.impl.factory.CommunityFacadeFactory.newFacade(CommunityFacadeFactory.java:40) 
     at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:108) 
     at org.neo4j.server.CommunityNeoServer.lambda$static$32(CommunityNeoServer.java:55) 
     at org.neo4j.server.database.LifecycleManagingDatabase.start(LifecycleManagingDatabase.java:89) 
     at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434) 
     ... 5 more 
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component '[email protected]' was successfully initialized, but failed to start. Please see attached cause exception. 
     at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:444) 
     at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) 
     at org.neo4j.kernel.impl.transaction.state.DataSourceManager.start(DataSourceManager.java:99) 
     at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434) 
     at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) 
     at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:140) 
     ... 10 more 
Caused by: org.neo4j.kernel.impl.storemigration.StoreUpgrader$UnableToUpgradeException: Failure doing migration 
     at org.neo4j.kernel.impl.storemigration.StoreUpgrader.migrateToIsolatedDirectory(StoreUpgrader.java:248) 
     at org.neo4j.kernel.impl.storemigration.StoreUpgrader.migrateIfNeeded(StoreUpgrader.java:132) 
     at org.neo4j.kernel.impl.storemigration.DatabaseMigrator.migrate(DatabaseMigrator.java:98) 
     at org.neo4j.kernel.NeoStoreDataSource.upgradeStore(NeoStoreDataSource.java:554) 
     at org.neo4j.kernel.NeoStoreDataSource.start(NeoStoreDataSource.java:433) 
     at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434) 
     ... 15 more 
Caused by: java.io.IOException: Legacy index migration failed. 
     at org.neo4j.kernel.impl.storemigration.participant.LegacyIndexMigrator.migrateLegacyIndexes(LegacyIndexMigrator.java:127) 
     at org.neo4j.kernel.impl.storemigration.participant.LegacyIndexMigrator.migrate(LegacyIndexMigrator.java:77) 
     at org.neo4j.kernel.impl.storemigration.StoreUpgrader.migrateToIsolatedDirectory(StoreUpgrader.java:240) 
     ... 20 more 
Caused by: org.neo4j.upgrade.lucene.LegacyIndexMigrationException: Migration of legacy index at path:/usr/local/Cellar/neo4j/3.0.0/libexec/data/databases/graph_ito.db/upgrade/index/lucene/node/Hr failed. 
     at org.neo4j.upgrade.lucene.LuceneLegacyIndexUpgrader.upgradeIndexes(LuceneLegacyIndexUpgrader.java:114) 
     at org.neo4j.kernel.impl.storemigration.participant.LegacyIndexMigrator.migrateLegacyIndexes(LegacyIndexMigrator.java:121) 
     ... 22 more 
Caused by: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/usr/local/Cellar/neo4j/3.0.0/libexec/data/databases/graph_ito.db/upgrade/index/lucene/node/Hr/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. 
     at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:299) 
     at org.apache.lucene.index.SegmentInfos$1.doBody(SegmentInfos.java:493) 
     at org.apache.lucene.index.SegmentInfos$1.doBody(SegmentInfos.java:490) 
     at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:731) 
     at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:683) 
     at org.apache.lucene.index.SegmentInfos.readLatestCommit(SegmentInfos.java:490) 
     at org.apache.lucene.index.DirectoryReader.listCommits(DirectoryReader.java:257) 
     at org.apache.lucene.index.IndexUpgrader.upgrade(IndexUpgrader.java:158) 
     at org.apache.lucene.index.IndexUpgrader.main(IndexUpgrader.java:78) 
     at org.neo4j.upgrade.lucene.IndexUpgraderWrapper.upgradeIndex(IndexUpgraderWrapper.java:66) 
     at org.neo4j.upgrade.lucene.LuceneLegacyIndexUpgrader.upgradeIndexes(LuceneLegacyIndexUpgrader.java:109) 
     ... 23 more 

Toute idée?

+0

Il existe un problème neo4j existant (https://github.com/neo4j/neo4j/issues/7042) pour ce qui semble être le même problème, mais il a été fermé par le demandeur sans explication de la façon dont il a été corrigé . Vous souhaiterez peut-être ouvrir un nouveau problème (ou rouvrir l'ancien). – cybersam

Répondre

1

En référence à Neo4j Github Issue, j'ai pu résoudre le problème en supprimant certains fichiers de l'index neo4j.

J'ai dû supprimer les fichiers ${GRAPH_DATABASE}/index/lucene/node/index/segment*, puis redémarrer le serveur neo4j a fait l'affaire pour moi.

Vous pouvez référencer le lien des problèmes de github pour plus de détails. En outre, vous pouvez aussi simplement supprimer les fichiers ont indiqué sur le journal des erreurs ainsi,

causés par: java.lang.IllegalArgumentException: Cet outil a été invoqué pour ne pas supprimer avant de commettre des points, mais les commits suivants étaient trouvé: [DirectoryReader.ReaderCommit (segments_3), DirectoryReader.ReaderCommit (segments_5)]

note: Je migrait de 2.3.0-M03 à 3.0.1.

+0

Je n'ai pas le dossier d'index LAST, mais changeset, node, relation, user et way folder. Mais je vois des fichiers de segments, devrais-je les supprimer dans tous les dossiers? –

+0

@JeroenSteen Je vous recommande d'interroger sur le thread Github que j'ai lié ci-dessus. Je préfère ne pas supprimer ces fichiers car ils ne sont peut-être pas liés au problème. – Runcorn