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.

namenode in loop forever leasemanager HDFS-4882

Highlighted

namenode in loop forever leasemanager HDFS-4882

Explorer

Hi,

 

Recently, we are facing "namenode's leasemanager from looping forever". It will bring namenode to a state nothing could be executed

other than rolling it.

 

It looks like is a known issue fixed in later versions  as per the ticket https://issues.apache.org/jira/browse/HDFS-4882.

 

We are currently running cdh4.7.1.p0.47, the fix is available in CDH 5.4/apache 2.6.1. In this jira, there is a patch for this issue that has

been tested in later version. I wanted to check if anybody who faced this problem tried to use this patch and compile cdh4.7.1 code and

was the issue fixed?

 

Thanks

RK

5 REPLIES 5

Re: namenode in loop forever leasemanager HDFS-4882

Master Guru
HDFS-4882 has been fixed via a backport in CDH5, from CDH 5.3.0 onwards.

If you are strongly certain thats your issue, you can find the CDH4 hadoop sources to build from at http://archive.cloudera.com/cdh4/cdh/4/hadoop-2.0.0-cdh4.7.1.tar.gz

Note: CDH4 has reached EOM and will receive no further updates/fixes from Cloudera.

Re: namenode in loop forever leasemanager HDFS-4882

Explorer
Harsh,

Error messages in name node and sequence of events happening is making us
believe this could be the issue. Is there any way to check if this is the
issue we are encountering?

Thanks
RK

Re: namenode in loop forever leasemanager HDFS-4882

Master Guru
Per the JIRA that would be the right way to determine the issue. Does seem like you're hitting it if you see the same sequence of events.

Re: namenode in loop forever leasemanager HDFS-4882

Explorer

Thanks Harsh. will let you know how it goes.

Re: namenode in loop forever leasemanager HDFS-4882

Explorer

This issue stopped happening after few hardware upgrades to name node. We thought of spending time in upgrading to cdh5 instead of patch to cdh4.

 

Thanks

RK