[ 
https://issues.apache.org/jira/browse/HBASE-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated HBASE-13610:
-----------------------------------
    Attachment: HBASE-13610-0.98.patch

Straightforward backport in all respects.

New unit in TestAdmin2 passes. TestShell passes. Ran new command by hand.

Compatibility report comparing HEAD of 0.98 against 0.98.12 after this change:
{noformat}
Running the Java API Compliance Checker...
using Java 1.7.0_79
reading classes 0.98.12 ...
WARNING: skip "impl" packages (use --keep-internal option to check them)
reading classes 0.98.13-SNAPSHOT ...
WARNING: skip "impl" packages
comparing classes ...
creating compatibility report ...
result: COMPATIBLE
total "Binary" compatibility problems: 0, warnings: 0
total "Source" compatibility problems: 0, warnings: 0
{noformat}

Checked UI changes, looks good. Nice warning when balancing is disabled now.

Not sure why this was deemed intrusive earlier.

> Backport HBASE-13222 (Provide means of non-destructive balancer inspection) 
> to 0.98
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-13610
>                 URL: https://issues.apache.org/jira/browse/HBASE-13610
>             Project: HBase
>          Issue Type: Task
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 0.98.13
>
>         Attachments: HBASE-13610-0.98.patch
>
>
> We have an internal user who wanted a facility like this during a recent 
> upgrade.
> On HBASE-13222 [~elserj] said:
> bq.  I've dropped 0.98 from the fixVersions since the patch ended up being 
> much more intrusive than Nicks initial patch.
> I skimmed the V3 patch 
> (https://issues.apache.org/jira/secure/attachment/12707615/HBASE-13222-v3.patch)
>  and the essential change is an Admin API addition {{public boolean 
> isBalancerOn()}}, and a new shell command, both of which we can do in 0.98 
> minors. Going to port back those parts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to