Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

When a datanode is marked as DEAD by namenode

Highlighted

When a datanode is marked as DEAD by namenode

New Contributor

 

when a datanode is marked as DEAD by namenode, the blocks contained in that dead node becomes under-replicated, right? so will namenode fix that problem right away or will it wait for any period of time. If yes how long will it wait or what property controls the duration.

 

Thanks,

Harish

3 REPLIES 3
Highlighted

Re: when a datanode is marked as DEAD by namenode, the blocks contained in that dead node becomes under-replicated, right? so will namenode fix that problem right away or will it wait for any period of time. If yes, how long will it wait or what property controls the duration.

Contributor

After 10 minutes your node will have dead state and begin replication of data. You can change this parameter if required.

Highlighted

Re: when a datanode is marked as DEAD by namenode, the blocks contained in that dead node becomes under-replicated, right? so will namenode fix that problem right away or will it wait for any period of time. If yes, how long will it wait or what property controls the duration.

New Contributor

Thanks for the response goga_chitashvil. Could you tell me what configuration property holds this value and in which config site xml.

Highlighted

Re: when a datanode is marked as DEAD by namenode, the blocks contained in that dead node becomes under-replicated, right? so will namenode fix that problem right away or will it wait for any period of time. If yes, how long will it wait or what property controls the duration.

Contributor

You need to add it in custom hdfs site:

dfs.namenode.heartbeat.recheck-interval

 

Don't have an account?
Coming from Hortonworks? Activate your account here