You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2019/04/23 15:02:00 UTC

[jira] [Resolved] (ACCUMULO-4166) Limit compactions per tserver

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

Keith Turner resolved ACCUMULO-4166.
------------------------------------
    Resolution: Duplicate

https://github.com/apache/accumulo/issues/564

> Limit compactions per tserver
> -----------------------------
>
>                 Key: ACCUMULO-4166
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4166
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>            Priority: Major
>             Fix For: 2.0.0
>
>
> For user initiated compactions, I would like to be able to limit the number of threads that run compactions on each tablet server.  My use case is that for Fluo tables I need to periodically compact ranges of a table to garbage collect Fluo transactional data.  However, I would like these compactions to have minimal impact.
> Being able to do the following would be nice, where the {{-m}} options is the max number of compactions to run on any tablet server.
> {noformat}
>    compact -t myTable  -b p: -e p:~  -m 1
> {noformat}
> Thinking the best implementation would be to push this information to the tablet server and let it manage, rather than having the master try to coordinate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)