You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/12/14 10:09:00 UTC

[jira] [Updated] (SPARK-33716) Decommissioning Race Condition during Pod Snapshot

     [ https://issues.apache.org/jira/browse/SPARK-33716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun updated SPARK-33716:
----------------------------------
    Issue Type: Bug  (was: Improvement)

> 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
>
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org