You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/07/09 07:26:51 UTC
[jira] Assigned: (CASSANDRA-475) sending random data crashes thrift
service
[ https://issues.apache.org/jira/browse/CASSANDRA-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-475:
----------------------------------------
Assignee: Nate McCall (was: Brandon Williams)
looks like we need to set a transport max length and a protocol read length (besides upgrading to a new thrift jar).
unclear if these would prohibit using large binary column values. may need to make them configurable. (would transport length be read length + some overhead? or is transport length just a buffer size that we can leave at some reasonably safe value and is transparent to the rest?)
> sending random data crashes thrift service
> ------------------------------------------
>
> Key: CASSANDRA-475
> URL: https://issues.apache.org/jira/browse/CASSANDRA-475
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Eric Evans
> Assignee: Nate McCall
> Fix For: 0.7
>
>
> Use dd if=/dev/urandom count=1 | nc $host 9160 as a handy recipe for shutting a cassandra instance down.
> Thrift has spoken (see THRIFT-601), but "Don't Do That" is probably an insufficient answer for our users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.