[jira] [Updated] (MAPREDUCE-3441) NodeManager should identify failed disks becoming good back again
[ https://issues.apache.org/jira/browse/MAPREDUCE-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3441: --- Issue Type: Bug (was: Sub-task) Parent: (was: MAPREDUCE-3121) > NodeManager should identify failed disks becoming good back again > - > > Key: MAPREDUCE-3441 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3441 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: nodemanager >Reporter: Ravi Gummadi > > MAPREDUCE-3121 makes NodeManager identify disk failures. But once a disk goes > down, it is marked as failed forever. To reuse that disk (after it becomes > good), NodeManager needs restart. This JIRA is to improve NodeManager to > reuse good disks(which could be bad some time back). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3441) NodeManager should identify failed disks becoming good back again
[ https://issues.apache.org/jira/browse/MAPREDUCE-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3441: --- Issue Type: Sub-task (was: Improvement) Parent: MAPREDUCE-3121 > NodeManager should identify failed disks becoming good back again > - > > Key: MAPREDUCE-3441 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3441 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Ravi Gummadi > > MAPREDUCE-3121 makes NodeManager identify disk failures. But once a disk goes > down, it is marked as failed forever. To reuse that disk (after it becomes > good), NodeManager needs restart. This JIRA is to improve NodeManager to > reuse good disks(which could be bad some time back). -- 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
[jira] [Updated] (MAPREDUCE-3441) NodeManager should identify failed disks becoming good back again
[ https://issues.apache.org/jira/browse/MAPREDUCE-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3441: --- Component/s: mrv2 Summary: NodeManager should identify failed disks becoming good back again (was: Make NodeManager identify the failed disks becoming goodno) May be we don't need to restart the whole NM. If the returning disk is cleaned up and reinitialized separately, that should be enough I guess. > NodeManager should identify failed disks becoming good back again > - > > Key: MAPREDUCE-3441 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3441 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Ravi Gummadi > > MAPREDUCE-3121 makes NodeManager identify disk failures. But once a disk goes > down, it is marked as failed forever. To reuse that disk (after it becomes > good), NodeManager needs restart. This JIRA is to improve NodeManager to > reuse good disks(which could be bad some time back). -- 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
