[
https://issues.apache.org/jira/browse/HBASE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167008#comment-13167008
]
stack commented on HBASE-4988:
------------------------------
@Chunhui Let me try in 0.92. I don't think we have this issue there, or at
least, the scenario you paint should be harder to produce. If .META. server is
killed, we'll retry a good few times. The .META. should get redeployed
meantime. If it does not, the cluster is sort of hosed anyways? All
regionservers shouldn't go down though.
What you think of the rationale in HBASE-4562 that moves the PONR before the
meta parent offline edit?
You have tried your patch in 0.90? It makes things better for you? Maybe we
should apply for 0.90.6?
> MetaServer crash cause all splitting regionserver abort
> -------------------------------------------------------
>
> Key: HBASE-4988
> URL: https://issues.apache.org/jira/browse/HBASE-4988
> Project: HBase
> Issue Type: Bug
> Reporter: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
