Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-807

Improve cassandra-cli error display and thrift connection checking

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 0.6
    • Legacy/Tools
    • Java

    Description

      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

      Attachments

        1. cassandra-cli-cleanup.patch
          9 kB
          Mark Wolfe

        Activity

          People

            wolfeidau Mark Wolfe
            wolfeidau Mark Wolfe
            Mark Wolfe
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: