[
https://issues.apache.org/jira/browse/CASSANDRA-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960859#comment-14960859
]
Michael Shuler commented on CASSANDRA-10420:
--------------------------------------------
The best way to troubleshoot this exception is to have some way of reproducing
the error. If you could provide a schema and steps or a test of some sort that
reliably triggers the error you are seeing, that would be super helpful.
That said, first, I would suggest determining if this still occurs in the
latest 2.1.x release (2.1.11 was just released today and will be available
soon). The 2.0 branch is no longer under active development. Have you at least
tried this on the latest 2.0.17 release, and do you still see the same issue?
Lastly, while thrift is still technically supported, less development is spent
on thrift than native cql, and thrift may some day be deprecated in the future.
> Cassandra server should throw meaningfull exception when
> thrift_framed_transport_size_in_mb reached
> ---------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10420
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10420
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Yuan Yao
>
> In cassandra's configuration, we set "thrift_framed_transport_size_in_mb" as
> 15
> When send data large than some threshold max value, java.net.SocketException:
> Connection reset will be thrown out from server. This exception doesn't
> deliver meaningful message. Client side can't detect what's wrong with the
> request
> Please throw out meaningful exception in this case to client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
