[
https://issues.apache.org/jira/browse/HBASE-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977989#action_12977989
]
Todd Lipcon commented on HBASE-3403:
------------------------------------
+ // Turn off the meta scanner so it don't remove parent on us.
+ cluster.getMaster().catalogJanitorSwitch(false);
Is this a potential issue? ie the catalog janitor shouldn't remove the parent
if the daughters aren't ready yet, should it? Or is this just for the
simulation done in the test?
- naming-wise, can we use "setCatalogJanitorEnabled(false)" just like our other
accessors? Also .onOff() -> setEnabled()?
- Does this change introduce a new bug? Consider the following scenario:
1. Region A exists
2. Region A splits to B and C, A is marked offline
3. B and C both open just fine
4. B splits to E and F, successfully
5. server crashes
When we process the server shutdown, we end up re-creating B.
> 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.
