> [!CAUTION]
> You are currently viewing version 1.2 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.2 (unsupported)</button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/ts-cassandra.html)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/ts-cassandra.html)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/ts-cassandra.html)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/ts-cassandra.html)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/ts-cassandra.html)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/ts-cassandra.html)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/ts-cassandra.html)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/ts-cassandra.html)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/ts-cassandra.html)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/ts-cassandra.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/ts-cassandra.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/ts-cassandra.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/ts-cassandra.md.txt)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/ts-cassandra.md.txt)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/ts-cassandra.md.txt)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/ts-cassandra.md.txt)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/ts-cassandra.md.txt)


This topic discusses steps you can take to troubleshoot and fix problems with the
[Cassandra](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/what-is-hybrid.md.txt#cassandra-datastore) datastore. Cassandra is a
persistent datastore
that runs in the `cassandra` component of the
[hybrid runtime architecture](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/what-is-hybrid.md.txt#about-the-runtime-plane).
See also
[Runtime service configuration overview](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/service-config.md.txt).

## Cassandra pods are stuck in the Pending state

### Symptom


When starting up, the Cassandra pods remain in the **Pending** state.

### Error message


When you use `kubectl` to view the pod states, you see that one or more
Cassandra pods are stuck in the `Pending` state. The
`Pending` state indicates that Kubernetes is unable to schedule the pod
on a node: the pod cannot be created. For example:

    kubectl get pods -n namespace

    NAME                                     READY   STATUS      RESTARTS   AGE
    adah-resources-install-4762w             0/4     Completed   0          10m
    apigee-cassandra-0                       0/1     Pending     0          10m
    ...

### Possible causes


A pod stuck in the Pending state can have multiple causes. For example:

| Cause | Description |
|---|---|
| Insufficient resources | There is not enough CPU or memory available to create the pod. |
| Volume not created | The pod is waiting for the persistent volume to be created. |

### Diagnosis

Use `kubectl`
to describe the pod to determine the source of the error. For example:

```
kubectl -n namespace describe pods pod_name
```


For example:

```
kubectl -n apigee describe pods apigee-cassandra-0
```


The output may show one of these possible problems:

- If the problem is insufficient resources, you will see a Warning message that indicates insufficient CPU or memory.
- If the error message indicates that the pod has unbound immediate PersistentVolumeClaims (PVC), it means the pod is not able to create its [Persistent volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/).

### Resolution

#### Insufficient resources

Modify the Cassandra node pool so that it has sufficient CPU and memory resources.
See [Resizing a node pool](https://cloud.google.com/kubernetes-engine/docs/how-to/node-pools#resizing_a_node_pool) for details.

#### Persistent volume not created

If you determine a persistent volume issue, describe the PersistentVolumeClaim (PVC) to determine
why it is not being created:

1. List the PVCs in the cluster:

   ```
   kubectl -n namespace get pvc

   NAME                                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
   cassandra-data-apigee-cassandra-0   Bound    pvc-b247faae-0a2b-11ea-867b-42010a80006e   10Gi       RWO            standard       15m
   ...
   ```
2. Describe the PVC for the pod that is failing. For example, the following command describes the PVC bound to the pod `apigee-cassandra-0`:

   ```
   kubectl apigee describe pvc cassandra-data-apigee-cassandra-0

   Events:
     Type     Reason              Age                From                         Message
     ---     ---              ---               ---                         ---
     Warning  ProvisioningFailed  3m (x143 over 5h)  persistentvolume-controller  storageclass.storage.k8s.io "apigee-sc" not found
   ```


   Note that in this example, the StorageClass named `apigee-sc` does not exist. To
   resolve this problem, create the missing StorageClass in the cluster, as explained in [Change the default StorageClass](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/cassandra-config.md.txt).


See also [Debugging Pods](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-pod-replication-controller#debugging-pods).

## Cassandra pods are stuck in the CrashLoopBackoff state

### Symptom


When starting up, the Cassandra pods remain in the **CrashLoopBackoff** state.

### Error message


When you use `kubectl` to view the pod states, you see that one or more
Cassandra pods are in the `CrashLoopBackoff` state.
This state indicates that Kubernetes is unable to create the pod. For example:

    kubectl get pods -n namespace

    NAME                                     READY   STATUS            RESTARTS   AGE
    adah-resources-install-4762w             0/4     Completed         0          10m
    apigee-cassandra-0                       0/1     CrashLoopBackoff           0          10m
    ...

### Possible causes


A pod stuck in the `CrashLoopBackoff` state can have multiple causes. For example:

| Cause | Description |
|---|---|
| Data center differs from previous data center | This error indicates that the Cassandra pod has a persistent volume that has data from a previous cluster, and the new pods are not able to join the old cluster. This usually happens when stale persistent volumes persist from the previous Cassandra cluster on the same Kubernetes node. This problem can occur if you delete and recreate Cassandra in the cluster. |
| Truststore directory not found | This error indicates that the Cassandra pod is not able to create a TLS connection. This usually happens when the provided keys and certificates are invalid, missing, or have other issues. |

### Diagnosis


Check the [Cassandra error log](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/cassandra-logs.md.txt) to determine the cause of the problem.

1. List the pods to get the ID of the Cassandra pod that is failing:

   ```
   kubectl get pods -n namespace
   ```
2. Check the failing pod's log:

   ```
   kubectl logs pod_id -n namespace
   ```

### Resolution


Look for the following clues in the pod's log:

#### Data center differs from previous data center


If you see this log message:

```
Cannot start node if snitch's data center (us-east1) differs from previous data center
```

- Check if there are any stale or old PVC in the cluster and delete them.
- If this is a fresh install, delete all the PVCs and re-try the setup. For example:

      kubectl -n namespace get pvc
      kubectl -n namespace delete pvc cassandra-data-apigee-cassandra-0

#### Truststore directory not found


If you see this log message:

```
Caused by: java.io.FileNotFoundException: /apigee/cassandra/ssl/truststore.p12
(No such file or directory)
```


Verify the key and certificates if provided in your overrides file are correct and valid. For
example:

```
cassandra:
  sslRootCAPath: path_to_root_ca-file
  sslCertPath: path-to-tls-cert-file
  sslKeyPath: path-to-tls-key-file
```

## Node failure

### Symptom

When starting up, the Cassandra pods remain in the Pending state. This
problem can indicate an underlying node failure.

### Diagnosis

1. Determine which Cassandra pods are not running:

   ```
   $ kubectl get pods -n your_namespace
       NAME          READY   STATUS    RESTARTS   AGE
       cassandra-0   0/1     Pending   0          13s
       cassandra-1   1/1     Running   0          8d
       cassandra-2   1/1     Running   0          8d
   ```
2. Check the worker nodes. If one is in the **NotReady** state, then that is the node that has failed:

   ```
   kubectl get nodes -n your_namespace
   NAME                          STATUS   ROLES    AGE   VERSION
   ip-10-30-1-190.ec2.internal   Ready    <none>   8d    v1.13.2
   ip-10-30-1-22.ec2.internal    Ready    master   8d    v1.13.2
   ip-10-30-1-36.ec2.internal    NotReady <none>   8d    v1.13.2
   ip-10-30-2-214.ec2.internal   Ready    <none>   8d    v1.13.2
   ip-10-30-2-252.ec2.internal   Ready    <none>   8d    v1.13.2
   ip-10-30-2-47.ec2.internal    Ready    <none>   8d    v1.13.2
   ip-10-30-3-11.ec2.internal    Ready    <none>   8d    v1.13.2
   ip-10-30-3-152.ec2.internal   Ready    <none>   8d    v1.13.2
   ip-10-30-3-5.ec2.internal     Ready    <none>   8d    v1.13.2
   ```

### Resolution

1. Remove the dead Cassandra pod from the cluster.

       $ kubectl exec -it apigee-cassandra-0 -- nodetool status
       $ kubectl exec -it apigee-cassandra-0 -- nodetool removenode deadnode_hostID

2. Remove the VolumeClaim from the dead node to prevent the Cassandra pod from attempting to come up on the dead node because of the affinity:

       kubectl get pvc -n your_namespace
       kubectl delete pvc volumeClaim_name -n your_namespace

3. Update the volume template and create PersistentVolume for the newly added node. The following is an example volume template:

   ```
   apiVersion: v1
   kind: PersistentVolume
   metadata:
     name: cassandra-data-3
   spec:
     capacity:
       storage: 100Gi
     accessModes:
     - ReadWriteOnce
     persistentVolumeReclaimPolicy: Retain
     storageClassName: local-storage
     local:
       path: /apigee/data
     nodeAffinity:
       "required":
         "nodeSelectorTerms":
         - "matchExpressions":
           - "key": "kubernetes.io/hostname"
             "operator": "In"
             "values": ["ip-10-30-1-36.ec2.internal"]
   ```
4. Replace the values with the new hostname/IP and apply the template:

   ```
   kubectl apply -f volume-template.yaml
   ```