You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Blake Atkinson (JIRA)" <ji...@apache.org> on 2015/07/30 21:48:04 UTC
[jira] [Created] (CASSANDRA-9943) nodetool repair error: "nodetool
failed, check server logs"
Blake Atkinson created CASSANDRA-9943:
-----------------------------------------
Summary: nodetool repair error: "nodetool failed, check server logs"
Key: CASSANDRA-9943
URL: https://issues.apache.org/jira/browse/CASSANDRA-9943
Project: Cassandra
Issue Type: Bug
Environment: Ubuntu 14.04
AWS m3.xlarge
Cassandra 2.1.8
Reporter: Blake Atkinson
Priority: Minor
Attachments: system.log
Rolling a "nodetool repair -pr" through a 5 node cluster and got the following error at the end of the repair:
{noformat}
[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)
{noformat}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)