cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Holmberg (Jira)" <>
Subject [jira] [Updated] (CASSANDRA-15352) Replica failure propagation to coordinator and client
Date Wed, 06 Nov 2019 21:55:00 GMT


Adam Holmberg updated CASSANDRA-15352:
    Labels: client-impacting  (was: )

> Replica failure propagation to coordinator and client
> -----------------------------------------------------
>                 Key: CASSANDRA-15352
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Messaging/Internode
>            Reporter: Alex Petrov
>            Priority: Normal
>              Labels: client-impacting
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message