accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Loss (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3480) GroupBalancer improvements
Date Thu, 22 Jan 2015 17:07:37 GMT

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

Brian Loss commented on ACCUMULO-3480:
--------------------------------------

The numbers are looking better.  Now, my big test takes about 20s and here are the numbers:
{noformat}
balance                            88% (17000ms)
    balanceExtraExpected           67% (12900ms)
        ColumnKeySet.removeAll     66% (12650ms)  (this is the Guava table's ColumnKeySet)
{noformat}

> GroupBalancer improvements
> --------------------------
>
>                 Key: ACCUMULO-3480
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3480
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.7.0
>
>         Attachments: ACCUMULO-3480-1.patch, ACCUMULO-3480-2.patch, ACCUMULO-3480-3.patch
>
>
> [~bfloss] made the following comment on ACCUMULO-3439
> bq. The balance method in GroupBalancer does nothing if there are any incoming migrations.
You probably want to check the incoming migrations and only bail out if any of those migrations
are for the specific table that the GroupBalancer is managing.
> I chatted w/ Brian and he also mentioned that the group balancer should record time at
the end, and not the beginning.  



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

Mime
View raw message