Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-15352

Replica failure propagation to coordinator and client

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Triage Needed
    • Normal
    • Resolution: Unresolved
    • None
    • Messaging/Internode
    • None
    • All
    • Clients

    Description

      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 rapid write protection 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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ifesdjeen Alex Petrov
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated: