[
https://issues.apache.org/jira/browse/CASSANDRA-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990714#comment-12990714
]
Stu Hood commented on CASSANDRA-2109:
-------------------------------------
> We should most likely catch the IOError and throw a special error to client
I think this is the case where a client thread decides to do a local read,
which will perform the read in the client thread, rather than in the stages.
Honestly, I'd prefer to remove this special casing, rather than letting the
crash-onliness leak into the client threads and then needing to wrap it.
Opened CASSANDRA-2110
> Improve default window size for DES
> -----------------------------------
>
> Key: CASSANDRA-2109
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2109
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stu Hood
> Priority: Minor
> Labels: des
> Fix For: 0.8
>
>
> The window size for DES is currently hardcoded at 100 requests. A larger
> window means that it takes longer to react to a suddenly slow node, but that
> you have a smoother transition for scores.
> An example of bad behaviour: with a window of size 100, we saw a case with a
> failing node where if enough requests could be answered quickly out of cache
> or bloomfilters, the window might be momentarily filled with 10 ms requests,
> pushing out requests that had to go disk and took 10 seconds.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
