Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 25 Jun 2014 15:56:24 +0000 (UTC)
From: "Jimmy Xiang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12721778.1403039253159.46686.1403711784776@arcas>
In-Reply-To: <JIRA.12721778.1403039253159@arcas>
References: <JIRA.12721778.1403039253159@arcas>
Subject: [jira] [Commented] (HBASE-11370) SSH doesn't need to scan meta if
 not using ZK for assignment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jimmy Xiang commented on HBASE-11370:
-------------------------------------

Good questions.  At first, for the new column sn, if useZK=true, this column is not created. If useZK=false, column sn may have different value than column server. We should have just one column. The reason we have two is for support old clients. During migration (useZK true => false), we need both column sn and server. Probably, it is better to keep the column name "sn" since in the future, we can deprecate column "server".

bq. I think regionAssignments should only be updated for State.Open not for all other cases.
You are right. I meant to update the serverHoldings only (so that it has the same info as the meta for SSH purpose). Let me fix it. 

> SSH doesn't need to scan meta if not using ZK for assignment
> ------------------------------------------------------------
>
>                 Key: HBASE-11370
>                 URL: https://issues.apache.org/jira/browse/HBASE-11370
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>             Fix For: 0.99.0
>
>         Attachments: hbase-11370.patch
>
>
> If we don't use ZK for assignment, the meta content should be the same as that in memory. So we should be able to avoid a meta scan.


--
This message was sent by Atlassian JIRA
(v6.2#6252)