Hi, Stack:
You have a point. I checked the non-hbase machine's hbck's result, and it
shows :
Summary:
2418 inconsistencies detected.
Status: INCONSISTENT
That number seems very familiar to me, so I went to the master admin
page, and found:
Total: servers: 6 requests=2783, regions=2417
if we add the root region back in, then essentially the hbck is complaining
every region is bad,
which is not true.
On the other hand, the hbase machine hbck says
0 inconsistencies detected.
Status: OK
that is probably too good to be true too.
I run "hadoop dfs -ls /hbase/table_name | grep region_id" and confirmed that
in both machine,
the region's directory showed up. In both machine, I was running in hdfs
account.
When you say I print more info, does that mean I need to modify the hbck
code ? I might do it later
when I can find some time.
Jimmy.
--------------------------------------------------
From: "Stack" <[email protected]>
Sent: Wednesday, May 25, 2011 10:03 AM
To: <[email protected]>
Subject: Re: hbase hbck error
On Wed, May 25, 2011 at 9:18 AM, Jinsong Hu <[email protected]>
wrote:
I tried several other non-hbase machines that has proper configuration,
sure
enough, all of them complain problems.
This is interesting Jinsong. For sure the configuration was pointed
at the right filesystem. Do you think there could have been a
suppressed error or some such thing remotely querying the filesystem
for the presence of region directories? Can you add in a of
printf'ing to see whats going on in hbck?
Thanks for digging in on this.
St.Ack