[
https://issues.apache.org/jira/browse/HBASE-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085900#comment-13085900
]
stack commented on HBASE-4203:
------------------------------
Your explanation above helps a lot. Now its clear what you are going on about.
So, how do you distingush between the case where a master comes on line and
the RIT is OPENING but NO exception has happened processing .META... its just a
bit slow and will move to OPENED in a little while... how you distinguish this
case form the pathological case you describe above where we have to wait 30
mins?
Otherwise, yes, this is important one to fix. Good on you Ram.
> While master restarts and if the META region's state is OPENING then master
> cannot assign META until timeout monitor deducts
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4203
> URL: https://issues.apache.org/jira/browse/HBASE-4203
> Project: HBase
> Issue Type: Bug
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
>
> 1. Start Master and 2 RS.
> 2. If any exception happens while opening the META region the state in znode
> will be OPENING.
> 3. If at this point the master restarts then the master will start processing
> the regions in RIT.
> 4. If the znode is found to be in OPENING then master waits for timeout
> monitor to deduct and then call opening.
> 5. If default timeout monitor is configured(1800000 sec/30 min) then it will
> take 30 mins to open the META region itself.
> Soln:
> ====
> Better not to wait for the Timeout monitor period to open catalog tables on
> Master restart
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
