Hi, all
It turned out the name node was not available all the time
while it was busy scanning the file system and reporting errors
and fsck failed to connect to it.
I guess Hbase failed to connect to the name node too at that time.
It took ~10-15 min.
BTW, it looks like yet another design flaw, since the name node
should be able to handle incoming requests and do other things
simultaneously immediately after the startup
Thank you for your cooperation,
M.
On Sun, Apr 19, 2009 at 9:54 PM, Michael Dagaev
<[email protected]> wrote:
> Hi, all
>
> I see a lot of errors like "ERROR org.apache.hadoop.dfs.LeaseManager:
> /hbase/<tablle name>/compaction.dir/943239101/<column
> data>/info/6358397599897724359 not found in lease.paths" in the name
> node log. The hadoop fsck fails to connect to the name node. So, it
> looks like HDFS is ill. Does anybody know how to fix it?
>
> Thank you for your cooperation,
> M.
>
