You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2012/06/01 15:12:37 UTC

[jira] [Created] (HBASE-6147) SSH and AM.joinCluster leads to region assignment inconsistency in many cases.

ramkrishna.s.vasudevan created HBASE-6147:
---------------------------------------------

             Summary: SSH and AM.joinCluster leads to region assignment inconsistency in many cases.
                 Key: HBASE-6147
                 URL: https://issues.apache.org/jira/browse/HBASE-6147
             Project: HBase
          Issue Type: Bug
    Affects Versions: 0.94.0, 0.92.1
            Reporter: ramkrishna.s.vasudevan
             Fix For: 0.92.2, 0.96.0, 0.94.1


We are facing few issues in the master restart and SSH going in parallel.
Chunhui also suggested that we need to rework on this part.  This JIRA is aimed at solving all such possibilities of region assignment inconsistency

--
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

[jira] [Commented] (HBASE-6147) SSH and AM.joinCluster leads to region assignment inconsistency in many cases.

Posted by "chunhui shen (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/HBASE-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288326#comment-13288326 ] 

chunhui shen commented on HBASE-6147:
-------------------------------------

@ram
We has already found and fix many case for SSH and AM.joinCluster, however it seems exist many other cases all the same.

I first give a suggestion just mentioned in another issue:

Don't assign user regions in SSH until master is initialized, just like doing the following
{code}
process(){
...

if (isCarryingRoot() || isCarryingMeta()){...}

...

    int waitedTimeForMasterInitialized = 0;
    while (!server.isStopped() && !services.isInitialized()) {
      try {
        if (waitedTimeForMasterInitialized == 0) {
          LOG.info("Master is not initialized, waiting...");
        }
        Thread.sleep(100);
        waitedTimeForMasterInitialized += 100;
      } catch (InterruptedException e) {
        Thread.currentThread().interrupt();
        throw new IOException("Interrupted", e);
      }
    }
    if (waitedTimeForMasterInitialized > 0) {
      LOG.info("Recovery time calculation: waiting on master to be initialized took "
          + waitedTimeForMasterInitialized + "ms");
    }
...
}
{code}

In some cases, above code will increase recovery time, if we could fix many cases caused by SSH and AM.joinCluster, I think it is valuable.

Correct me if wrong, thanks.
                
> SSH and AM.joinCluster leads to region assignment inconsistency in many cases.
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-6147
>                 URL: https://issues.apache.org/jira/browse/HBASE-6147
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.1, 0.94.0
>            Reporter: ramkrishna.s.vasudevan
>             Fix For: 0.92.3
>
>
> We are facing few issues in the master restart and SSH going in parallel.
> Chunhui also suggested that we need to rework on this part.  This JIRA is aimed at solving all such possibilities of region assignment inconsistency

--
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