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

nodetool repair error: "nodetool failed, check server logs"

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Cannot Reproduce
    • None
    • None
    • None
    • Ubuntu 14.04
      AWS m3.xlarge
      Cassandra 2.1.8

    • Low

    Description

      Rolling a "nodetool repair -pr" through a 5 node cluster and got the following error at the end of the repair:

      [2015-07-30 19:04:46,136] Repair session d7bd3ac0-36ed-11e5-b5e9-fbf3677ba4be for range (7944740144028661,11828837077287116] finished
      [2015-07-30 19:04:46,136] Repair session d7c09620-36ed-11e5-b5e9-fbf3677ba4be for range (1732339538045103946,1747616566950087006] finished
      [2015-07-30 19:04:46,136] Repair session d7c502f1-36ed-11e5-b5e9-fbf3677ba4be for range (-6749979629629406618,-6744383949129926802] finished
      [2015-07-30 19:04:46,137] Repair session d7c8fa90-36ed-11e5-b5e9-fbf3677ba4be for range (4123273621202200825,4151984034998723255] finished
      [2015-07-30 19:04:46,137] Repair command #8 finished
      error: nodetool failed, check server logs
      -- StackTrace --
      java.lang.RuntimeException: nodetool failed, check server logs
              at org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:290)
              at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:202)
      

      I've seen it before with repairs on previous versions of 2.1, but can't repro it consistently. Right after the repair "finishes", it spits out many "LEAK DETECTED", but not sure if it's related.

      Attachments

        1. system.log
          8.39 MB
          Blake Atkinson

        Activity

          People

            Unassigned Unassigned
            Blake Atkinson Blake Atkinson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: