[
https://issues.apache.org/jira/browse/CASSANDRA-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122756#comment-14122756
]
Christian Spriegel edited comment on CASSANDRA-7886 at 9/5/14 10:09 AM:
------------------------------------------------------------------------
[~slebresne]: Customer keep sending in requests. So if cassandra suddenly
decides to make every request wait for 15 sec. (config increased) then we run
out of heap, because requests pile up :-(
As a workaround we can probably decrease the timeout setting, but the behaviour
should be changed imho.
Can we set fixversion to 3.0 already so that this ticket wont be forgotten?
edit: Thanks for the fast response :-)
was (Author: christianmovi):
[~slebresne]: Customer keep sending in requests. So if cassandra suddenly
decides to make every request wait for 15 sec. (config increased) then we run
out of heap, because requests pile up :-(
As a workaround we can probably decrease the timeout setting, but the behaviour
should be changed imho.
Can we set fixversion to 3.0 already so that this ticket wont be forgotten?
> TombstoneOverwhelmingException should not wait for timeout
> ----------------------------------------------------------
>
> Key: CASSANDRA-7886
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7886
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: Tested with Cassandra 2.0.8
> Reporter: Christian Spriegel
> Priority: Minor
>
> *Issue*
> When you have TombstoneOverwhelmingExceptions occuring in queries, this will
> cause the query to be simply dropped on every data-node, but no response is
> sent back to the coordinator. Instead the coordinator waits for the specified
> read_request_timeout_in_ms.
> On the application side this can cause memory issues, since the application
> is waiting for the timeout interval for every request.Therefore, if our
> application runs into TombstoneOverwhelmingExceptions, then (sooner or later)
> our entire application cluster goes down :-(
> *Proposed solution*
> I think the data nodes should send a error message to the coordinator when
> they run into a TombstoneOverwhelmingException. Then the coordinator does not
> have to wait for the timeout-interval.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
