[CASSANDRA-4414] Ship the exact cause for timeout and unavailable exception back to the client

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.2.0 beta 1
• Assignee: Jonathan Ellis
• Reporter: Sylvain Lebresne

Authors

Jonathan Ellis

Reviewers

Sylvain Lebresne

• Created: 05/Jul/12 13:24
• Updated: 16/Apr/19 09:32
• Resolved: 13/Jul/12 16:32

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.

Issue Links

• blocks: CASSANDRA-4285 Atomic, eventually-consistent batches