You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/12/18 15:57:46 UTC
[jira] [Updated] (SPARK-12396) Once driver client registered
successfully,it still retry to connected to master.
[ https://issues.apache.org/jira/browse/SPARK-12396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated SPARK-12396:
------------------------------
Flags: (was: Patch)
Target Version/s: (was: 1.5.2)
Labels: (was: patch)
Fix Version/s: (was: 1.5.2)
[~ZhangMei] please read https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark Don't set target/fix version, and there's no 'patch' type or flag used here. I don't see a pull request.
> Once driver client registered successfully,it still retry to connected to master.
> ---------------------------------------------------------------------------------
>
> Key: SPARK-12396
> URL: https://issues.apache.org/jira/browse/SPARK-12396
> Project: Spark
> Issue Type: Bug
> Components: Deploy
> Affects Versions: 1.5.1, 1.5.2
> Reporter: echo
> Priority: Minor
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> As description in AppClient.scala,Once driver connect to a master successfully, all scheduling work and Futures will be cancelled. But at currently,it still try to connect to master. And it should not happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org