Fwd: Spark 2.3.1: k8s driver pods stuck in Initializing state

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Fwd: Spark 2.3.1: k8s driver pods stuck in Initializing state

Christopher Carney

Our driver pods from k8s are getting stuck in initializing state like so:

NAME                                                                                                   READY     STATUS     RESTARTS   AGE

my-pod-fd79926b819d3b34b05250e23347d0e7-driver   0/1       Init:0/1   0          18h


And from kubectl describe pod
Warning  FailedMount  9m (x128 over 4h)  kubelet, 10.47.96.167  Unable to mount volumes for pod "my-pod-fd79926b819d3b34b05250e23347d0e7-driver_spark(1f3aba7b-c10f-11e8-bcec-1292fec79aba)": timeout expired waiting for volumes to attach or mount for pod "spark"/"my-pod-fd79926b819d3b34b05250e23347d0e7-driver". list of unmounted volumes=[spark-init-properties]. list of unattached volumes=[spark-init-properties download-jars-volume download-files-volume spark-token-tfpvp]
  Warning  FailedMount  4m (x153 over 4h)  kubelet, 10.47.96.167  MountVolume.SetUp failed for volume "spark-init-properties" : configmaps "my-pod-fd79926b819d3b34b05250e23347d0e7-init-config" not found

From what I can see in kubectl get configmap the init config map for the driver pod isn't there.

Am I correct in assuming since the configmap isn't being created the driver pod will never start (hence stuck in init)?

Where does the init config map come from?

Why would it not be created?

Thanks,
Christopher Carney


The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.