[
https://issues.apache.org/jira/browse/CASSANDRA-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047485#comment-16047485
]
Marcus Eriksson edited comment on CASSANDRA-13594 at 6/13/17 6:25 AM:
----------------------------------------------------------------------
https://github.com/krummas/cassandra/commits/marcuse/limit_repair_command_threads
introduces 2 new config variables:
* {{repair_command_pool_size}} - how many repair commands can we run at the
same time
* {{repair_command_pool_full_strategy}} what do we do when the pool is full
({{queue}} or {{reject}})
was (Author: krummas):
https://github.com/krummas/cassandra/commits/marcuse/limit_repair_command_threads
> Use an ExecutorService for repair commands instead of new Thread(..).start()
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-13594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13594
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 4.x
>
>
> Currently when starting a new repair, we create a new Thread and start it
> immediately
> It would be nice to be able to 1) limit the number of threads and 2) reject
> starting new repair commands if we are already running too many.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
