[jira] [Updated] (CASSANDRA-13594) Use an ExecutorService for repair commands instead of new Thread(..).start()

["Marcus Eriksson (JIRA)" <ji...@apache.org>]

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

Marcus Eriksson updated CASSANDRA-13594:
----------------------------------------
    Status: Patch Available  (was: Open)

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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org