Fwd: Spark driver pod scheduling fails on auto scaled node
-- Forwarded message - From: prudhvi ch Date: Thu, Jan 31, 2019, 5:54 PM Subject: Fwd: Spark driver pod scheduling fails on auto scaled node To: -- Forwarded message - From: Prudhvi Chennuru (CONT) Date: Thu, Jan 31, 2019, 5:01 PM Subject: Fwd: Spark driver pod scheduling fails on auto scaled node To: Hi, I am using kubernetes *v 1.11.5* and spark *v 2.3.0*, *calico(daemonset)* as overlay network plugin and kubernetes *cluster auto scalar* feature to autoscale cluster if needed. When the cluster is auto scaling calico pods are scheduling on those nodes but they are not ready for 40 to 50 seconds and the driver and executors pods scheduling on those nodes are failing as calico is not ready. So is there a way to overcome this issue by not scheduling driver and executor pods until *calico* is ready or introduce a delay in driver or executor pods to schedule on the nodes. *I am not using spark operator.* -- *Thanks,* *Prudhvi Chennuru.* -- *Thanks,* *Prudhvi Chennuru.* -- 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.
Fwd: Spark driver pod scheduling fails on auto scaled node
-- Forwarded message - From: Prudhvi Chennuru (CONT) Date: Thu, Jan 31, 2019, 5:01 PM Subject: Fwd: Spark driver pod scheduling fails on auto scaled node To: Hi, I am using kubernetes *v 1.11.5* and spark *v 2.3.0*, *calico(daemonset)* as overlay network plugin and kubernetes *cluster auto scalar* feature to autoscale cluster if needed. When the cluster is auto scaling calico pods are scheduling on those nodes but they are not ready for 40 to 50 seconds and the driver and executors pods scheduling on those nodes are failing as calico is not ready. So is there a way to overcome this issue by not scheduling driver and executor pods until *calico* is ready or introduce a delay in driver or executor pods to schedule on the nodes. *I am not using spark operator.* -- *Thanks,* *Prudhvi Chennuru.* -- *Thanks,* *Prudhvi Chennuru.* -- 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.
Fwd: Spark driver pod scheduling fails on auto scaled node
Hi, I am using kubernetes *v 1.11.5* and spark *v 2.3.0*, *calico(daemonset)* as overlay network plugin and kubernetes *cluster auto scalar* feature to autoscale cluster if needed. When the cluster is auto scaling calico pods are scheduling on those nodes but they are not ready for 40 to 50 seconds and the driver and executors pods scheduling on those nodes are failing as calico is not ready. So is there a way to overcome this issue by not scheduling driver and executor pods until *calico* is ready or introduce a delay in driver or executor pods to schedule on the nodes. *I am not using spark operator.* -- *Thanks,* *Prudhvi Chennuru.* 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.
