You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by John Lilley <jo...@redpoint.net> on 2014/03/04 13:46:31 UTC
decommissioning a node
Our cluster has a node that reboot randomly. So I've gone to Ambari, decommissioned its HDFS service, stopped all services, and deleted the node from the cluster. I expected and fsck to immediately show under-replicated blocks, but everything comes up fine. How do I tell the cluster that this node is really gone, and it should start replicating the missing blocks?
Thanks
John
RE: decommissioning a node
Posted by John Lilley <jo...@redpoint.net>.
OK, restarting all services now fsck shows under-replication. Was it the NameNode restart?
John
From: John Lilley [mailto:john.lilley@redpoint.net]
Sent: Tuesday, March 04, 2014 5:47 AM
To: user@hadoop.apache.org
Subject: decommissioning a node
Our cluster has a node that reboot randomly. So I've gone to Ambari, decommissioned its HDFS service, stopped all services, and deleted the node from the cluster. I expected and fsck to immediately show under-replicated blocks, but everything comes up fine. How do I tell the cluster that this node is really gone, and it should start replicating the missing blocks?
Thanks
John
RE: decommissioning a node
Posted by John Lilley <jo...@redpoint.net>.
OK, restarting all services now fsck shows under-replication. Was it the NameNode restart?
John
From: John Lilley [mailto:john.lilley@redpoint.net]
Sent: Tuesday, March 04, 2014 5:47 AM
To: user@hadoop.apache.org
Subject: decommissioning a node
Our cluster has a node that reboot randomly. So I've gone to Ambari, decommissioned its HDFS service, stopped all services, and deleted the node from the cluster. I expected and fsck to immediately show under-replicated blocks, but everything comes up fine. How do I tell the cluster that this node is really gone, and it should start replicating the missing blocks?
Thanks
John
RE: decommissioning a node
Posted by John Lilley <jo...@redpoint.net>.
OK, restarting all services now fsck shows under-replication. Was it the NameNode restart?
John
From: John Lilley [mailto:john.lilley@redpoint.net]
Sent: Tuesday, March 04, 2014 5:47 AM
To: user@hadoop.apache.org
Subject: decommissioning a node
Our cluster has a node that reboot randomly. So I've gone to Ambari, decommissioned its HDFS service, stopped all services, and deleted the node from the cluster. I expected and fsck to immediately show under-replicated blocks, but everything comes up fine. How do I tell the cluster that this node is really gone, and it should start replicating the missing blocks?
Thanks
John
RE: decommissioning a node
Posted by John Lilley <jo...@redpoint.net>.
OK, restarting all services now fsck shows under-replication. Was it the NameNode restart?
John
From: John Lilley [mailto:john.lilley@redpoint.net]
Sent: Tuesday, March 04, 2014 5:47 AM
To: user@hadoop.apache.org
Subject: decommissioning a node
Our cluster has a node that reboot randomly. So I've gone to Ambari, decommissioned its HDFS service, stopped all services, and deleted the node from the cluster. I expected and fsck to immediately show under-replicated blocks, but everything comes up fine. How do I tell the cluster that this node is really gone, and it should start replicating the missing blocks?
Thanks
John