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

Ship the exact cause for timeout and unavailable exception back to the client

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 1.2.0 beta 1
    • Component/s: None
    • Labels:
      None

      Description

      Currently when a client gets a timeout exception, it doesn't know what happened. But sever side we usually know a little more than that. For example, for 99% of the timeouts at CL > ONE, we will have some replica that have acknowlege. I think it could be useful to send that information to the client with the exception. That could help with monitoring, "post-mortem" analysis and debugging.

      Unavailable exceptions could also ship which nodes were alive and which ones where not.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jbellis Jonathan Ellis
                Reporter:
                slebresne Sylvain Lebresne
                Reviewer:
                Sylvain Lebresne
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: