Page Comparison

...

Orphaned pod

If Pipeline Studio transitions get pod gets stuck in PENDING state for 5 minutes and then gets deleted, that means the cluster doesn’t have enough resources to schedule the pod.

...

• Stop Dataprep service

  • Get the router service name from kubectl get services

  • Stop Dataprep service using kubectl exec -it <app-fabric-pod-name> --curl -X POST http://<router-service-name>:11015/v3/namespaces/system/apps/dataprep/services/service/stop

• Delete Dataprep deployment to remove the orphaned Dataprep pod

  • Get Dataprep deployment name from kubectl get deployment

  • Delete the deployment using kubectl delete deployment/<dataprep-deployment-name>

• Verify that Dataprep pods don’t show up in kubectl get pods.

• Start Dataprep service: kubectl exec -it <app-fabric-pod-name> -- curl -X POST http://<router-service-name>:11015/v3/namespaces/system/apps/dataprep/services/service/start

• Start Pipeline Studio service: kubectl exec -it <app-fabric-pod-name> -- curl -X POST http://<router-service-name>:11015/v3/namespaces/system/apps/pipeline/services/studio/start

• Verify that all pods and services are up. Check kubectl get pods, kubectl get services.

...