core:
standalone: false
numberOfServers: 2
persistentVolume:
## whether or not persistence is enabled
##
enabled: true
## core server data Persistent Volume mount root path
##
mountPath: /data
## core server data Persistent Volume size
##
size: 250Mi
discoveryService:
type: ClusterIP
annotations: {}
labels: {}
loadBalancerSourceRanges:
# Controls how many services get created. Usually want to over-provision so cores can
# scale up for things like rolling upgrades.
instances: [0, 1]
standaloneOnly: [0]
readReplica:
numberOfServers: 0
I could see that the kubernetes services are created service/discovery-neo4j-neo4j-0, service/discovery-neo4j-neo4j-1 and using the ports 5000/TCP,6000/TCP,7000/TCP,3637/TCP.
The pods pod/neo4j-neo4j-core-0 and pod/neo4j-neo4j-core-1 are not running and waiting with the message 2020-10-31 16:43:19.091+0000 INFO Database 'system' is waiting for a total of 3 core members...
I checked the neo4j conf file of this pod and pasted below...
It's tough to diagnose this, but by chance have you tried deploying multiple times? E.g. why is your service called discovery-neo4j-neo4j-2, was there a discovery-neo4j-neo4j-0 and/or discovery-neo4j-neo4j-1?
Separately, I would increase your number of servers to 3, to give you at least some fault tolerance.
It was a typo of getting pod/neo4j-neo4j-core-0 repeated twice.
Also I increased the numberOfServers to 3 and it all starting working now. Thank you for the suggestion. I marked the reply as Solution