keith-turner opened a new issue, #3178: URL: https://github.com/apache/accumulo/issues/3178
Accumulo currently supports allocating tablets to specific servers using IP addresses and hostnames using certain balancer plugins. This provides a way to dedicate compute resources to specific tables. Another way this could be accomplished is by adding a group option to tablet servers like [scan servers](https://github.com/apache/accumulo/blob/ab8e2f518887a2505cad9dbc02e82197babfc1bd/server/tserver/src/main/java/org/apache/accumulo/tserver/ScanServer.java#L130) have. The group set for a tablet server could then be made available to balancer plugins. Balancer plugins could use this information to assign specific tables or tablets to groups of tablet servers. This feature would be useful for running groups of tablet servers in Kubernetes pods where the IP addresses may not be static. Then tables could be assigned to those different groups giving different tables different qualities of compute resources. It could also be used to simplify the balancer configuration on clusters with fixed ip addresses. An example of of this could work is * on host A run `accumulo tserver -g meta` * on host B run `accumulo tserver -g meta` * on host C run `accumulo tserver` * on host D run `accumulo tserver` After doing the above configure a balancer to assign the accumulo metadata table to group meta. This would result in accumulo metadata tables going to host A or B without having to configure the balancer with specifig information about host A and B. The balancer plugin should assign all other tablets to host C and D. To implement this feature would need to : - Add the `-g` startup option to the tserver - Store the group name in zookeeper for each tserver - Modify the manager to get the group names from zookeeper and pass them to the balancer - Possibly update the accumulo-cluster script to support group names for tservers in the cluster yaml file. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
