[
https://issues.apache.org/jira/browse/SPARK-33716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun resolved SPARK-33716.
-----------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
Issue resolved by pull request 30693
[https://github.com/apache/spark/pull/30693]
> Decommissioning Race Condition during Pod Snapshot
> --------------------------------------------------
>
> Key: SPARK-33716
> URL: https://issues.apache.org/jira/browse/SPARK-33716
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
> Affects Versions: 3.1.0, 3.2.0
> Reporter: Holden Karau
> Assignee: Holden Karau
> Priority: Major
> Fix For: 3.1.0
>
>
> Some version of Kubernetes may create a deletion timestamp field before
> changing the pod status to terminating, so a decommissioning node may have a
> deletion timestamp and a stage of running. Depending on when the K8s snapshot
> comes back this can cause a race condition with Spark believing the pod has
> been deleted before it has been.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
