[
https://issues.apache.org/jira/browse/HBASE-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-3403:
-------------------------
Attachment: 3403-v2.txt
Made Todd suggested changes as well as handling of the possible scenario he
describes. The fixup code was copied from 0.20. In 0.20, it was not possible
to get into the state Todd postulates above but in 0.90, when fixup is done in
shutdown handler and not in the 'catalogJanitor', it could happen. I added
test that manufactures the postulated condition and we seem to be doing right
thing.
> Region orphaned after failure during split
> ------------------------------------------
>
> Key: HBASE-3403
> URL: https://issues.apache.org/jira/browse/HBASE-3403
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.0
> Reporter: Todd Lipcon
> Priority: Blocker
> Fix For: 0.90.0
>
> Attachments: 3403-v2.txt, 3403.txt, broken-split.txt,
> hbck-fix-missing-in-meta.txt, master-logs.txt.gz
>
>
> ERROR: Region
> hdfs://haus01.sf.cloudera.com:11020/hbase-normal/usertable/2ad8df700eea55f70e02ea89178a65a2
> on HDFS, but not listed in META or deployed on any region server.
> ERROR: Found inconsistency in table usertable
> Not sure how I got into this state, will look through logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
