[jira] Updated: (HDFS-1125) Removing a datanode (failed or decommissioned) should not require a namenode restart
[ https://issues.apache.org/jira/browse/HDFS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-1125: --- Fix Version/s: 0.22.0 This really needs to get fixed for 0.22 . This a huge issue as it makes it difficult to building monitoring tools for alerting purposes. > Removing a datanode (failed or decommissioned) should not require a namenode > restart > > > Key: HDFS-1125 > URL: https://issues.apache.org/jira/browse/HDFS-1125 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node >Affects Versions: 0.20.2 >Reporter: Alex Loddengaard >Priority: Minor > Fix For: 0.22.0 > > > I've heard of several Hadoop users using dfsadmin -report to monitor the > number of dead nodes, and alert if that number is not 0. This mechanism > tends to work pretty well, except when a node is decommissioned or fails, > because then the namenode requires a restart for said node to be entirely > removed from HDFS. More details here: > http://markmail.org/search/?q=decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode#query:decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode+page:1+mid:7gwqwdkobgfuszb4+state:results > Removal from the exclude file and a refresh should get rid of the dead node. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HDFS-1125) Removing a datanode (failed or decommissioned) should not require a namenode restart
[ https://issues.apache.org/jira/browse/HDFS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-1125: --- Priority: Blocker (was: Minor) > Removing a datanode (failed or decommissioned) should not require a namenode > restart > > > Key: HDFS-1125 > URL: https://issues.apache.org/jira/browse/HDFS-1125 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node >Affects Versions: 0.20.2 >Reporter: Alex Loddengaard >Priority: Blocker > Fix For: 0.22.0 > > > I've heard of several Hadoop users using dfsadmin -report to monitor the > number of dead nodes, and alert if that number is not 0. This mechanism > tends to work pretty well, except when a node is decommissioned or fails, > because then the namenode requires a restart for said node to be entirely > removed from HDFS. More details here: > http://markmail.org/search/?q=decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode#query:decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode+page:1+mid:7gwqwdkobgfuszb4+state:results > Removal from the exclude file and a refresh should get rid of the dead node. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HDFS-1125) Removing a datanode (failed or decommissioned) should not require a namenode restart
[ https://issues.apache.org/jira/browse/HDFS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nigel Daley updated HDFS-1125: -- Priority: Critical (was: Blocker) Fix Version/s: (was: 0.22.0) Issue Type: Improvement (was: Bug) At this point I don't see how this 6 month old unassigned issue is a blocker for 0.22. I also think this is an improvement, not a bug. Removing from 0.22 blocker list. > Removing a datanode (failed or decommissioned) should not require a namenode > restart > > > Key: HDFS-1125 > URL: https://issues.apache.org/jira/browse/HDFS-1125 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Affects Versions: 0.20.2 >Reporter: Alex Loddengaard >Priority: Critical > > I've heard of several Hadoop users using dfsadmin -report to monitor the > number of dead nodes, and alert if that number is not 0. This mechanism > tends to work pretty well, except when a node is decommissioned or fails, > because then the namenode requires a restart for said node to be entirely > removed from HDFS. More details here: > http://markmail.org/search/?q=decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode#query:decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode+page:1+mid:7gwqwdkobgfuszb4+state:results > Removal from the exclude file and a refresh should get rid of the dead node. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] [Updated] (HDFS-1125) Removing a datanode (failed or decommissioned) should not require a namenode restart
[ https://issues.apache.org/jira/browse/HDFS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-1125: --- Priority: Blocker (was: Critical) I'm setting this back to a blocker. > Removing a datanode (failed or decommissioned) should not require a namenode > restart > > > Key: HDFS-1125 > URL: https://issues.apache.org/jira/browse/HDFS-1125 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Affects Versions: 0.20.2 >Reporter: Alex Loddengaard >Priority: Blocker > > I've heard of several Hadoop users using dfsadmin -report to monitor the > number of dead nodes, and alert if that number is not 0. This mechanism > tends to work pretty well, except when a node is decommissioned or fails, > because then the namenode requires a restart for said node to be entirely > removed from HDFS. More details here: > http://markmail.org/search/?q=decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode#query:decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode+page:1+mid:7gwqwdkobgfuszb4+state:results > Removal from the exclude file and a refresh should get rid of the dead node. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HDFS-1125) Removing a datanode (failed or decommissioned) should not require a namenode restart
[ https://issues.apache.org/jira/browse/HDFS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-1125: --- Affects Version/s: 0.20.2 > Removing a datanode (failed or decommissioned) should not require a namenode > restart > > > Key: HDFS-1125 > URL: https://issues.apache.org/jira/browse/HDFS-1125 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node >Affects Versions: 0.20.2 >Reporter: Alex Loddengaard >Priority: Minor > > I've heard of several Hadoop users using dfsadmin -report to monitor the > number of dead nodes, and alert if that number is not 0. This mechanism > tends to work pretty well, except when a node is decommissioned or fails, > because then the namenode requires a restart for said node to be entirely > removed from HDFS. More details here: > http://markmail.org/search/?q=decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode#query:decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode+page:1+mid:7gwqwdkobgfuszb4+state:results > Removal from the exclude file and a refresh should get rid of the dead node. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
