[jira] [Commented] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”
[
https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289673#comment-17289673
]
Berenguer Blasi commented on CASSANDRA-16381:
-
The networking topology failure is a known failure, correct.
[~aholmber] plenty of random commits got pushed to the PR, probably some git
acrobatics gone wrong :-) Also seems the original commit is missing a test _if_
it's doable and you'll have to re-run ci bc the ci runs we have have those
extra commits.
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16441) Snapshot_test.py DTests failing
[ https://issues.apache.org/jira/browse/CASSANDRA-16441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289430#comment-17289430 ] Brandon Williams edited comment on CASSANDRA-16441 at 2/23/21, 11:33 PM: - I haven't been able to reproduce these failures exactly, but I did find a race when [copying files|https://github.com/apache/cassandra-dtest/blob/trunk/snapshot_test.py#L216] when autocompaction is still enabled. Patch to disable it. So far this seems to be running smoothly for me. was (Author: brandon.williams): I haven't been able to reproduce these failures exactly, but I did find a race when [copying files|https://github.com/apache/cassandra-dtest/blob/trunk/snapshot_test.py#L58] when autocompaction is still enabled. Patch to disable it. So far this seems to be running smoothly for me. > Snapshot_test.py DTests failing > --- > > Key: CASSANDRA-16441 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16441 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0-beta5, 4.0-beta > > > [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/623/workflows/1c89bd58-bcd1-45dc-b923-3aba245a78a6/jobs/3451] > These failures are also observed for other patches in Jenkins dev (weird but > they are not seen failing in the latest builds and they are failing with > completely unrelated different patches...) > [https://jenkins-cm4.apache.org/job/Cassandra-devbranch/375/#showFailuresLink] > [https://jenkins-cm4.apache.org/job/Cassandra-devbranch/368/] > Jenkins dev history for one of the tests: > https://jenkins-cm4.apache.org/job/Cassandra-devbranch/375/testReport/junit/dtest-novnode.snapshot_test/TestArchiveCommitlog/test_archive_commitlog_with_active_commitlog/history/ > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16441) Snapshot_test.py DTests failing
[ https://issues.apache.org/jira/browse/CASSANDRA-16441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289430#comment-17289430 ] Brandon Williams commented on CASSANDRA-16441: -- I haven't been able to reproduce these failures exactly, but I did find a race when [copying files|https://github.com/apache/cassandra-dtest/blob/trunk/snapshot_test.py#L58] when autocompaction is still enabled. Patch to disable it. So far this seems to be running smoothly for me. > Snapshot_test.py DTests failing > --- > > Key: CASSANDRA-16441 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16441 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0-beta5, 4.0-beta > > > [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/623/workflows/1c89bd58-bcd1-45dc-b923-3aba245a78a6/jobs/3451] > These failures are also observed for other patches in Jenkins dev (weird but > they are not seen failing in the latest builds and they are failing with > completely unrelated different patches...) > [https://jenkins-cm4.apache.org/job/Cassandra-devbranch/375/#showFailuresLink] > [https://jenkins-cm4.apache.org/job/Cassandra-devbranch/368/] > Jenkins dev history for one of the tests: > https://jenkins-cm4.apache.org/job/Cassandra-devbranch/375/testReport/junit/dtest-novnode.snapshot_test/TestArchiveCommitlog/test_archive_commitlog_with_active_commitlog/history/ > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289094#comment-17289094
]
Ekaterina Dimitrova edited comment on CASSANDRA-16443 at 2/23/21, 11:13 PM:
[~Bereng] when I pointed you there I was responding to a different question but
I believe we cleared the topic on Slack. Yes, the merge happens on a per second
resolution. Please let me know if there are any additional questions I can try
to help with.
Patch committed
[here|https://github.com/apache/cassandra/commit/0b60c8f37694d44482768ebc327989f7a42c8c08].
Thank you!
was (Author: e.dimitrova):
[~Bereng] when I pointed you there I was responding to a different question but
I believe we cleared the topic on Slack. Yes, the merge happens on a per second
resolution. Please let me know if there are any additional questions I can try
to help with.
Committed
[here|https://github.com/apache/cassandra/commit/0b60c8f37694d44482768ebc327989f7a42c8c08].
Thank you!
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
>
[jira] [Comment Edited] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289094#comment-17289094
]
Ekaterina Dimitrova edited comment on CASSANDRA-16443 at 2/23/21, 11:12 PM:
[~Bereng] when I pointed you there I was responding to a different question but
I believe we cleared the topic on Slack. Yes, the merge happens on a per second
resolution. Please let me know if there are any additional questions I can try
to help with.
Committed
[here|https://github.com/apache/cassandra/commit/0b60c8f37694d44482768ebc327989f7a42c8c08].
Thank you!
was (Author: e.dimitrova):
When I pointed you there I was responding to a different question but I believe
we cleaned the topic on Slack. Yes, the merge happens on a per second
resolution. Please let me know if there are any additional questions I can try
to help with.
Committed
[here|https://github.com/apache/cassandra/commit/0b60c8f37694d44482768ebc327989f7a42c8c08].
Thank you!
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
>
[jira] [Comment Edited] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289094#comment-17289094
]
Ekaterina Dimitrova edited comment on CASSANDRA-16443 at 2/23/21, 11:12 PM:
When I pointed you there I was responding to a different question but I believe
we cleaned the topic on Slack. Yes, the merge happens on a per second
resolution. Please let me know if there are any additional questions I can try
to help with.
Committed
[here|https://github.com/apache/cassandra/commit/0b60c8f37694d44482768ebc327989f7a42c8c08].
Thank you!
was (Author: e.dimitrova):
When I pointed you there I was responding to a different question but I believe
we cleaned the topic on Slack. Yes, the merge happens on a per second
resolution. Please let me know if there are any additional questions I can try
to help with.
Committed [here
|https://github.com/apache/cassandra/commit/0b60c8f37694d44482768ebc327989f7a42c8c08].
Thank you!
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
>
[jira] [Updated] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16443:
Fix Version/s: (was: 4.0-beta)
4.0
Since Version: 4.0-beta4
Source Control Link:
https://github.com/apache/cassandra/commit/0b60c8f37694d44482768ebc327989f7a42c8c08
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
> org.apache.cassandra.config.EncryptionOptions.(EncryptionOptions.java:242)
> at org.apache.cassandra.config.Config.(Config.java:280)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
>
[jira] [Updated] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16443:
Since Version: (was: 4.0-beta4)
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
> org.apache.cassandra.config.EncryptionOptions.(EncryptionOptions.java:242)
> at org.apache.cassandra.config.Config.(Config.java:280)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> at
> org.yaml.snakeyaml.constructor.BaseConstructor.newInstance(BaseConstructor.java:330)
> at
> org.yaml.snakeyaml.constructor.BaseConstructor.newInstance(BaseConstructor.java:308)
> at
>
[jira] [Comment Edited] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289094#comment-17289094
]
Ekaterina Dimitrova edited comment on CASSANDRA-16443 at 2/23/21, 11:11 PM:
When I pointed you there I was responding to a different question but I believe
we cleaned the topic on Slack. Yes, the merge happens on a per second
resolution. Please let me know if there are any additional questions I can try
to help with.
Committed [here
|https://github.com/apache/cassandra/commit/0b60c8f37694d44482768ebc327989f7a42c8c08].
Thank you!
was (Author: e.dimitrova):
When I pointed you there I was responding to a different question but I believe
we cleaned the topic on Slack. Yes, the merge happens on a per second
resolution.
I believe this one is ready to commit if there are no other outstanding
questions?
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0-beta
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
> org.apache.cassandra.config.EncryptionOptions.(EncryptionOptions.java:242)
> at org.apache.cassandra.config.Config.(Config.java:280)
> at
>
[cassandra] branch trunk updated: Fix timestamp issue in SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
This is an automated email from the ASF dual-hosted git repository.
edimitrova pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new 0b60c8f Fix timestamp issue in SinglePartitionSliceCommandTest
testPartitionDeletionRowDeletionTie
0b60c8f is described below
commit 0b60c8f37694d44482768ebc327989f7a42c8c08
Author: Benjamin Lerer
AuthorDate: Fri Feb 19 18:00:13 2021 +0100
Fix timestamp issue in SinglePartitionSliceCommandTest
testPartitionDeletionRowDeletionTie
Patch by Benjamin Lerer; reviewed by Ekaterina Dimitrova and Berenguer
Blasi for CASSANDRA-16443
---
CHANGES.txt| 1 +
.../org/apache/cassandra/cql3/QueryProcessor.java | 22 +++---
.../db/SinglePartitionSliceCommandTest.java| 12 ++--
3 files changed, 30 insertions(+), 5 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index c2abba7..dbfa272 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
4.0-beta5
+ * Fix timestamp issue in SinglePartitionSliceCommandTest
testPartitionD…eletionRowDeletionTie (CASSANDRA-16443)
* Promote protocol V5 out of beta (CASSANDRA-14973)
* Fix incorrect encoding for strings can be UTF8 (CASSANDRA-16429)
* Fix node unable to join when RF > N in multi-DC with added warning
(CASSANDRA-16296)
diff --git a/src/java/org/apache/cassandra/cql3/QueryProcessor.java
b/src/java/org/apache/cassandra/cql3/QueryProcessor.java
index c92718d..87829ab 100644
--- a/src/java/org/apache/cassandra/cql3/QueryProcessor.java
+++ b/src/java/org/apache/cassandra/cql3/QueryProcessor.java
@@ -368,9 +368,25 @@ public class QueryProcessor implements QueryHandler
*/
public static UntypedResultSet executeOnceInternal(String query, Object...
values)
{
-CQLStatement statement = parseStatement(query,
internalQueryState().getClientState());
-statement.validate(internalQueryState().getClientState());
-ResultMessage result = statement.executeLocally(internalQueryState(),
makeInternalOptions(statement, values));
+return executeOnceInternal(internalQueryState(), query, values);
+}
+
+/**
+ * Execute an internal query with the provided {@code nowInSec} and {@code
timestamp} for the {@code QueryState}.
+ * This method ensure that the statement will not be cached in the
prepared statement cache.
+ */
+@VisibleForTesting
+public static UntypedResultSet executeOnceInternalWithNowAndTimestamp(int
nowInSec, long timestamp, String query, Object... values)
+{
+QueryState queryState = new
QueryState(InternalStateInstance.INSTANCE.clientState, timestamp, nowInSec);
+return executeOnceInternal(queryState, query, values);
+}
+
+private static UntypedResultSet executeOnceInternal(QueryState queryState,
String query, Object... values)
+{
+CQLStatement statement = parseStatement(query,
queryState.getClientState());
+statement.validate(queryState.getClientState());
+ResultMessage result = statement.executeLocally(queryState,
makeInternalOptions(statement, values));
if (result instanceof ResultMessage.Rows)
return
UntypedResultSet.create(((ResultMessage.Rows)result).result);
else
diff --git
a/test/unit/org/apache/cassandra/db/SinglePartitionSliceCommandTest.java
b/test/unit/org/apache/cassandra/db/SinglePartitionSliceCommandTest.java
index 12168ec..102eb90 100644
--- a/test/unit/org/apache/cassandra/db/SinglePartitionSliceCommandTest.java
+++ b/test/unit/org/apache/cassandra/db/SinglePartitionSliceCommandTest.java
@@ -343,10 +343,18 @@ public class SinglePartitionSliceCommandTest
BiFunction> tester = (flush,
multiSSTable)->
{
cfs.truncateBlocking();
-QueryProcessor.executeOnceInternal("DELETE FROM
ks.partition_row_deletion USING TIMESTAMP 10 WHERE k=1");
+
+final long timestamp = FBUtilities.timestampMicros();
+final int nowInSec = FBUtilities.nowInSeconds();
+
+QueryProcessor.executeOnceInternalWithNowAndTimestamp(nowInSec,
+ timestamp,
+ "DELETE FROM
ks.partition_row_deletion USING TIMESTAMP 10 WHERE k=1");
if (flush && multiSSTable)
cfs.forceBlockingFlush();
-QueryProcessor.executeOnceInternal("DELETE FROM
ks.partition_row_deletion USING TIMESTAMP 10 WHERE k=1 and c=1");
+QueryProcessor.executeOnceInternalWithNowAndTimestamp(nowInSec,
+ timestamp,
+ "DELETE FROM
ks.partition_row_deletion USING TIMESTAMP 10 WHERE k=1 and c=1");
if (flush)
[jira] [Commented] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”
[
https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289411#comment-17289411
]
Brandon Williams commented on CASSANDRA-16381:
--
bq. my dtest passed.
Scratch that, it never ran because I ran against the current dtests.
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”
[
https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289409#comment-17289409
]
Adam Holmberg commented on CASSANDRA-16381:
---
This test is broken for 4.0, independent of the changes I'm proposing here
(it's regexing for trace messages that changed format). I'll open a ticket, but
I would prefer not to block since it's known to be a test issue, and I've
manually verified the functionality that test is trying to characterize.
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16467) speculative retry should allow more friendly params, allowing upgrade from 2.x not to break
[ https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-16467: - Test and Documentation Plan: existing test coverage Status: Patch Available (was: Open) > speculative retry should allow more friendly params, allowing upgrade from > 2.x not to break > --- > > Key: CASSANDRA-16467 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16467 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > 2.x speculative retry params are case insensitive, while 3.0 and 3.11 have > added case sensitivity. As as result of this, one of our internal > applications suffered an issue during > C* upgrade from 2.x to 3.0. > This ticket is to propose making 3.0 and 3.11 speculative_retry params case > insensitive as well (essentially a slightly modified backport of > CASSANDRA-13876, but not to allow something like "99p" which 4.0 allows) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16467) speculative retry should allow more friendly params, allowing upgrade from 2.x not to break
[ https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-16467: - Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Component/s: Local/Config Discovered By: User Report Severity: Low Status: Open (was: Triage Needed) > speculative retry should allow more friendly params, allowing upgrade from > 2.x not to break > --- > > Key: CASSANDRA-16467 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16467 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > 2.x speculative retry params are case insensitive, while 3.0 and 3.11 have > added case sensitivity. As as result of this, one of our internal > applications suffered an issue during > C* upgrade from 2.x to 3.0. > This ticket is to propose making 3.0 and 3.11 speculative_retry params case > insensitive as well (essentially a slightly modified backport of > CASSANDRA-13876, but not to allow something like "99p" which 4.0 allows) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”
[
https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289375#comment-17289375
]
Brandon Williams edited comment on CASSANDRA-16381 at 2/23/21, 9:52 PM:
[This|https://ci-cassandra.apache.org/job/Cassandra-devbranch/395/testReport/junit/dtest-large-novnode.replication_test/TestReplication/test_network_topology/]
looks a bit suspect to me, though the code looks good and my dtest passed.
was (Author: brandon.williams):
[|This|https://ci-cassandra.apache.org/job/Cassandra-devbranch/395/testReport/junit/dtest-large-novnode.replication_test/TestReplication/test_network_topology/]
looks a bit suspect to me, though the code looks good and my dtest passed.
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”
[
https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289375#comment-17289375
]
Brandon Williams commented on CASSANDRA-16381:
--
[|This|https://ci-cassandra.apache.org/job/Cassandra-devbranch/395/testReport/junit/dtest-large-novnode.replication_test/TestReplication/test_network_topology/]
looks a bit suspect to me, though the code looks good and my dtest passed.
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16467) speculative retry should allow more friendly params, allowing upgrade from 2.x not to break
[ https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289304#comment-17289304 ] Sumanth Pasupuleti commented on CASSANDRA-16467: *3.0.x* [Patch|https://github.com/apache/cassandra/compare/cassandra-3.0...sumanth-pasupuleti:bugfix/30_speculative_retry_params_case] [Passing UTs|https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra/53/workflows/3a0b4cdd-32c8-4b8a-83fa-34e6a78679d5] *3.11.x* [Patch|https://github.com/apache/cassandra/compare/cassandra-3.11...sumanth-pasupuleti:bugfix/311_speculative_retry_params_case] [UTs|https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra/54/workflows/6241a82b-3dde-4599-9c72-7d11e39c7206] (one failing that seems unrelated) > speculative retry should allow more friendly params, allowing upgrade from > 2.x not to break > --- > > Key: CASSANDRA-16467 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16467 > Project: Cassandra > Issue Type: Bug >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > 2.x speculative retry params are case insensitive, while 3.0 and 3.11 have > added case sensitivity. As as result of this, one of our internal > applications suffered an issue during > C* upgrade from 2.x to 3.0. > This ticket is to propose making 3.0 and 3.11 speculative_retry params case > insensitive as well (essentially a slightly modified backport of > CASSANDRA-13876, but not to allow something like "99p" which 4.0 allows) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16467) speculative retry should allow more friendly params, allowing upgrade from 2.x not to break
[ https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumanth Pasupuleti updated CASSANDRA-16467: --- Fix Version/s: 3.11.x 3.0.x > speculative retry should allow more friendly params, allowing upgrade from > 2.x not to break > --- > > Key: CASSANDRA-16467 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16467 > Project: Cassandra > Issue Type: Bug >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > 2.x speculative retry params are case insensitive, while 3.0 and 3.11 have > added case sensitivity. As as result of this, one of our internal > applications suffered an issue during > C* upgrade from 2.x to 3.0. > This ticket is to propose making 3.0 and 3.11 speculative_retry params case > insensitive as well (essentially a slightly modified backport of > CASSANDRA-13876, but not to allow something like "99p" which 4.0 allows) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16467) speculative retry should allow more friendly params, allowing upgrade from 2.x not to break
Sumanth Pasupuleti created CASSANDRA-16467: -- Summary: speculative retry should allow more friendly params, allowing upgrade from 2.x not to break Key: CASSANDRA-16467 URL: https://issues.apache.org/jira/browse/CASSANDRA-16467 Project: Cassandra Issue Type: Bug Reporter: Sumanth Pasupuleti Assignee: Sumanth Pasupuleti 2.x speculative retry params are case insensitive, while 3.0 and 3.11 have added case sensitivity. As as result of this, one of our internal applications suffered an issue during C* upgrade from 2.x to 3.0. This ticket is to propose making 3.0 and 3.11 speculative_retry params case insensitive as well (essentially a slightly modified backport of CASSANDRA-13876, but not to allow something like "99p" which 4.0 allows) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16456) Add Plugin Support for CQLSH
[ https://issues.apache.org/jira/browse/CASSANDRA-16456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289288#comment-17289288 ] Sumanth Pasupuleti commented on CASSANDRA-16456: +1 to the idea of adding plugin support that would allow using both an AuthProvider that is provided within the python C* driver, as well as a custom AuthProvider one may potentially write. We currently have an internal minor patch to cqlsh to accommodate our internal AuthProvider. This ticket would certainly help us not have that minor fork and rather plugin our custom AuthProvider. > Add Plugin Support for CQLSH > > > Key: CASSANDRA-16456 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16456 > Project: Cassandra > Issue Type: New Feature >Reporter: Brian Houser >Priority: Normal > Labels: gsoc2021, mentor > > Currently the Cassandra drivers offer a plugin authenticator architecture for > the support of different authentication methods. This has been leveraged to > provide support for LDAP, Kerberos, and Sigv4 authentication. Unfortunately, > cqlsh, the included CLI tool, does not offer such support. Switching to a new > enhanced authentication scheme thus means being cut off from using cqlsh in > normal operation. > We should have a means of using the same plugins and authentication providers > as the Python Cassandra driver. > Here's a link to an initial draft of > [CEP|https://docs.google.com/document/d/1_G-OZCAEmDyuQuAN2wQUYUtZBEJpMkHWnkYELLhqvKc/edit?usp=sharing]. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16415) Broken test mixedModeReadColumnSubsetDigestCheck - org.apache.cassandra.distributed.upgrade.MixedModeReadTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289233#comment-17289233
]
Andres de la Peña commented on CASSANDRA-16415:
---
New CI rounds for the last changes:
*
[3.0|https://app.circleci.com/pipelines/github/adelapena/cassandra/192/workflows/7c49eee3-4e2b-4140-bc09-30d80eeb20f7]
*
[3.11|https://app.circleci.com/pipelines/github/adelapena/cassandra/190/workflows/4941bf2b-fef2-4cda-aae9-7e2b3e8614a2]
* [trunk
(j8)|https://app.circleci.com/pipelines/github/adelapena/cassandra/191/workflows/c5b5107d-70cc-4fcf-8794-fc3b2d903b22]
* [trunk
(j11)|https://app.circleci.com/pipelines/github/adelapena/cassandra/191/workflows/0be9401d-a625-4fd8-9cb6-e43d8c181629]
> Broken test mixedModeReadColumnSubsetDigestCheck -
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest
> -
>
> Key: CASSANDRA-16415
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16415
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination, Test/dtest/java
>Reporter: Yifan Cai
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
> Time Spent: 6h 50m
> Remaining Estimate: 0h
>
> The test has been failing and can always be reproduced in the recent CI.
> Stack trace:
> {code:java}
> junit.framework.AssertionFailedError: Found Digest Mismatch
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.checkTraceForDigestMismatch(MixedModeReadTest.java:89)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.lambda$mixedModeReadColumnSubsetDigestCheck$0(MixedModeReadTest.java:63)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:171)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck(MixedModeReadTest.java:76)
> {code}
> The initial investigation shows that
> * The test only fails in the setup phase of
> mixedModeReadColumnSubsetDigestCheck. The cluster version is
> *Versions.Major.v3X*
> * The test failure is likely a consequence of CASSANDRA-15962. After
> dropping the commit in branch cassandra-3.11 and rebuild the dtest jar, the
> upgrade test can pass. Meanwhile, dropping the other commits does not help.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14973) Bring protocol v5 out of beta, introduce v6 before 4.0 release is cut
[
https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-14973:
Source Control Link:
https://github.com/apache/cassandra/commit/c9d6c725dd0b4aa5693eb1c6d2221c28e9e99c6e
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
I spoke to [~eduard.tudenhoefner] & [~adutra] offline & everyone was happy to
merge now, so I've committed to trunk in
{{c9d6c725dd0b4aa5693eb1c6d2221c28e9e99c6e}}.
I've opened a [dtest pr|https://github.com/apache/cassandra-dtest/pull/127]
with the minor changes required there. Only
{{test_cqlsh.py::TestCqlsh::test_protocol_negotiation}} should actually break
without the dtest change.
> Bring protocol v5 out of beta, introduce v6 before 4.0 release is cut
> -
>
> Key: CASSANDRA-14973
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14973
> Project: Cassandra
> Issue Type: Task
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Urgent
> Labels: protocolv5
> Fix For: 4.0-beta
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced
> Beta flag for v5 protocol. However, up till now, v5 is in beta both in
> [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46]
> and in
> [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35].
>
> Before the final 4.0 release is cut, we need to bring v5 out of beta and
> finalise native protocol spec, and start bringing all new changes to v6
> protocol, which will be in beta.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Promote protocol v5 from beta
This is an automated email from the ASF dual-hosted git repository. samt pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new c9d6c72 Promote protocol v5 from beta c9d6c72 is described below commit c9d6c725dd0b4aa5693eb1c6d2221c28e9e99c6e Author: Sam Tunnicliffe AuthorDate: Mon Feb 22 12:01:36 2021 + Promote protocol v5 from beta Patch by Sam Tunnicliffe; reviewed by Alex Petrov and Eduard Tudenhoefner for CASSANDRA-14973 --- CHANGES.txt| 1 + NEWS.txt | 2 +- bin/cqlsh.py | 2 +- build.xml | 23 +++- ...sandra-driver-core-3.10.3-1af7382fe-shaded.jar} | Bin 2780339 -> 2781089 bytes ...-driver-internal-only-3.23.0.post0-1a184b99.zip | Bin 348039 -> 0 bytes ...sandra-driver-internal-only-3.24.0-1de685b1.zip | Bin 0 -> 346893 bytes .../cassandra/cql3/functions/types/CodecUtils.java | 5 +++ .../cassandra/transport/CQLMessageHandler.java | 39 ++--- .../cassandra/transport/ClientResourceLimits.java | 7 ++-- .../cassandra/transport/ProtocolVersion.java | 9 ++--- .../cql3/statements/DescribeStatementTest.java | 2 +- .../cassandra/service/ProtocolBetaVersionTest.java | 2 +- .../cassandra/transport/CQLConnectionTest.java | 2 +- .../transport/ProtocolNegotiationTest.java | 19 +- .../cassandra/transport/ProtocolVersionTest.java | 10 -- .../cassandra/stress/settings/SettingsMode.java| 2 +- 17 files changed, 75 insertions(+), 50 deletions(-) diff --git a/CHANGES.txt b/CHANGES.txt index 4d3372b..c2abba7 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 4.0-beta5 + * Promote protocol V5 out of beta (CASSANDRA-14973) * Fix incorrect encoding for strings can be UTF8 (CASSANDRA-16429) * Fix node unable to join when RF > N in multi-DC with added warning (CASSANDRA-16296) * Add an option to nodetool tablestats to check sstable location correctness (CASSANDRA-16344) diff --git a/NEWS.txt b/NEWS.txt index 817f286..3fd26e4 100644 --- a/NEWS.txt +++ b/NEWS.txt @@ -133,7 +133,7 @@ Upgrading CASSANDRA-16083, backward compatibility layer was added so it can be still exposed under the old 3.11 scope. - Native protocol v5 is promoted from beta in this release. The wire format has changed significantly and users should take care to ensure client drivers are upgraded to a version - with support for the final v5 format, if currently connecting over v5-beta. (CASSANDRA-15299) + with support for the final v5 format, if currently connecting over v5-beta. (CASSANDRA-15299, CASSANDRA-14973) - Cassandra removed support for the OldNetworkTopologyStrategy. Before upgrading you will need to change the replication strategy for the keyspaces using this strategy to the NetworkTopologyStrategy. (CASSANDRA-13990) - Sstables for tables using with a frozen UDT written by C* 3.0 appear as corrupted. diff --git a/bin/cqlsh.py b/bin/cqlsh.py index 5162a00..09183a7 100644 --- a/bin/cqlsh.py +++ b/bin/cqlsh.py @@ -476,7 +476,7 @@ class Shell(cmd.Cmd): if protocol_version is not None: kwargs['protocol_version'] = protocol_version else: -kwargs['protocol_version'] = 4 +kwargs['protocol_version'] = 5 self.conn = Cluster(contact_points=(self.hostname,), port=self.port, cql_version=cqlver, auth_provider=self.auth_provider, ssl_options=sslhandling.ssl_settings(hostname, CONFIG_FILE) if ssl else None, diff --git a/build.xml b/build.xml index c397019..5c93897 100644 --- a/build.xml +++ b/build.xml @@ -645,6 +645,7 @@ + @@ -748,7 +750,9 @@ + @@ -779,7 +783,9 @@ + @@ -856,14 +862,15 @@ - - - - - - - - + + diff --git a/lib/cassandra-driver-core-3.10.0-shaded.jar b/lib/cassandra-driver-core-3.10.3-1af7382fe-shaded.jar similarity index 77% rename from lib/cassandra-driver-core-3.10.0-shaded.jar rename to lib/cassandra-driver-core-3.10.3-1af7382fe-shaded.jar index d53e577..adf439a 100644 Binary files a/lib/cassandra-driver-core-3.10.0-shaded.jar and b/lib/cassandra-driver-core-3.10.3-1af7382fe-shaded.jar differ diff --git a/lib/cassandra-driver-internal-only-3.23.0.post0-1a184b99.zip b/lib/cassandra-driver-internal-only-3.23.0.post0-1a184b99.zip deleted file mode 100644 index 9b25bc1..000
[jira] [Updated] (CASSANDRA-14973) Bring protocol v5 out of beta, introduce v6 before 4.0 release is cut
[ https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-14973: Summary: Bring protocol v5 out of beta, introduce v6 before 4.0 release is cut (was: Bring v5 driver out of beta, introduce v6 before 4.0 release is cut) > Bring protocol v5 out of beta, introduce v6 before 4.0 release is cut > - > > Key: CASSANDRA-14973 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14973 > Project: Cassandra > Issue Type: Task >Reporter: Alex Petrov >Assignee: Sam Tunnicliffe >Priority: Urgent > Labels: protocolv5 > Fix For: 4.0-beta > > > In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced > Beta flag for v5 protocol. However, up till now, v5 is in beta both in > [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46] > and in > [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35]. > > Before the final 4.0 release is cut, we need to bring v5 out of beta and > finalise native protocol spec, and start bringing all new changes to v6 > protocol, which will be in beta. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14973) Bring protocol v5 out of beta, introduce v6 before 4.0 release is cut
[ https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-14973: Status: Ready to Commit (was: Review In Progress) > Bring protocol v5 out of beta, introduce v6 before 4.0 release is cut > - > > Key: CASSANDRA-14973 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14973 > Project: Cassandra > Issue Type: Task >Reporter: Alex Petrov >Assignee: Sam Tunnicliffe >Priority: Urgent > Labels: protocolv5 > Fix For: 4.0-beta > > > In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced > Beta flag for v5 protocol. However, up till now, v5 is in beta both in > [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46] > and in > [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35]. > > Before the final 4.0 release is cut, we need to bring v5 out of beta and > finalise native protocol spec, and start bringing all new changes to v6 > protocol, which will be in beta. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14973) Bring v5 driver out of beta, introduce v6 before 4.0 release is cut
[ https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Holmberg updated CASSANDRA-14973: -- Status: Review In Progress (was: Patch Available) > Bring v5 driver out of beta, introduce v6 before 4.0 release is cut > --- > > Key: CASSANDRA-14973 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14973 > Project: Cassandra > Issue Type: Task >Reporter: Alex Petrov >Assignee: Sam Tunnicliffe >Priority: Urgent > Labels: protocolv5 > Fix For: 4.0-beta > > > In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced > Beta flag for v5 protocol. However, up till now, v5 is in beta both in > [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46] > and in > [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35]. > > Before the final 4.0 release is cut, we need to bring v5 out of beta and > finalise native protocol spec, and start bringing all new changes to v6 > protocol, which will be in beta. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16463) high and critical CVEs io.netty to 4.1.42.Final to fix critical and high vulnerabilities
[ https://issues.apache.org/jira/browse/CASSANDRA-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-16463: - Resolution: Invalid Status: Resolved (was: Open) > high and critical CVEs io.netty to 4.1.42.Final to fix critical and high > vulnerabilities > > > Key: CASSANDRA-16463 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16463 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Bhargav Joshi >Priority: High > > Repository | Tag | CVE ID | Severity | Packages | Source Package | Package > Version | Fix Status > -- | -- | -- | -- | -- | -- | -- | -- > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20445 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20444 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-16869 | high | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.42.Final -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16463) high and critical CVEs io.netty to 4.1.42.Final to fix critical and high vulnerabilities
[ https://issues.apache.org/jira/browse/CASSANDRA-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289143#comment-17289143 ] Benedict Elliott Smith edited comment on CASSANDRA-16463 at 2/23/21, 3:49 PM: -- The CVEs are not relevant to Cassandra as [we do not make use of the affected components|https://github.com/apache/cassandra/search?q=HttpObjectDecoder]. was (Author: benedict): The CVEs are not relevant to Cassandra as we do not make use of the affected components. > high and critical CVEs io.netty to 4.1.42.Final to fix critical and high > vulnerabilities > > > Key: CASSANDRA-16463 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16463 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Bhargav Joshi >Priority: High > > Repository | Tag | CVE ID | Severity | Packages | Source Package | Package > Version | Fix Status > -- | -- | -- | -- | -- | -- | -- | -- > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20445 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20444 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-16869 | high | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.42.Final -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16463) high and critical CVEs io.netty to 4.1.42.Final to fix critical and high vulnerabilities
[ https://issues.apache.org/jira/browse/CASSANDRA-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289143#comment-17289143 ] Benedict Elliott Smith commented on CASSANDRA-16463: The CVEs are not relevant to Cassandra as we do not make use of the affected components. > high and critical CVEs io.netty to 4.1.42.Final to fix critical and high > vulnerabilities > > > Key: CASSANDRA-16463 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16463 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Bhargav Joshi >Priority: High > > Repository | Tag | CVE ID | Severity | Packages | Source Package | Package > Version | Fix Status > -- | -- | -- | -- | -- | -- | -- | -- > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20445 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20444 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-16869 | high | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.42.Final -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14973) Bring v5 driver out of beta, introduce v6 before 4.0 release is cut
[
https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289124#comment-17289124
]
Sam Tunnicliffe commented on CASSANDRA-14973:
-
Looking at the CI results:
* the jvm-dtest failure looks unrelated, but I'll file a JIRA to investigate.
That fixture, {{CASTest}} has historically been flaky, so perhaps
CASSANDRA-16355 didn't catch all issues. I'll file a JIRA to investigate
* the failures on each of the cqlsh_dtests jobs are all coming from either
{{TestCqlshCopy}} and pass locally or
{{test_cqlsh.py::TestCqlsh::test_protocol_negotiation}} which is fixed in my
[dtest branch|https://github.com/beobal/cassandra-dtest/tree/14973]
* the jvm_upgrade_dtest failure,
{{MixedModeReadTest::mixedModeReadColumnSubsetDigestCheck}} is addressed by
CASSANDRA-16415
Otherwise, the results so far look pretty reasonable.
> Bring v5 driver out of beta, introduce v6 before 4.0 release is cut
> ---
>
> Key: CASSANDRA-14973
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14973
> Project: Cassandra
> Issue Type: Task
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Urgent
> Labels: protocolv5
> Fix For: 4.0-beta
>
>
> In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced
> Beta flag for v5 protocol. However, up till now, v5 is in beta both in
> [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46]
> and in
> [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35].
>
> Before the final 4.0 release is cut, we need to bring v5 out of beta and
> finalise native protocol spec, and start bringing all new changes to v6
> protocol, which will be in beta.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16463) high and critical CVEs io.netty to 4.1.42.Final to fix critical and high vulnerabilities
[ https://issues.apache.org/jira/browse/CASSANDRA-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhargav Joshi updated CASSANDRA-16463: -- Resolution: (was: Invalid) Status: Open (was: Resolved) This is not limited to Datastax, CVE is part of io.netty bundle within cassandra libraries > high and critical CVEs io.netty to 4.1.42.Final to fix critical and high > vulnerabilities > > > Key: CASSANDRA-16463 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16463 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Bhargav Joshi >Priority: High > > Repository | Tag | CVE ID | Severity | Packages | Source Package | Package > Version | Fix Status > -- | -- | -- | -- | -- | -- | -- | -- > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20445 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20444 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-16869 | high | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.42.Final -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16463) high and critical CVEs io.netty to 4.1.42.Final to fix critical and high vulnerabilities
[ https://issues.apache.org/jira/browse/CASSANDRA-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289114#comment-17289114 ] Bhargav Joshi commented on CASSANDRA-16463: --- |Registry|Repository|Tag|Id|Distro|CVE ID|Severity|Packages|Package Version|Fix Status| | |cassandra|3.11.10|sha256:87779a1dd1f7fa01317fab42d888150c4340369c26cb8904c3a14abeea117447|Ubuntu-focal|CVE-2019-20445|critical|io.netty_netty-all|4.0.44.Final|fixed in 4.1.44| | |cassandra|3.11.10|sha256:87779a1dd1f7fa01317fab42d888150c4340369c26cb8904c3a14abeea117447|Ubuntu-focal|CVE-2019-20444|critical|io.netty_netty-all|4.0.44.Final|fixed in 4.1.44| > high and critical CVEs io.netty to 4.1.42.Final to fix critical and high > vulnerabilities > > > Key: CASSANDRA-16463 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16463 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Bhargav Joshi >Priority: High > > Repository | Tag | CVE ID | Severity | Packages | Source Package | Package > Version | Fix Status > -- | -- | -- | -- | -- | -- | -- | -- > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20445 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20444 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-16869 | high | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.42.Final -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16463) high and critical CVEs io.netty to 4.1.42.Final to fix critical and high vulnerabilities
[ https://issues.apache.org/jira/browse/CASSANDRA-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289115#comment-17289115 ] Bhargav Joshi commented on CASSANDRA-16463: --- Cassandra on dockerhub also has the same CVEs > high and critical CVEs io.netty to 4.1.42.Final to fix critical and high > vulnerabilities > > > Key: CASSANDRA-16463 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16463 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Bhargav Joshi >Priority: High > > Repository | Tag | CVE ID | Severity | Packages | Source Package | Package > Version | Fix Status > -- | -- | -- | -- | -- | -- | -- | -- > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20445 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-20444 | critical | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.44 > datastax/cassandra-mgmtapi-3_11_7 | v0.1.22 | CVE-2019-16869 | high | > io.netty_netty-all | | 4.0.44.Final | fixed in 4.1.42.Final -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16466) Cannot start multiple repair sessions over the same sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289106#comment-17289106
]
Brandon Williams commented on CASSANDRA-16466:
--
Please note that jira is not a discussion forum. If you are trying to file a
bug, please add the necessary information, such as the version.
That said, you absolutely have another repair session running. I recommend
using a location designed for discussion to investigate further such as slack
or the user ML: https://cassandra.apache.org/community/ since is not likely to
be a bug.
> Cannot start multiple repair sessions over the same sstables
>
>
> Key: CASSANDRA-16466
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16466
> Project: Cassandra
> Issue Type: Bug
>Reporter: Dm Yu
>Priority: Normal
>
> When starting the repair (cassandra 3.11.9, _nodetool repair -full_) an
> error occurs
> {quote}ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585
> ActiveRepairService.java:561 - Cannot start multiple repair sessions over the
> same sstables
> ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585 Validator.java:268 -
> Failed creating a merkle tree for [repair
> #c71cbc30-75bd-11eb-b3bb-b73fcd17890a
> java.lang.RuntimeException: Cannot start multiple repair sessions over the
> same sstables
> {quote}
> but there is no active repair processes.
> {quote}nodetool compactionstats
> pending tasks: 0
> nodetool netstats
> Mode: NORMAL
> Not sending any streams.
> Read Repair Statistics:
> Attempted: 588586868
> Mismatch (Blocking): 1460468
> Mismatch (Background): 8022504
> Pool Name Active Pending Completed Dropped
> Large messages n/a 0 21545142 3
> Small messages n/a 0 59512600068 209
> Gossip messages n/a 0 5991347 488
> {quote}
> How can i start node repair?
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16466) Cannot start multiple repair sessions over the same sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16466:
-
Resolution: Incomplete
Status: Resolved (was: Triage Needed)
> Cannot start multiple repair sessions over the same sstables
>
>
> Key: CASSANDRA-16466
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16466
> Project: Cassandra
> Issue Type: Bug
>Reporter: Dm Yu
>Priority: Normal
>
> When starting the repair (cassandra 3.11.9, _nodetool repair -full_) an
> error occurs
> {quote}ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585
> ActiveRepairService.java:561 - Cannot start multiple repair sessions over the
> same sstables
> ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585 Validator.java:268 -
> Failed creating a merkle tree for [repair
> #c71cbc30-75bd-11eb-b3bb-b73fcd17890a
> java.lang.RuntimeException: Cannot start multiple repair sessions over the
> same sstables
> {quote}
> but there is no active repair processes.
> {quote}nodetool compactionstats
> pending tasks: 0
> nodetool netstats
> Mode: NORMAL
> Not sending any streams.
> Read Repair Statistics:
> Attempted: 588586868
> Mismatch (Blocking): 1460468
> Mismatch (Background): 8022504
> Pool Name Active Pending Completed Dropped
> Large messages n/a 0 21545142 3
> Small messages n/a 0 59512600068 209
> Gossip messages n/a 0 5991347 488
> {quote}
> How can i start node repair?
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16466) Cannot start multiple repair sessions over the same sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dm Yu updated CASSANDRA-16466:
--
Description:
When starting the repair (cassandra 3.11.9, _nodetool repair -full_) an error
occurs
{quote}ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585
ActiveRepairService.java:561 - Cannot start multiple repair sessions over the
same sstables
ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585 Validator.java:268 -
Failed creating a merkle tree for [repair #c71cbc30-75bd-11eb-b3bb-b73fcd17890a
java.lang.RuntimeException: Cannot start multiple repair sessions over the
same sstables
{quote}
but there is no active repair processes.
{quote}nodetool compactionstats
pending tasks: 0
nodetool netstats
Mode: NORMAL
Not sending any streams.
Read Repair Statistics:
Attempted: 588586868
Mismatch (Blocking): 1460468
Mismatch (Background): 8022504
Pool Name Active Pending Completed Dropped
Large messages n/a 0 21545142 3
Small messages n/a 0 59512600068 209
Gossip messages n/a 0 5991347 488
{quote}
How can i start node repair?
was:
When starting the repair (_nodetool repair -full_) an error occurs
{quote}ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585
ActiveRepairService.java:561 - Cannot start multiple repair sessions over the
same sstables
ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585 Validator.java:268 -
Failed creating a merkle tree for [repair #c71cbc30-75bd-11eb-b3bb-b73fcd17890a
java.lang.RuntimeException: Cannot start multiple repair sessions over the same
sstables
{quote}
but there is no active repair processes.
{quote}nodetool compactionstats
pending tasks: 0
nodetool netstats
Mode: NORMAL
Not sending any streams.
Read Repair Statistics:
Attempted: 588586868
Mismatch (Blocking): 1460468
Mismatch (Background): 8022504
Pool Name Active Pending Completed Dropped
Large messages n/a 0 21545142 3
Small messages n/a 0 59512600068 209
Gossip messages n/a 0 5991347 488
{quote}
How can i start node repair?
> Cannot start multiple repair sessions over the same sstables
>
>
> Key: CASSANDRA-16466
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16466
> Project: Cassandra
> Issue Type: Bug
>Reporter: Dm Yu
>Priority: Normal
>
> When starting the repair (cassandra 3.11.9, _nodetool repair -full_) an
> error occurs
> {quote}ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585
> ActiveRepairService.java:561 - Cannot start multiple repair sessions over the
> same sstables
> ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585 Validator.java:268 -
> Failed creating a merkle tree for [repair
> #c71cbc30-75bd-11eb-b3bb-b73fcd17890a
> java.lang.RuntimeException: Cannot start multiple repair sessions over the
> same sstables
> {quote}
> but there is no active repair processes.
> {quote}nodetool compactionstats
> pending tasks: 0
> nodetool netstats
> Mode: NORMAL
> Not sending any streams.
> Read Repair Statistics:
> Attempted: 588586868
> Mismatch (Blocking): 1460468
> Mismatch (Background): 8022504
> Pool Name Active Pending Completed Dropped
> Large messages n/a 0 21545142 3
> Small messages n/a 0 59512600068 209
> Gossip messages n/a 0 5991347 488
> {quote}
> How can i start node repair?
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16466) Cannot start multiple repair sessions over the same sstables
Dm Yu created CASSANDRA-16466:
-
Summary: Cannot start multiple repair sessions over the same
sstables
Key: CASSANDRA-16466
URL: https://issues.apache.org/jira/browse/CASSANDRA-16466
Project: Cassandra
Issue Type: Bug
Reporter: Dm Yu
When starting the repair (_nodetool repair -full_) an error occurs
{quote}ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585
ActiveRepairService.java:561 - Cannot start multiple repair sessions over the
same sstables
ERROR [ValidationExecutor:87] 2021-02-23 09:59:11,585 Validator.java:268 -
Failed creating a merkle tree for [repair #c71cbc30-75bd-11eb-b3bb-b73fcd17890a
java.lang.RuntimeException: Cannot start multiple repair sessions over the same
sstables
{quote}
but there is no active repair processes.
{quote}nodetool compactionstats
pending tasks: 0
nodetool netstats
Mode: NORMAL
Not sending any streams.
Read Repair Statistics:
Attempted: 588586868
Mismatch (Blocking): 1460468
Mismatch (Background): 8022504
Pool Name Active Pending Completed Dropped
Large messages n/a 0 21545142 3
Small messages n/a 0 59512600068 209
Gossip messages n/a 0 5991347 488
{quote}
How can i start node repair?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16428) Fix selections of JDKs in debian docker images on arm64
[
https://issues.apache.org/jira/browse/CASSANDRA-16428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289102#comment-17289102
]
Brandon Williams commented on CASSANDRA-16428:
--
[~RenhaiZhao] Mck is on vacation this week, but he'll get to it when he gets
back, everything is good here! Thanks for your review.
> Fix selections of JDKs in debian docker images on arm64
> ---
>
> Key: CASSANDRA-16428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16428
> Project: Cassandra
> Issue Type: Task
> Components: Build, Packaging
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
>
> The debian docker
> [image|https://github.com/apache/cassandra-builds/blob/trunk/docker/buster-image.docker]
> used by the
> [cassandra-deb-packaging.sh|https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-deb-packaging.sh]
> tries to set the jdk like
> {code}
> update-java-alternatives --set java-1.8.0-openjdk-amd64
> {code}
> This won't work on arm64.
> Suggestion is to replace it with the following:
> {code}
> update-java-alternatives --set $(update-java-alternatives -l | cut -d" " -f1
> | grep java-1.8)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”
[
https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289101#comment-17289101
]
Brandon Williams commented on CASSANDRA-16381:
--
Jenkins running
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch/395/]
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”
[
https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289098#comment-17289098
]
Adam Holmberg edited comment on CASSANDRA-16381 at 2/23/21, 2:13 PM:
-
argh. I was in a rush and forgot the circle config. Thanks Berenguer. Will get
back with that.
(another run is started at the same link)
was (Author: aholmber):
argh. I was in a rush and forgot the circle config. Thanks Berenguer. Will get
back with that.
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16381) nodetool removenode error “Conflicting replica added”
[
https://issues.apache.org/jira/browse/CASSANDRA-16381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289098#comment-17289098
]
Adam Holmberg commented on CASSANDRA-16381:
---
argh. I was in a rush and forgot the circle config. Thanks Berenguer. Will get
back with that.
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16443:
Status: Ready to Commit (was: Review In Progress)
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0-beta
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
> org.apache.cassandra.config.EncryptionOptions.(EncryptionOptions.java:242)
> at org.apache.cassandra.config.Config.(Config.java:280)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> at
> org.yaml.snakeyaml.constructor.BaseConstructor.newInstance(BaseConstructor.java:330)
> at
> org.yaml.snakeyaml.constructor.BaseConstructor.newInstance(BaseConstructor.java:308)
> at
>
[jira] [Comment Edited] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289094#comment-17289094
]
Ekaterina Dimitrova edited comment on CASSANDRA-16443 at 2/23/21, 1:56 PM:
---
When I pointed you there I was responding to a different question but I believe
we cleaned the topic on Slack. Yes, the merge happens on a per second
resolution.
I believe this one is ready to commit if there are no other outstanding
questions?
was (Author: e.dimitrova):
When I pointed you there I was responding to a different question but I believe
we cleaned the topic on Slack. Yes, the merge happens per second resolution.
I believe this one is ready to commit if there are no other outstanding
questions?
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0-beta
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
> org.apache.cassandra.config.EncryptionOptions.(EncryptionOptions.java:242)
> at org.apache.cassandra.config.Config.(Config.java:280)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
>
[jira] [Commented] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289094#comment-17289094
]
Ekaterina Dimitrova commented on CASSANDRA-16443:
-
When I pointed you there I was responding to a different question but I believe
we cleaned the topic on Slack. Yes, the merge happens per second resolution.
I believe this one is ready to commit if there are no other outstanding
questions?
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0-beta
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
> org.apache.cassandra.config.EncryptionOptions.(EncryptionOptions.java:242)
> at org.apache.cassandra.config.Config.(Config.java:280)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> at
>
[jira] [Updated] (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
]
Brandon Williams updated CASSANDRA-16381:
-
Reviewers: Berenguer Blasi, Brandon Williams (was: Berenguer Blasi)
> 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: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: dtest.tar.bz2, node1.tar.bz2, node2.tar.bz2,
> node3.tar.bz2
>
>
> 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
> __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 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 ’.++ 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14973) Bring v5 driver out of beta, introduce v6 before 4.0 release is cut
[ https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289022#comment-17289022 ] Sam Tunnicliffe commented on CASSANDRA-14973: - Thanks [~ifesdjeen]. [~eduard.tudenhoefner]: now that the java and python drivers have been updated, I've switched the bundled artifacts to ones built from the upstream source trees, referencing the sha1s. I've also rebased and squashed the C* changes, removing the temporary commits that were there for running CI. Do you have time to check out the latest changes? CI is currently running: [Circle|https://app.circleci.com/pipelines/github/beobal/cassandra?branch=14973-trunk], [Apache|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/394/] > Bring v5 driver out of beta, introduce v6 before 4.0 release is cut > --- > > Key: CASSANDRA-14973 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14973 > Project: Cassandra > Issue Type: Task >Reporter: Alex Petrov >Assignee: Sam Tunnicliffe >Priority: Urgent > Labels: protocolv5 > Fix For: 4.0-beta > > > In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced > Beta flag for v5 protocol. However, up till now, v5 is in beta both in > [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46] > and in > [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35]. > > Before the final 4.0 release is cut, we need to bring v5 out of beta and > finalise native protocol spec, and start bringing all new changes to v6 > protocol, which will be in beta. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14973) Bring v5 driver out of beta, introduce v6 before 4.0 release is cut
[ https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-14973: Reviewers: Alex Petrov, Eduard Tudenhoefner (was: Eduard Tudenhoefner) > Bring v5 driver out of beta, introduce v6 before 4.0 release is cut > --- > > Key: CASSANDRA-14973 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14973 > Project: Cassandra > Issue Type: Task >Reporter: Alex Petrov >Assignee: Sam Tunnicliffe >Priority: Urgent > Labels: protocolv5 > Fix For: 4.0-beta > > > In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced > Beta flag for v5 protocol. However, up till now, v5 is in beta both in > [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46] > and in > [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35]. > > Before the final 4.0 release is cut, we need to bring v5 out of beta and > finalise native protocol spec, and start bringing all new changes to v6 > protocol, which will be in beta. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16443) Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest testPartitionDeletionRowDeletionTie
[
https://issues.apache.org/jira/browse/CASSANDRA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289003#comment-17289003
]
Berenguer Blasi commented on CASSANDRA-16443:
-
Ok I _think_ this might be bc {{localDeletionTime}} has a resolution of
seconds. Hence {{AtomicBTreePartition.addAllWithSizeDeltaInternal() -> add() ->
add() -> superseeds()}} would merge/not merge on a seconds resolution.
> Fix flaky test org.apache.cassandra.db.SinglePartitionSliceCommandTest
> testPartitionDeletionRowDeletionTie
> --
>
> Key: CASSANDRA-16443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16443
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-beta5, 4.0-beta
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/225/jdk=jdk_11_latest,label=cassandra/testReport/junit/org.apache.cassandra.db/SinglePartitionSliceCommandTest/testPartitionDeletionRowDeletionTie/
> {code}
> Error Message
> Expected [Row[info=[ts=11] ]: c=1 | [v=1 ts=11]] but got [Row[info=[ts=11]
> del=deletedAt=10, localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> Stacktrace
> junit.framework.AssertionFailedError: Expected [Row[info=[ts=11] ]: c=1 |
> [v=1 ts=11]] but got [Row[info=[ts=11] del=deletedAt=10,
> localDeletion=1613085925 ]: c=1 | [v=1 ts=11]] expected:
> java.util.ArrayList<[[[v=1 ts=11]]]> but was: java.util.ArrayList<[[[v=1
> ts=11]]]>
> at
> org.apache.cassandra.db.SinglePartitionSliceCommandTest.testPartitionDeletionRowDeletionTie(SinglePartitionSliceCommandTest.java:382)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-02-11 23:25:22,114 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,117 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:/home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test/jdk/jdk_11_latest/label/cassandra/test/conf/cassandra.yaml
> DEBUG [main] 2021-02-11 23:25:22,196 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:417 -
> -Dio.netty.noUnsafe: false
> DEBUG [main] 2021-02-11 23:25:22,211 PlatformDependent0.java:897 - Java
> version: 11
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:130 -
> sun.misc.Unsafe.theUnsafe: available
> DEBUG [main] 2021-02-11 23:25:22,213 PlatformDependent0.java:154 -
> sun.misc.Unsafe.copyMemory: available
> DEBUG [main] 2021-02-11 23:25:22,214 PlatformDependent0.java:192 -
> java.nio.Buffer.address: available
> DEBUG [main] 2021-02-11 23:25:22,216 PlatformDependent0.java:266 - direct
> buffer constructor: unavailable
> java.lang.UnsupportedOperationException: Reflective setAccessible(true)
> disabled
> at
> io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
> at
> io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:238)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> io.netty.util.internal.PlatformDependent0.(PlatformDependent0.java:232)
> at
> io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:293)
> at
> io.netty.util.internal.PlatformDependent.(PlatformDependent.java:92)
> at io.netty.handler.ssl.OpenSsl.(OpenSsl.java:124)
> at
> org.apache.cassandra.security.SSLFactory.(SSLFactory.java:100)
> at
> org.apache.cassandra.config.EncryptionOptions.(EncryptionOptions.java:242)
> at org.apache.cassandra.config.Config.(Config.java:280)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> at
>
