You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2014/08/26 00:44:59 UTC
[jira] [Created] (ACCUMULO-3083) capability balancing
Eric Newton created ACCUMULO-3083:
-------------------------------------
Summary: 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)