Cassandra-cli doesn't use framed transport by default
-----------------------------------------------------
Key: CASSANDRA-1290
URL: https://issues.apache.org/jira/browse/CASSANDRA-1290
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.7
Reporter: Jon Hermes
Assignee: Jon Hermes
Priority: Minor
Fix For: 0.7
Spawned by CASSANDRA-475 .
The cli uses non-framed transport, which causes errors on connection that look
like:
cli:{noformat}$ bin/cassandra-cli
Welcome to cassandra CLI.
Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
[defa...@unknown] connect 127.0.0.1/9160
Exception retrieving information about the cassandra node, check you have
connected to the thrift port.{noformat}
cass:{noformat}ERROR 15:48:12,523 Thrift error occurred during processing of
message.
org.apache.thrift.TException: Message length exceeded: 1684370275
at
org.apache.thrift.protocol.TBinaryProtocol.checkReadLength(TBinaryProtocol.java:384)
at
org.apache.thrift.protocol.TBinaryProtocol.readStringBody(TBinaryProtocol.java:350)
at
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:213)
at
org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.java:2519)
at
org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:167)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619){noformat}
Changing it to use framed transport fixes this, and it should be using framed
transport by default regardless.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
