Neo4j

aguyhasnoname · 06-03-2019

In a Kubernetes cluster on AWS EKS I am deploying a five core causal cluster via a handful of manifests very similar to a helm package and two initContainers, one for apoc plugin install, and a second for @david.allen's restore script built off of a ...

aguyhasnoname · 06-04-2019

Adding these here in case they help anyone else discover this issue. They are the logs of the Core starting, but only if is restarting/updating. ~$ kubectl logs neo4j-4 Changed password for user 'neo4j'. Active database: graph.db Directories in use: ...

aguyhasnoname · 06-04-2019

Also, interestingly, if an edit is made to the statefulSet and the pods are updated they fail to come back up. This makes me think it's not necessarily unclean shutdowns.

aguyhasnoname · 06-04-2019

Thanks for this suggestion. Running the consistency checker on my backup in the instance that just ran the restore initContainer seems to be checking out fine. 2019-06-04 20:16:35.696+0000 INFO [o.n.k.i.s.f.RecordFormatSelector] Selected RecordFormat...

aguyhasnoname · 06-04-2019

Thanks for your reply @david.allen. Agree completely about avoiding the problem to begin with. Considering the bringing the uncleanly shutdown/evicted core back up so it can self-heal/rejoin the cluster I do like your idea. However, implementing it w...

aguyhasnoname · 05-17-2019

Many thanks for the reply. I'm running them all via a kubernetes manifest so not sure how easy it'd be to apply one of those solutions. Thanks though!

Neo4j

User Statistics

User Activity

Core server cannot rejoin Causal Cluster after unclean shutdown in Kubernetes

Re: Core server cannot rejoin Causal Cluster after unclean shutdown in Kubernetes

Re: Core server cannot rejoin Causal Cluster after unclean shutdown in Kubernetes

Re: Core server cannot rejoin Causal Cluster after unclean shutdown in Kubernetes

Re: Core server cannot rejoin Causal Cluster after unclean shutdown in Kubernetes

Re: Unable to find transaction 1 in any of my logical logs