[
https://issues.apache.org/jira/browse/CASSANDRA-17810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985999#comment-17985999
]
Christoph Schnepf commented on CASSANDRA-17810:
-----------------------------------------------
Hi,
I'm currently facing this issue on a cluster running 4.1.9. Is there a chance
to backport this change to 4.1?
> Revise timeout handling on queries triggering timeout introduced by
> CASSANDRA-7392
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-17810
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17810
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 5.0-alpha1, 5.0
>
>
> In situations where a replica times out with the code introduced in
> CASSANDRA-7392, they drop the timed-out query on the floor without notifying
> the coordinator; this doesn't become apparent coordinator-side until we go to
> serialize the response. While the results of this (i.e. missed data) should
> mostly be fixed by short read protection on repeat requests, the coordinator
> can in some cases throw an exception like {{IllegalStateException:
> UnfilteredRowIterator for keyspace.table has an open RT bound as its last
> item}} which is decidedly unfriendly.
> We should introduce a specific exception to allow replicas to notify a
> coordinator something has timed out and been dropped on the floor so the
> coordinator can appropriately handle that scenario and abort the query at
> that time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
