[
https://issues.apache.org/jira/browse/CASSANDRA-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127479#comment-16127479
]
Joel Knighton commented on CASSANDRA-13594:
-------------------------------------------
This causes a test failure in {{DatabaseDescriptorRefTest}} because of the new
Config class - I've pushed a fix
[here|https://github.com/jkni/cassandra/commit/ec3e7a84e5bae4b6968ee39a39f331fe0f5dd036].
> 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.0
>
> Attachments: 13594.png
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
