[
https://issues.apache.org/jira/browse/SPARK-34389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282825#comment-17282825
]
Ranju commented on SPARK-34389:
-------------------------------
Attila, I had a question on pod Creation timeout if you see this meaningful,
what is the probability of occurring this case where pods are created and not
seen or processed by K8s cluster in this math.max(podAllocationDelay
5,conf.get(KUBERNETES_ALLOCATION_EXECUTOR_TIMEOUT)) period.
I am thinking When K8s cluster will not be able to process, also is it possible
that it is not processing all but creating executor snapshots.
> Spark job on Kubernetes scheduled For Zero or less than minimum number of
> executors and Wait indefinitely under resource starvation
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-34389
> URL: https://issues.apache.org/jira/browse/SPARK-34389
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
> Affects Versions: 3.0.1
> Reporter: Ranju
> Priority: Major
> Attachments: DriverLogs_ExecutorLaunchedLessThanMinExecutor.txt,
> Steps to reproduce.docx
>
>
> In case Cluster does not have sufficient resource (CPU/ Memory ) for minimum
> number of executors , the executors goes in Pending State for indefinite time
> until the resource gets free.
> Suppose, Cluster Configurations are:
> total Memory=204Gi
> used Memory=200Gi
> free memory= 4Gi
> SPARK.EXECUTOR.MEMORY=10G
> SPARK.DYNAMICALLOCTION.MINEXECUTORS=4
> SPARK.DYNAMICALLOCATION.MAXEXECUTORS=8
> Rather, the job should be cancelled if requested number of minimum executors
> are not available at that point of time because of resource unavailability.
> Currently it is doing partial scheduling or no scheduling and waiting
> indefinitely. And the job got stuck.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
