[
https://issues.apache.org/jira/browse/SPARK-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428572#comment-15428572
]
Michael Gummelt commented on SPARK-10401:
-----------------------------------------
This should probably be a separate JIRA, but I'm just adding a note here that
{{--kill}} doesn't seem to kill the job immediately. It invokes Mesos'
{{killTask}} function, which runs a {{docker stop}} for docker images. This
sends a SIGTERM, which seems to be ignored, then sends a SIGKILL after 10s,
which ultimately kills the job. I'd like to find out why the SIGTERM is
ignored.
> spark-submit --unsupervise <job id>
> -----------------------------------
>
> Key: SPARK-10401
> URL: https://issues.apache.org/jira/browse/SPARK-10401
> Project: Spark
> Issue Type: New Feature
> Components: Deploy, Mesos
> Affects Versions: 1.5.0
> Reporter: Alberto Miorin
>
> When I submit a streaming job with the option --supervise to the new mesos
> spark dispatcher, I cannot decommission the job.
> I tried spark-submit --kill, but dispatcher always restarts it.
> Driver and Executors are both Docker containers.
> I think there should be a subcommand spark-submit --unsupervise <job id>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
