cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rodrigo Peinado (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-805) using Integer.MAX_VALUE for executor keepalive time defeats the purpose of the SEDA-like stage divisions
Date Mon, 22 Mar 2010 19:59:27 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847210#action_12847210
] 

Rodrigo Peinado edited comment on CASSANDRA-805 at 3/22/10 7:59 PM:
--------------------------------------------------------------------

Maybe a StageController attached to the Stage that monitors its throughput to do runtime tuning
of the thread pool.

      was (Author: rodrigoap):
    Maybe a StageController attached to the Stage that monitors its throughput to do runtime
tunning of the thread pool.
  
> using Integer.MAX_VALUE for executor keepalive time defeats the purpose of the SEDA-like
stage divisions
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-805
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-805
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 0.7
>
>
> we should allow thread pools to shrink when they have excess capacity

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message