Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Before you begin

  1. Follow the steps in this KB article for connecting to public or private GKE cluster.

  2. Install kubectl and configure kubectl command line access using steps 1 and 2 in Getting thread dump section in the same article (alternatively, see go/cdf-internal-runbook for same instructions in more easily copy-paste-able format).

Updating memory of a pod

  1. Get the name of the pod of interest: kubectl get pods

  2. To check current configuration of pod: kubectl describe pod/<name of pod>

  3. Modify and save the memory in the yaml:  kubectl edit cdapmasters.cdap.cdap.io/<instance-name> -o yaml

  4. Check if the pod restarted successfully: kubectl get pods

For nodes stuck in init:CrashLoopBackoff state

  1. Delete the PV:

    1. Find the name of the PV for the pod we want to restart: kubectl get pvc

    2. Delete the PV: kubectl delete pvc/<pod-pvc-name>

  2. Delete the statefulset:

    1. Find the name of the statefulset for the pod we want to restart: kubectl get statefulset

    2. Delete the statefulset: kubectl delete statefulset/<pod-statefulset-name>

  3. Check if the pod restarted successfully:

    1. kubectl get pods

    2. kubectl describe pod/<updated-pod>

  • No labels