accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3083) capability balancing
Date Wed, 27 Aug 2014 23:08:58 GMT

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

Christopher Tubbs commented on ACCUMULO-3083:
---------------------------------------------

This seems similar to ACCUMULO-2841, in that we'd have the ability to specify arbitrary attributes/tags
to Accumulo components. TServers could launch with a tag in their local config and report
that tag when registering in ZK, for use by the balancer.

> capability balancing
> --------------------
>
>                 Key: ACCUMULO-3083
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3083
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>            Reporter: Eric Newton
>
> I was thinking about balancing, in much the way that new container-based (yarn, mesos,
etc) resource managers work.  The existing {{Balancers}} try to keep the number of tablets
even over presumably homogeneous nodes.
> But as clusters age and are improved and expanded in piecemeal, the hardware capabilities
will drift apart.  Some nodes may be capable of handling more load than others.  We may even
want some nodes to have a trivial number of tablets so the data they serve is always cached.
> Tablet servers could advertise an attribute (or several).  Really, it would just be a
name, like {{fatnode}} or {{metaonly}}.  These would then be used by the {{Balancer}} to favor
or ignore tservers for balancing.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message