hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11626) Region will be closed if user try to move it to an error destination server
Date Mon, 11 Aug 2014 18:00:17 GMT

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

Andrew Purtell commented on HBASE-11626:
----------------------------------------

Sorry for the misunderstanding [~cuijianwei], I agree with your opinion. 

> Region will be closed if user try to move it to an error destination server
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-11626
>                 URL: https://issues.apache.org/jira/browse/HBASE-11626
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.98.4
>            Reporter: cuijianwei
>            Priority: Minor
>
> When moving region to a destination server by hbase shell command, such as:
> {code}
> move '7dbe79eb3a77df085c8546b2ee540e7f', 'localhost,58220,1406806842691'
> {code}
> user could pass an error destination server name, such as misspellinging the server name.
Then, HMaster will close the region firstly and then assign the region to a random server
when finding the destination server is not online, and the region can not serve before it
is online again. Do we need to check the destination server name corresponds to an online
server before closing region?(in HMaster.move(...)) 
> {code}
> ...
> if (destServerName == null || destServerName.length == 0) {
>       ....
>     } else {
>       dest = ServerName.valueOf(Bytes.toString(destServerName));
>       if (dest.equals(regionState.getServerName())) {
>          ...
>       }
>       // ### check the destination sever is online before closing region ###
>     }
> ...
> {code}



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

Mime
View raw message