hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy
Date Sat, 09 Jun 2012 00:43:23 GMT

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

Siddharth Seth updated MAPREDUCE-3921:
--------------------------------------

       Fix Version/s:     (was: 0.23.2)
    Target Version/s: 0.23.3, 2.0.1-alpha
              Status: Patch Available  (was: Open)

Submitting to jenkins.

Minor stuff
In TaskAttemptImpl, createJobCounterUpdateEventTAKilled - SLOTS_MILLIS_MAPS shouldn't be updated
if a task_attempt is transitioning from SUCCEEDED to FAILED.
Some minor formatting changes required in RMContainerAllocator (spacing in the for loop).
Also the warnings in the same class.
Otherwise, lgtm.

Bobby, the patch doesn't apply to the 23 branch. Has a dependency on MAPREDUCE-3958. Do you
want to pull that in to 23 as well ?

                
> MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3921
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3921
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Bikas Saha
>         Attachments: MAPREDUCE-3921-1.patch, MAPREDUCE-3921-3.patch, MAPREDUCE-3921-4.patch,
MAPREDUCE-3921-5.patch, MAPREDUCE-3921-6.patch, MAPREDUCE-3921-7.patch, MAPREDUCE-3921-9.patch,
MAPREDUCE-3921-branch-0.23.patch, MAPREDUCE-3921-branch-0.23.patch, MAPREDUCE-3921-branch-0.23.patch,
MAPREDUCE-3921.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message