You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2017/08/08 16:05:00 UTC
[jira] [Comment Edited] (CASSANDRA-13594) Use an ExecutorService
for repair commands instead of new Thread(..).start()
[ https://issues.apache.org/jira/browse/CASSANDRA-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118439#comment-16118439 ]
Ariel Weisberg edited comment on CASSANDRA-13594 at 8/8/17 4:04 PM:
--------------------------------------------------------------------
I've noticed that short_read test seems to time out quite a bit. I'll run it locally a bit and see if it reproduces. I think I did before with no luck. This issue might only appear in Apache Jenkins.
was (Author: aweisberg):
I've noticed that short_read test seems to time out quite a bit. I'll run it locally a bit and see if it reproduces. I think I did before with no luck. This an issue might only appear in Apache Jenkins.
> 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