Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 22 Feb 2013 12:38:13 +0000 (UTC)
From: "nkeywal (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12623419.1355248859380.323074.1361536693921@arcas>
In-Reply-To: <JIRA.12623419.1355248859380@arcas>
References: <JIRA.12623419.1355248859380@arcas>
Subject: [jira] [Commented] (HBASE-7327) Assignment Timeouts: Remove the
 code from the master
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

nkeywal commented on HBASE-7327:
--------------------------------

[~jxiang]
As we're doing a RPC to the regionserver, we know if the regionserver accepted to request to open or not. So theoretically, either the region server is live so it can update the region status (open successful or not), either the RS is dead, and so we will know this by ZK. So to me, we should not need the TOM.

[~ram_krish]
bq. This may not be the case i feel. The master code processFailOver() may take care of this. 
Yes, it does now. Previously (before HBASE-7407), it was waiting for the TOM.
And now, if I remove it, all the tests are ok.

I'm going to try to write new tests, and I will update the JIRA with them, with a target for commit middle of  next week.
                
> Assignment Timeouts: Remove the code from the master
> ----------------------------------------------------
>
>                 Key: HBASE-7327
>                 URL: https://issues.apache.org/jira/browse/HBASE-7327
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.96.0
>            Reporter: nkeywal
>            Assignee: nkeywal
>         Attachments: 7327.v1.uncomplete.patch, 7327.v2.patch
>
>
> As per HBASE-7247...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira