You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:00:25 UTC
[jira] [Updated] (SPARK-22117) TasksetManager echo not change after
MapoutTracker epoch changed
[ https://issues.apache.org/jira/browse/SPARK-22117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-22117:
---------------------------------
Labels: bulk-closed (was: )
> TasksetManager echo not change after MapoutTracker epoch changed
> ----------------------------------------------------------------
>
> Key: SPARK-22117
> URL: https://issues.apache.org/jira/browse/SPARK-22117
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.1.0
> Reporter: SuYan
> Priority: Major
> Labels: bulk-closed
>
> assumes 2 taskset running, A, B
> A throw FetchFailed, and zombie, and MapTracker epoch changed, and will have a new Taskset...
> and assume the lost executor re-registered, and have a new epoch....
> but B epoch will never change, so the running Task succeed on the back-home executor will regard as invaild...
> may use the current epoch when in callling the resourceOffer, so the running task will use the latest epoch?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org