[jira] [Commented] (CASSANDRA-15352) Replica failure propagation to coordinator and client

["Benedict Elliott Smith (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-15352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958984#comment-16958984 ] 

Benedict Elliott Smith commented on CASSANDRA-15352:
----------------------------------------------------

We should consider implementing CASSANDRA-15221 alongside this?

> Replica failure propagation to coordinator and client
> -----------------------------------------------------
>
>                 Key: CASSANDRA-15352
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15352
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Messaging/Internode
>            Reporter: Alex Petrov
>            Priority: Normal
>
> We should add early reporting of replica-side errors, since currently we just time-out requests. On normal read-write path this is not that important, but this is a protocol change we will need to improve cheap quorums for transient replication. This might have potential positive impact for regular read-write path, since we’ll be aborting queries early instead of timing them out. Can be useful for failing / going away nodes (which is also one of the changes we’re planning to implement). 
> We do have means for propagating error both in client protocol through <reasonmap> and in internode through FAILURE_RSP, which is true and we do not have to extend the protocol to implement this change, but this is still a change in protocol behavior, since we’ll be sending a message where we would usually silently timeout.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org