[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-07-02 Thread Zhijie Shen (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhijie Shen updated MAPREDUCE-5900:
---

   Resolution: Fixed
Fix Version/s: 2.5.0
   Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2. Thanks Mayank for the patch and Wangda for 
review!

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: trunk, 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Fix For: 2.5.0
>
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch, 
> MAPREDUCE-5900-trunk-2.patch, MAPREDUCE-5900-trunk-3.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-07-02 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Affects Version/s: trunk

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: trunk, 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch, 
> MAPREDUCE-5900-trunk-2.patch, MAPREDUCE-5900-trunk-3.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-07-02 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Status: Patch Available  (was: Open)

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1, trunk
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch, 
> MAPREDUCE-5900-trunk-2.patch, MAPREDUCE-5900-trunk-3.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-07-02 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Attachment: MAPREDUCE-5900-trunk-3.patch

Thanks [~zjshen] for the review.
Update Comments.

Thanks,
Mayank

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch, 
> MAPREDUCE-5900-trunk-2.patch, MAPREDUCE-5900-trunk-3.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-07-02 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Status: Open  (was: Patch Available)

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch, 
> MAPREDUCE-5900-trunk-2.patch, MAPREDUCE-5900-trunk-3.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-28 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Status: Patch Available  (was: Open)

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch, 
> MAPREDUCE-5900-trunk-2.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-28 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Attachment: MAPREDUCE-5900-trunk-2.patch

Attaching trunk patch

Thanks,
Mayank

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch, 
> MAPREDUCE-5900-trunk-2.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-28 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Status: Open  (was: Patch Available)

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-28 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Attachment: MAPREDUCE-5900-branch-241-2.patch

Copied the testcase from MAPREDUCE-5848 and made little changes to make it work 
for 2.4.1 branch.

Thanks  Subramaniam Krishnan for the patch for MAPREDUCE-5848

Thanks,
Mayank

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, 
> MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-22 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Status: Patch Available  (was: Open)

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, MAPREDUCE-5900-trunk-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-22 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Status: Open  (was: Patch Available)

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, MAPREDUCE-5900-trunk-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-22 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Attachment: MAPREDUCE-5900-trunk-1.patch

Attaching trunk patch

Previous patch is for 2.4.1

Thanks,
Mayank

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch, MAPREDUCE-5900-trunk-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-21 Thread Vinod Kumar Vavilapalli (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kumar Vavilapalli updated MAPREDUCE-5900:
---

Target Version/s: 2.4.1
   Fix Version/s: (was: 2.4.1)
  (was: trunk)

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-21 Thread Vinod Kumar Vavilapalli (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kumar Vavilapalli updated MAPREDUCE-5900:
---

Issue Type: Sub-task  (was: Bug)
Parent: MAPREDUCE-4584

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Attachments: MAPREDUCE-5900-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-21 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Description: 
We have Added preemption exit code needs to be incorporated
MR needs to recognize the special exit code value of -102 and interpret it as a 
container being killed instead of a container failure.

  was:
When YARN reports a completed container to the MR AM, it always interprets it 
as a failure.  This can lead to a job failing because too many of its tasks 
failed, when in fact they only failed because the scheduler preempted them.

MR needs to recognize the special exit code value of -102 and interpret it as a 
container being killed instead of a container failure.


> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Fix For: trunk, 2.4.1
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-21 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Attachment: MAPREDUCE-5900-1.patch

Attaching patch.

Thanks,
Mayank

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Fix For: trunk, 2.4.1
>
> Attachments: MAPREDUCE-5900-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-21 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Status: Patch Available  (was: Open)

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Fix For: trunk, 2.4.1
>
> Attachments: MAPREDUCE-5900-1.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-21 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Affects Version/s: (was: 2.0.2-alpha)
   2.4.1

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Fix For: trunk, 2.4.1
>
>
> When YARN reports a completed container to the MR AM, it always interprets it 
> as a failure.  This can lead to a job failing because too many of its tasks 
> failed, when in fact they only failed because the scheduler preempted them.
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-21 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Fix Version/s: (was: 2.1.0-beta)
   2.4.1
   trunk

> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.4.1
>Reporter: Mayank Bansal
>Assignee: Mayank Bansal
> Fix For: trunk, 2.4.1
>
>
> When YARN reports a completed container to the MR AM, it always interprets it 
> as a failure.  This can lead to a job failing because too many of its tasks 
> failed, when in fact they only failed because the scheduler preempted them.
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

2014-05-21 Thread Mayank Bansal (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mayank Bansal updated MAPREDUCE-5900:
-

Description: 
When YARN reports a completed container to the MR AM, it always interprets it 
as a failure.  This can lead to a job failing because too many of its tasks 
failed, when in fact they only failed because the scheduler preempted them.

MR needs to recognize the special exit code value of -102 and interpret it as a 
container being killed instead of a container failure.

  was:
When YARN reports a completed container to the MR AM, it always interprets it 
as a failure.  This can lead to a job failing because too many of its tasks 
failed, when in fact they only failed because the scheduler preempted them.

MR needs to recognize the special exit code value of -100 and interpret it as a 
container being killed instead of a container failure.


> Container preemption interpreted as task failures and eventually job failures 
> --
>
> Key: MAPREDUCE-5900
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: applicationmaster, mr-am, mrv2
>Affects Versions: 2.0.2-alpha
>Reporter: Mayank Bansal
>Assignee: Sandy Ryza
> Fix For: 2.1.0-beta
>
>
> When YARN reports a completed container to the MR AM, it always interprets it 
> as a failure.  This can lead to a job failing because too many of its tasks 
> failed, when in fact they only failed because the scheduler preempted them.
> MR needs to recognize the special exit code value of -102 and interpret it as 
> a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)