[
https://issues.apache.org/jira/browse/HBASE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147534#comment-13147534
]
Ted Yu commented on HBASE-4748:
-------------------------------
Here is relevant master log:
{code}
2011-11-10 17:04:22,495 INFO org.apache.hadoop.hbase.master.MasterFileSystem:
Log folder hdfs://linux76:9000/hbase/.logs/linux76,60020,1320924692314 belongs
to an existing region server
2011-11-10 17:04:22,497 INFO org.apache.hadoop.hbase.master.MasterFileSystem:
Log folder hdfs://linux76:9000/hbase/.logs/linux76,60020,1320924852399 belongs
to an existing region server
2011-11-10 17:04:22,497 INFO org.apache.hadoop.hbase.master.MasterFileSystem:
No logs to split
...
2011-11-10 17:04:36,018 DEBUG org.apache.hadoop.hbase.catalog.CatalogTracker:
new .META. server: linux76,60020,1320924159959 isn't valid. Cached .META.
server: null
2011-11-10 17:04:36,021 INFO org.apache.hadoop.hbase.catalog.CatalogTracker:
Retrying
org.apache.hadoop.hbase.NotAllMetaRegionsOnlineException: Timed out (100ms)
at
org.apache.hadoop.hbase.catalog.CatalogTracker.waitForMeta(CatalogTracker.java:449)
at
org.apache.hadoop.hbase.catalog.CatalogTracker.waitForMeta(CatalogTracker.java:413)
at
org.apache.hadoop.hbase.master.HMaster.assignRootAndMeta(HMaster.java:563)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:485)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:322)
at java.lang.Thread.run(Thread.java:619)
{code}
I think NotAllMetaRegionsOnlineException should be handled by
HMaster.finishInitialization(). Upon catching NotAllMetaRegionsOnlineException
we can call the following in a loop:
{code}
this.fileSystemManager.
splitLogAfterStartup(this.serverManager.getOnlineServers().keySet());
// Make sure root and meta assigned before proceeding.
assignRootAndMeta(status);
{code}
> 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
>
> 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
