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

Posted to issues@spark.apache.org by "SuYan (JIRA)" <ji...@apache.org> on 2017/09/25 11:49:00 UTC

[jira] [Created] (SPARK-22117) TasksetManager echo not change after MapoutTracker epoch changed

SuYan created SPARK-22117:
-----------------------------

             Summary: 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


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





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org