[
https://issues.apache.org/jira/browse/CASSANDRA-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176707#comment-14176707
]
Sylvain Lebresne commented on CASSANDRA-7886:
---------------------------------------------
bq. I am pretty sure that I was using the standard CQL client in my test. It
showed me the new error code I added.
First, what do you call "the standard CQL client"? Second, what I'm saying is
that the patch adds a new exception code (in {{ExceptionCode.java}}) which
*will* be sent to client (by {{ErrorMessage.java}}) and this new exception code
is *not* specified by the current protocol specification. Some clients might
end up handling unknown exception code reasonably well and that's probably what
you saw in your test, but that doesn't change the fact that we shouldn't send
unspecified stuff if we can help it.
> 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
> Assignee: Christian Spriegel
> Priority: Minor
> Fix For: 3.0
>
> Attachments: 7886_v1.txt
>
>
> *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)
