[
https://issues.apache.org/jira/browse/CASSANDRA-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835009#action_12835009
]
Mark Wolfe commented on CASSANDRA-807:
--------------------------------------
Just to illustrate what this looks like..
cassandra-trunk markw$ bin/cassandra-cli
Welcome to cassandra CLI.
Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
cassandra> connect localhostss/9160
Exception connecting to localhostss/9160 - java.net.UnknownHostException:
localhostss
cassandra> connect localhost/8888
Exception retrieving cluster name, check you have connected to the thrift port.
cassandra> connect localhost/9160
Connected to localhost/9160 cluster - Test Cluster
cassandra> exit
cassandra-trunk markw$
> Improve cassandra-cli error display and thrift connection checking
> ------------------------------------------------------------------
>
> Key: CASSANDRA-807
> URL: https://issues.apache.org/jira/browse/CASSANDRA-807
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Environment: Java
> Reporter: Mark Wolfe
> Attachments: cassandra-cli-cleanup.patch
>
>
> A new user observed that thier was some ambiguous error messages presented by
> the cassandra CLI if you connected to the wrong port on the cassandra daemon,
> or in fact anything else listening for a tcp connection. The CLI will say
> "connected" but when you run any of the commands a thrift exception will be
> displayed.
> So I suggest the following enhancements:
> * Verify that the CLI is indeed connected to a thrift port by requesting the
> cluster name
> * Hide as many of the stack traces as possible displaying a simple error
> message
> * Implement a --debug argument to the CLI which will output stacktraces
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
