[
https://issues.apache.org/jira/browse/SPARK-22117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SuYan updated SPARK-22117:
--------------------------
Description:
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...
So may use the current epoch when in callling the resourceOffer, so the running
task will use the latest epoch?
was:
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
> 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...
> So 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
