Verify the Neo4j cluster formation

You check the pods and services to verify that the core members have managed to form a cluster.

Check that the pods are READY.

Typically, it takes a minute or two after the pods are running. They become READY after they form a cluster. You can watch pod status changes by adding the -w option to the kubectl command (kubectl get pods -w).
```
kubectl get pods
```
```
NAME       READY   STATUS    RESTARTS   AGE
core-1-0   1/1     Running   0          4m51s
core-2-0   1/1     Running   0          4m25s
core-3-0   1/1     Running   0          4m7s
```

You can also check the logs of the pods, for example:

kubectl exec core-2-0 -- tail /logs/neo4j.log

2021-11-05 16:07:13.798+0000 INFO  Connected to core-2-internals.default.svc.cluster.local/10.48.1.4:7000 [raft version:4.0]
2021-11-05 16:07:21.147+0000 INFO  Database 'neo4j' is waiting for a total of 3 core members...
2021-11-05 16:07:31.245+0000 INFO  This instance bootstrapped the 'neo4j' database.
2021-11-05 16:07:31.657+0000 INFO  Sending metrics to CSV file at /metrics
2021-11-05 16:07:31.948+0000 INFO  Bolt enabled on 0.0.0.0:7687.
2021-11-05 16:07:31.954+0000 INFO  Bolt (Routing) enabled on 0.0.0.0:7688.
2021-11-05 16:07:33.852+0000 INFO  Connected to core-3-internals.default.svc.cluster.local/10.48.2.5:7000 [raft version:4.0]
2021-11-05 16:07:33.858+0000 INFO  Connected to core-2-internals.default.svc.cluster.local/10.48.1.4:7000 [raft version:4.0]
2021-11-05 16:07:37.956+0000 INFO  Remote interface available at http://localhost:7474/
2021-11-05 16:07:37.956+0000 INFO  Started.

Check that the services look good:

kubectl get services

NAME            TYPE          CLUSTER-IP      EXTERNAL-IP    PORT(S)                                        AGE
core-1             ClusterIP      10.112.0.8     <none>         7687/TCP,7474/TCP,7473/TCP                                                22h
core-1-admin       ClusterIP      10.112.6.162   <none>         6362/TCP,7687/TCP,7474/TCP,7473/TCP                                       22h
core-1-internals   ClusterIP      None           <none>         6362/TCP,7687/TCP,7474/TCP,7473/TCP,7688/TCP,5000/TCP,7000/TCP,6000/TCP   22h
core-2             ClusterIP      10.112.8.77    <none>         7687/TCP,7474/TCP,7473/TCP                                                22h
core-2-admin       ClusterIP      10.112.9.168   <none>         6362/TCP,7687/TCP,7474/TCP,7473/TCP                                       22h
core-2-internals   ClusterIP      None           <none>         6362/TCP,7687/TCP,7474/TCP,7473/TCP,7688/TCP,5000/TCP,7000/TCP,6000/TCP   22h
core-3             ClusterIP      10.112.8.68    <none>         7687/TCP,7474/TCP,7473/TCP                                                22h
core-3-admin       ClusterIP      10.112.15.3    <none>         6362/TCP,7687/TCP,7474/TCP,7473/TCP                                       22h
core-3-internals   ClusterIP      None           <none>         6362/TCP,7687/TCP,7474/TCP,7473/TCP,7688/TCP,5000/TCP,7000/TCP,6000/TCP   22h
kubernetes         ClusterIP      10.112.0.1     <none>         443/TCP                                                                   134d

For more information about the Neo4j services, see Access a Neo4j cluster.

Was this page helpful?