You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/16 21:07:58 UTC
[jira] [Resolved] (HBASE-4988) MetaServer crash cause all splitting
regionserver abort
[ https://issues.apache.org/jira/browse/HBASE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-4988.
--------------------------
Resolution: Won't Fix
Patch for 0.90.
Won't have this issue in 2.0.
Reopen if issue in more modern hbase.
> MetaServer crash cause all splitting regionserver abort
> -------------------------------------------------------
>
> Key: HBASE-4988
> URL: https://issues.apache.org/jira/browse/HBASE-4988
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.6
> Reporter: chunhui shen
> Assignee: chunhui shen
> Attachments: hbase-4988v1.patch
>
>
> If metaserver crash now,
> All the splitting regionserver will abort theirself.
> Becasue the code
> {code}
> this.journal.add(JournalEntry.PONR);
> MetaEditor.offlineParentInMeta(server.getCatalogTracker(),
> this.parent.getRegionInfo(), a.getRegionInfo(), b.getRegionInfo());
> {code}
> If the JournalEntry is PONR, split's roll back will abort itselef.
> It is terrible in huge putting environment when metaserver crash
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)