[
https://issues.apache.org/jira/browse/CASSANDRA-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412278#comment-13412278
]
Jonathan Ellis commented on CASSANDRA-4414:
-------------------------------------------
bq. I do think we should break this apart into a separate exception
I still would like to do this in an ideal world but I think our hands might be
tied by the client community... unless we're willing to break everyone who
doesn't add IPE, the optional field is a better approach.
> Ship the exact cause for timeout and unavailable exception back to the client
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-4414
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4414
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Fix For: 1.2
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
