Josh McKenzie created CASSANDRA-17810:
-----------------------------------------

             Summary: Revise timeout handling on queries triggering timeout 
introduced by CASSANDRA-7392
                 Key: CASSANDRA-17810
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17810
             Project: Cassandra
          Issue Type: Bug
          Components: Messaging/Internode
            Reporter: Josh McKenzie
            Assignee: Josh McKenzie


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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to