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

Confusing error message on schema updates when nodes are down

Agile BoardAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Low
    • Resolution: Unresolved
    • None
    • Legacy/Tools
    • PROD

    • Low

    Description

      Repro steps are as follows (this was tested on Windows and is a consistent repro)

      . Start a two node cluster.
      . Ensure that "nodetool status" shows both nodes as UN on both nodes
      . Stop Node2
      . Ensure that "nodetool status" shows that Node2 in DN.
      . Start cqlsh on Node1
      . Create a table
      . cqlsh times out with below message (coming from .py)

      Warning: schema version mismatch detected, which might be caused by DOWN nodes; if this is not the case, check the schema versions of your nodes in system.local and system.peers.
      OperationTimedOut: errors={}, last_host=10.1.0.10
      . Do a select * on the table that just timed out. It works fine.

      It just seems odd that there are no errors, but the table gets created fine. We should either fix the timeout exception with a real error or not throw timeout. Not sure what the best approach is.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned Assign to me
            anubhavk Anubhav Kale

            Dates

              Created:
              Updated:

              Issue deployment