You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2012/08/05 02:53:06 UTC

[jira] [Commented] (HBASE-6283) [region_mover.rb] Add option to exclude list of hosts on unload instead of just assuming the source node.

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

Hudson commented on HBASE-6283:
-------------------------------

Integrated in HBase-0.94-security-on-Hadoop-23 #6 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/6/])
    HBASE-6283 [region_mover.rb] Add option to exclude list of hosts on unload instead of just assuming the source node (Revision 1358449)

     Result = FAILURE
jmhsieh : 
Files : 
* /hbase/branches/0.94/bin/region_mover.rb

                
> [region_mover.rb] Add option to exclude list of hosts on unload instead of just assuming the source node.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6283
>                 URL: https://issues.apache.org/jira/browse/HBASE-6283
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>              Labels: jruby
>             Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1
>
>         Attachments: hbase-6283-v2.patch, hbase-6283.patch
>
>
> Currently, the region_mover.rb script excludes a single host, the host offloading data, as a region move target.  This essentially limits the number of machines that can be shutdown at a time to one.  For larger clusters, it is manageable to have several nodes down at a time and desirable to get this process done more quickly.
> The proposed patch adds an exclude file option, that allows multiple hosts to be excluded as targets.

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