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

Unable to truncate column family on node which has been decommissioned and re-bootstrapped

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


    • Type: Bug
    • Status: Resolved
    • Priority: Low
    • Resolution: Fixed
    • Fix Version/s: 1.2.17, 2.0.9, 2.1 rc2
    • Component/s: None
    • Labels:
    • Environment:

      Seen running cassandra 2.0.7 running on Red Hat Linux

    • Severity:


      After decommissioning a node, then re-bootstrapping it, it's not possible to truncate column families until cassandra is restarted.

      Steps to reproduce:

      • Start with a two node deployment (nodes A and B)
      • Run nodetool decommission on node B
      • Stop cassandra on node B
      • Delete the contents of the cassandra data and commitlog directories
      • Start cassandra on node B with node A as the seed
      • Run cqlsh on node B and try to truncate a column family
      • cqlsh displays: "Unable to complete request: one or more nodes were unavailable."

      According to the logs node B seems to think that itself is down. The follow logs appear when the server is started and there are no further logs to indicate the B is now UP (A=, B=

      INFO [main] 2014-05-29 10:40:11,090 MessagingService.java (line 461) Starting Messaging Service on port 7000
      INFO [HANDSHAKE-/] 2014-05-29 10:40:11,106 OutboundTcpConnection.java (line 386) Handshaking version with /
      INFO [GossipStage:1] 2014-05-29 10:40:11,182 Gossiper.java (line 903) Node / is now part of the cluster
      INFO [GossipStage:1] 2014-05-29 10:40:11,185 Gossiper.java (line 883) InetAddress / is now DOWN
      INFO [RequestResponseStage:1] 2014-05-29 10:40:11,215 Gossiper.java (line 869) InetAddress / is now UP

      This problem isn't hit if cassandra is restarted on node A while node B is stopped. The problem goes away if node B is restarted.




            • Assignee:
              brandon.williams Brandon Williams Assign to me
              thomaswhiteway Thomas Whiteway
              Brandon Williams
              Tom Hobbs
              Kishan Karunaratne


              • Created:

                Issue deployment