[
https://issues.apache.org/jira/browse/SPARK-25295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612337#comment-16612337
]
Stavros Kontopoulos commented on SPARK-25295:
---------------------------------------------
guys I started working on a short fix.
> Pod names conflicts in client mode, if previous submission was not a clean
> shutdown.
> ------------------------------------------------------------------------------------
>
> Key: SPARK-25295
> URL: https://issues.apache.org/jira/browse/SPARK-25295
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
> Affects Versions: 2.4.0
> Reporter: Prashant Sharma
> Priority: Major
>
> If the previous job was killed somehow, by disconnecting the client. It
> leaves behind the executor pods named spark-exec-#, which cause naming
> conflicts and failures for the next job submission.
> io.fabric8.kubernetes.client.KubernetesClientException: Failure executing:
> POST at: https://<ip>:6443/api/v1/namespaces/default/pods. Message: pods
> "spark-exec-4" already exists. Received status: Status(apiVersion=v1,
> code=409, details=StatusDetails(causes=[], group=null, kind=pods,
> name=spark-exec-4, retryAfterSeconds=null, uid=null,
> additionalProperties={}), kind=Status, message=pods "spark-exec-4" already
> exists, metadata=ListMeta(resourceVersion=null, selfLink=null,
> additionalProperties={}), reason=AlreadyExists, status=Failure,
> additionalProperties={}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
