[
https://issues.apache.org/jira/browse/ACCUMULO-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195497#comment-15195497
]
Keith Turner commented on ACCUMULO-4166:
----------------------------------------
A constraint on the max number of tablet servers involved may also be nice. A
command like the following would limit each tserver to one compaction and only
run compactions on 10 tservers at a time.
{noformat}
compact -t myTable -b p: -e p:~ -m 1 -t 10
{noformat}
> Limit compactions per tserver
> -----------------------------
>
> Key: ACCUMULO-4166
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4166
> Project: Accumulo
> Issue Type: Improvement
> Reporter: Keith Turner
> Fix For: 1.8.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
(v6.3.4#6332)
