You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Jeffrey Manno (Jira)" <ji...@apache.org> on 2021/09/03 18:43:00 UTC

[jira] [Resolved] (ACCUMULO-4047) TabletBalancer has an implicit requirement for a specific constructor

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

Jeffrey Manno resolved ACCUMULO-4047.
-------------------------------------
    Resolution: Cannot Reproduce

This no longer appears to be an issue after TabletBalancer has moved to become an interface along with several other changes since this ticket was created. I could not reproduce by utilizing ChaoticLoadBalancer, removing all constructors, and then confirming that ChoatLoadBalancer is applied and set properly.

> TabletBalancer has an implicit requirement for a specific constructor
> ---------------------------------------------------------------------
>
>                 Key: ACCUMULO-4047
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4047
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>            Reporter: Josh Elser
>            Priority: Major
>
> TabletBalancers are an extension point designed for non-core-Accumulo devs to implement balancers for a specific purpose.
> As noticed in ACCUMULO-3356, there is an unwritten requirement that any concrete implementations of TabletBalancer have a constructor that takes a String object as an argument. This wouldn't be so bad but it's a silent failure that falls back to the DefaultBalancer (that's why we haven't noticed ACCUMULO-3356 for ages).
> TabletBalancer already has an init method which could be used. There are lots of other ways it could be addressed. At a minimum, this should be prominently documented.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)