[
https://issues.apache.org/jira/browse/CASSANDRA-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407251#comment-13407251
]
Sylvain Lebresne commented on CASSANDRA-4414:
---------------------------------------------
I haven't checked but maybe thrift will gentle enough to allow adding optional
fields to the exceptions, which would be my preferred option. But yes, that is
one of the reason why I've targeted to 1.2, but don't take it at face value,
it's not definitive.
> 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
