Hi Everyone,
We are running a causal cluster on kubernetes with persistent volumes, it has been stable for a while at this point but we recently had one of the neo4j pods restart. One of the core members is now failing to start with the following logs:
Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@1ad926d3' was successfully initialized, but failed to start. Please see the attached cause exception "File version does not match header version. Expected: 0 but found: 204". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@1ad926d3' was successfully initialized, but failed to start. Please see the attached cause exception "File version does not match header version. Expected: 0 but found: 204".
org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@1ad926d3' was successfully initialized, but failed to start. Please see the attached cause exception "File version does not match header version. Expected: 0 but found: 204".
at org.neo4j.server.exception.ServerStartupErrors.translateToServerStartupError(ServerStartupErrors.java:45)
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:187)
at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:124)
at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:91)
at com.neo4j.server.enterprise.CommercialEntryPoint.main(CommercialEntryPoint.java:22)
Does anyone have any ideas how to best attempt to recover this node, without having to reseed that member?
Thank you!
