hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1066) Master should support close/open/reassignment/enable/disable operations on individual regions
Date Tue, 23 Dec 2008 22:32:44 GMT

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

stack commented on HBASE-1066:
------------------------------

{code}
hbase(main):002:0> tools
HBASE SURGERY TOOLS:
 enable_region   Enable a single region. For example,
  
                 hbase> enable_region 'REGIONNAME'
 
 disable_region  Disable a single region

 close_region    Close a single region.  Optionally specify regionserver and
                 whether to 'clean' STARTCODE and SERVER from '.META.' Do not
                 clean the latter if you do not want the region reassigned.
                 Examples:
                 
                 hbase> close_region 'REGIONNAME'
                 hbase> close_region 'REGIONNAME', false
                 hbase> close_region 'REGIONNAME', 'REGIONSERVER_IP:PORT'

Above commands are for 'experts'-only as misuse can damage an install
{code}

> Master should support close/open/reassignment/enable/disable operations on individual
regions
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1066
>                 URL: https://issues.apache.org/jira/browse/HBASE-1066
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: stack
>             Fix For: 0.19.0
>
>         Attachments: 1066-v3.patch, 1066-v4.patch, 1066.patch
>
>
> The master should support close/open/reassignment/enable/disable operations on individual
regions by way of a client API and corresponding shell command(s), and maybe also controls
on the master UI.
>  
> If one region out of 1000s is closed or offline, for example due to transient DFS problems,
currently the whole table must be disabled, then reenabled to trigger reassignment and, hopefully,
successful (re)open of the offline regions. The flurry of compactions this causes can exacerbate
the underlying problem and actually make cluster state worse, as more DFS errors accumulate.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message