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

Needs better logging for timeout/failures

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Legacy/Observability
    • Labels:
      None

      Description

      When read was failed due to timeout, Cassandra reports in logs "Timeout; reveived 1 of 3 responses". Same information is passed to clients.

      But this information is not enoght to get list of slow nodes.

      Better to have detailed message in debug log:
      "Timeout; reveived 1 of 4 responses. Requested but not responded node: [<ip1>, <ip2>], Failed nodes: [<ip3>]"

      I implemented such behavior by patching ReadCallback, AbstractWriteResponseHandler, DatacenterSyncWriteResponseHandler and WriteResponseHandler. It handles all cases except Paxos.

      But I want to implement solid solution that handle all cases in same way.

      But before I will start I want to know: are there any objections against such logging?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Fuud Fuud
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: