[
https://issues.apache.org/jira/browse/HBASE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730681#action_12730681
]
Haijun Cao commented on HBASE-1634:
-----------------------------------
I am on TRUNK. I don't think I have 1638 condition.
BTW, after "fixing" the UI, I try to count TestTable using hbase shell. The
count can't pass region TestTable,0001100543. I scan the content of .META.
table and notice that there is a row that contains only "historian"? I am new
to hbase (about 3 days old), so I really don't know what all this means.
Just wondering, to recover from this, can I manually delete all
"TestTable,0001192603" entries from .META. table? So that it does not stuck
there? Is it safe? Thanks!
Haijun
TestTable,0001100543,124745 column=info:server, timestamp=1247543378892,
value=10.10.30.148:60020
3328532
TestTable,0001100543,124745 column=info:serverstartcode,
timestamp=1247543378892, value=1247543311613
3328532
TestTable,0001192603,124738 column=historian:assignment,
timestamp=1247452778771, value=Region assigned to se
2904014 rver
haijun-linux.projectrialto.com,60020,1247452720744
TestTable,0001192603,124738 column=historian:open, timestamp=1247452781786,
value=Region opened on server : h
2904014 aijun-linux.projectrialto.com
TestTable,0001192603,124738 column=historian:split, timestamp=1247382905910,
value=Region split from: TestTab
2904014 le,0001039817,1247381765576
> UI and shell list throw NPE
> ---------------------------
>
> Key: HBASE-1634
> URL: https://issues.apache.org/jira/browse/HBASE-1634
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.20.0
>
>
> I have a .META. from bryan duxbury that has a row with only historian data.
> List does whole row, not just info, so if only historian entries, a row is
> returned. We then try and get a regioninfo from this row and NPE.
> As to why this happens, jd suggests that since we moved to async historian
> updates, row may have been deleted already. Confirm.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
