You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/01/17 20:19:43 UTC

[jira] Commented: (HBASE-3447) Split parents ending up deployed along with daughters

    [ https://issues.apache.org/jira/browse/HBASE-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982809#action_12982809 ] 

stack commented on HBASE-3447:
------------------------------

Any more in the log from around here?

{code}
logs/HM-haus01.sf.cloudera.com.log:2011-01-16 18:03:26,164 DEBUG oahh.M.handler.ServerShutdownHandler: Offlined and split region usertable,user136857679,1295149082811.9f2822a04028c86813fe71264da5c167.; checking daughter presence
{code}

The RS seems to report fine that the parent if split/offlined:

{code}
logs/RS-haus04.sf.cloudera.com.log:2011-01-16 17:51:44,112 INFO oahh.RS.CompactSplitThread: Region split, META updated, and report to master. Parent=usertable,user136857679,1295149082811.9f2822a04028c86813fe71264da5c167., new regions: usertable,user136857679,1295229096477.ea26a71066b5617d9d8c9a4394209895., usertable,user1372334755,1295229096477.9c05ac3446fd2ff2d0cc0ac78f063867.. Split took 7sec
{code}

... and the master on shutdown processing seems to recognize it as an offlined parent.

Is this the one you figured when we talked on IRC?



> Split parents ending up deployed along with daughters
> -----------------------------------------------------
>
>                 Key: HBASE-3447
>                 URL: https://issues.apache.org/jira/browse/HBASE-3447
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.0
>            Reporter: Todd Lipcon
>            Priority: Blocker
>         Attachments: unknown-region.log
>
>
> Testing rc3 got several regions in this state as reported by hbck:
> ERROR: Region UNKNOWN_REGION on haus02.sf.cloudera.com:57020, key=9f2822a04028c86813fe71264da5c167, not on HDFS or in META but deployed on haus02.sf.cloudera.com:57020
> (this without any injected failures or anything)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.