You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (Jira)" <ji...@apache.org> on 2021/02/03 12:03:00 UTC

[jira] [Issue Comment Deleted] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”

     [ https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Lerer updated CASSANDRA-16381:
---------------------------------------
    Comment: was deleted

(was: [~brandon.williams] Could it be linked to the changes to {{CassandraCompressedStreamWriter}} and {{CassandraStreamWriter}} where we create a new channel instead or reusing the existing one (see https://github.com/apache/cassandra/commit/9f6fcc340d89eecc000765f6ab93e862f53a02d9)?
That change was added to prevent interruped thread from closing the backing channel but it can probably be achieved in another way.)

> nodetool removenode error “Conflicting replica added”
> -----------------------------------------------------
>
>                 Key: CASSANDRA-16381
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16381
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Bootstrap and Decommission
>            Reporter: vincent royer
>            Assignee: Brandon Williams
>            Priority: Normal
>             Fix For: 4.0-beta
>
>
> When testing elassandra on C* 4.0, integration tests with ccm systematically failed on removing a node with the following error “Conflicting replica added” . [This integration test |https://github.com/strapdata/elassandra/blob/v6.8.4-strapdata/integ-test/test-cleanup-repair.sh#L289] was ok with Elassandra based on Cassandra 3.11, and there is no changes in that test. Moreover, it seems there is no cassandra-test (dtest) for removing a node (there is only one removenode test for transient replication). The topology_test.py remove a node from the CCM cluster, but it does not call nodetool removenode.
> I wonder if we have a non-tested regression here in C 4.0 ?
> ++ ccm node1 nodetool status
> ++ awk ‘/127.0.0.3/ \{ print $7 }’
> + HOST_ID3=6d2e858f-dacc-4c7c-a626-14b45f6b3b94
> + ccm node3 stop
> + ccm node1 nodetool removenode 6d2e858f-dacc-4c7c-a626-14b45f6b3b94
> Traceback (most recent call last):
>   File “/usr/local/bin/ccm”, line 4, in <module>
>     __import__(‘pkg_resources’).run_script(‘ccm==3.1.6’, ‘ccm’)
>   File “/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/__init__.py”, line 742, in run_script
>     self.require(requires)[0].run_script(script_name, ns)
>   File “/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/__init__.py”, line 1674, in run_script
>     exec(script_code, namespace, namespace)
>   File “/Library/Python/2.7/site-packages/ccm-3.1.6-py2.7.egg/EGG-INFO/scripts/ccm”, line 112, in <module>  File “build/bdist.macosx-10.14-intel/egg/ccmlib/cmds/node_cmds.py”, line 233, in run
>   File “build/bdist.macosx-10.14-intel/egg/ccmlib/node.py”, line 848, in nodetool
>   File “build/bdist.macosx-10.14-intel/egg/ccmlib/node.py”, line 2131, in handle_external_tool_process
> ccmlib.node.ToolError: Subprocess [‘nodetool’, ‘-h’, ‘localhost’, ‘-p’, ‘7100’, ‘removenode’, ‘6d2e858f-dacc-4c7c-a626-14b45f6b3b94’] exited with non-zero status; exit status: 1;
> stdout: nodetool: Conflicting replica added (expected unique ranges): Full(/127.0.0.1:7000,(4949329179655327935,6135417578204142297]); existing: Full(/127.0.0.1:7000,(4949329179655327935,6135417578204142297])
> See ‘nodetool help’ or ‘nodetool help <command>’.++ finish
> ++ echo ‘ERROR occurs, test failed’
> ERROR occurs, test failed
> ++ ‘[’ ‘!’ -z ‘’ ‘]’
> ++ exit 1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org