hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8631) Meta Region First Recovery
Date Thu, 30 May 2013 17:23:20 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-8631:
-------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Committed to trunk and 0.95.  Thanks for the patch J and for the reviews lads.
                
> Meta Region First Recovery
> --------------------------
>
>                 Key: HBASE-8631
>                 URL: https://issues.apache.org/jira/browse/HBASE-8631
>             Project: HBase
>          Issue Type: Bug
>          Components: MTTR
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>             Fix For: 0.98.0, 0.95.1
>
>         Attachments: hbase-8631.patch, hbase-8631-v2.patch, hbase-8631-v3.patch, hbase-8631-v4.patch
>
>
> We have a separate wal for meta region. While log splitting logic haven't taken the advantage
of this and splitlogworker still picks a wal file randomly. Imaging if we have multiple region
servers including meta RS fails about the same time while meta wal is recovered last, all
failed regions have to wait meta recovered and then can be online again. 
> The open JIRA is to let splitlogworker to pick a meta wal file firstly and then others.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message