[
https://issues.apache.org/jira/browse/CASSANDRA-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091565#comment-13091565
]
Hudson commented on CASSANDRA-3079:
-----------------------------------
Integrated in Cassandra #1048 (See
[https://builds.apache.org/job/Cassandra/1048/])
Add timeouts to client request schedulers
patch by Stu Hood; reviewed by Melvin Wang for CASSANDRA-3079
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1161983
Files :
* /cassandra/trunk/CHANGES.txt
*
/cassandra/trunk/src/java/org/apache/cassandra/scheduler/IRequestScheduler.java
* /cassandra/trunk/src/java/org/apache/cassandra/scheduler/NoScheduler.java
*
/cassandra/trunk/src/java/org/apache/cassandra/scheduler/RoundRobinScheduler.java
* /cassandra/trunk/src/java/org/apache/cassandra/scheduler/WeightedQueue.java
* /cassandra/trunk/src/java/org/apache/cassandra/thrift/CassandraServer.java
> Allow the client request scheduler to throw Timeouts
> ----------------------------------------------------
>
> Key: CASSANDRA-3079
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3079
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 0001-Add-timeouts-to-request-scheduling.txt,
> 0002-Fix-try-finally-nesting-for-scheduling.txt
>
>
> The RoundRobinScheduler prioritizes threads by allowing them to queue on a
> SynchronousQueue per scheduling bucket. These queues currently do not use
> timeouts, and we observed a cascading case where client retries caused the
> scheduler queues to fill such that latency was way above the client timeout.
> Allowing the IRequestScheduler.queue method to throw a (per-call
> configurable) timeout, we can avoid this cascading.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
