[
https://issues.apache.org/jira/browse/HBASE-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978035#action_12978035
]
stack commented on HBASE-3403:
------------------------------
bq. + cluster.getMaster().catalogJanitorSwitch(false);
I added above switch to avoid the unlikely but *perhaps* possible case of
split, compaction in each daughter, and run of catalogjanitor happens before we
get our edit of .META. in. Just trying to do all I can to avoid a debug of
failed tests up on hudson.
NP on changing name of method. Will do.
bq. Does this change introduce a new bug?
Yes. That could happen. Unlikely, but perhaps. Let me spin a new patch.
> 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.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.
