[
https://issues.apache.org/jira/browse/HBASE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148271#comment-13148271
]
ramkrishna.s.vasudevan commented on HBASE-4748:
-----------------------------------------------
@Ted
{code}
} catch (NotAllMetaRegionsOnlineException namroe) {
+ metaExceptions++;
+ regionsAssigned = 0;
+ LOG.debug("Meta regions offline, seen " + metaExceptions + "
exceptions");
+ }
{code}
but the internal code inside assignRootandMeta() is already catching the
NotAllMetaRegionsOnlineException. Inside verifyMetaRegionLocation()
{code}
try {
connection = waitForMetaServerConnection(timeout);
} catch (NotAllMetaRegionsOnlineException e) {
// Pass
}
{code}
and waitforMeta()
{code}
try {
if (waitForMeta(100) != null) break;
} catch (NotAllMetaRegionsOnlineException e) {
LOG.info("Retrying", e);
}
{code}
is also doing the same thing. So the NotAllMetaRegionsOnlineException will
never come to finishInitialization
and the flow will carry on as it was doing earlier. Correct me if am wrong.
> Race between creating recovered edits for META and master assigning ROOT and
> META.
> ----------------------------------------------------------------------------------
>
> Key: HBASE-4748
> URL: https://issues.apache.org/jira/browse/HBASE-4748
> Project: HBase
> Issue Type: Bug
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Attachments: 4748-v2.txt, 4748.txt
>
>
> 1. Start a cluster.
> 2. Alter a table
> 3. Restart the master using ./hbase-daemon.sh restart master
> 4. Kill the RS after master restarts.
> 5. Start RS again.
> 6. No table operations can be performed on the table that was altered but
> admin.listTables() is able to list the altered table.
--
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
