[jira] [Commented] (CASSANDRA-19124) Test failure: ConsistentBootstrapTest#coordinatorIsBehindTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794560#comment-17794560
]
Alex Petrov commented on CASSANDRA-19124:
-
I think the root cause is the same as [CASSANDRA-19123].
> Test failure: ConsistentBootstrapTest#coordinatorIsBehindTest
> --
>
> Key: CASSANDRA-19124
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19124
> Project: Cassandra
> Issue Type: Bug
>Reporter: Alex Petrov
>Priority: Normal
>
> {code}
> Forked Java VM exited abnormally. Please note the time in the report does not
> reflect the time until the VM exit.
> junit.framework.AssertionFailedError: Forked Java VM exited abnormally.
> Please note the time in the report does not reflect the time until the VM
> exit.
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.base/java.util.Vector.forEach(Vector.java:1394)
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.base/java.util.Vector.forEach(Vector.java:1394)
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> 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)
>
> at java.base/java.util.Vector.forEach(Vector.java:1394)
> 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)
>
> at org.apache.cassandra.anttasks.TestHelper.execute(TestHelper.java:53)
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.base/java.util.Vector.forEach(Vector.java:1394)
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19125) Investigate increased memory usage in tests with TCM
[ https://issues.apache.org/jira/browse/CASSANDRA-19125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19125: Attachment: ci_summary.html result_details.tar.gz > Investigate increased memory usage in tests with TCM > > > Key: CASSANDRA-19125 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19125 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.1-alpha1 > > Attachments: ci_summary.html, result_details.tar.gz > > > A few tests started failing with OOM after we committed TCM - we should > investigate why/if we use more memory -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19125) Investigate increased memory usage in tests with TCM
[ https://issues.apache.org/jira/browse/CASSANDRA-19125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19125: Test and Documentation Plan: ci run Status: Patch Available (was: Open) Looks like when enabling only Feature.GOSSIP (not NETWORK) in jvm dtests we also start MessagingService for no apparent reason, and when shutting down we don't fully shut down the started MS. https://github.com/krummas/cassandra/commits/marcuse/19125 > Investigate increased memory usage in tests with TCM > > > Key: CASSANDRA-19125 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19125 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.1-alpha1 > > > A few tests started failing with OOM after we committed TCM - we should > investigate why/if we use more memory -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19125) Investigate increased memory usage in tests with TCM
[ https://issues.apache.org/jira/browse/CASSANDRA-19125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19125: Change Category: Quality Assurance Complexity: Normal Component/s: Test/dtest/java Fix Version/s: 5.1-alpha1 Status: Open (was: Triage Needed) > Investigate increased memory usage in tests with TCM > > > Key: CASSANDRA-19125 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19125 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java >Reporter: Marcus Eriksson >Priority: Normal > Fix For: 5.1-alpha1 > > > A few tests started failing with OOM after we committed TCM - we should > investigate why/if we use more memory -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19126) Streaming appears to be incompatible with different storage_compatibility_mode settings
[
https://issues.apache.org/jira/browse/CASSANDRA-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794551#comment-17794551
]
Jacek Lewandowski commented on CASSANDRA-19126:
---
I doubt this is the best time to investigate that but I'm wondering why
acquiring a connection for messaging and for streaming is implemented
differently? What I've commented above is just a single manifestation of this
problem
> Streaming appears to be incompatible with different
> storage_compatibility_mode settings
> ---
>
> Key: CASSANDRA-19126
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19126
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming, Legacy/Streaming and Messaging,
> Messaging/Internode, Tool/bulk load
>Reporter: Branimir Lambov
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> In particular, SSTableLoader appears to be incompatible with
> storage_compatibility_mode: NONE, which manifests as a failure of
> {{org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest}}
> when the flag is turned on (found during CASSANDRA-18753 testing). Setting
> {{storage_compatibility_mode: NONE}} in the tool configuration yaml does not
> help (according to the docs, this setting is not picked up).
> This is likely a bigger problem as the acceptable streaming version for C* 5
> is 12 only in legacy mode and 13 only in none, i.e. two C* 5 nodes do not
> appear to be able to stream with each other if their setting for the
> compatibility mode is different.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19094) Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794550#comment-17794550
]
Alex Petrov commented on CASSANDRA-19094:
-
Trunk PR
> Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
> --
>
> Key: CASSANDRA-19094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19094
> Project: Cassandra
> Issue Type: Bug
> Components: Test/fuzz
>Reporter: Michael Semb Wever
>Assignee: Alex Petrov
>Priority: Normal
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> Seen in j11_simulator_dtests in CASSANDRA-19034
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/259/workflows/f343d3e3-00cf-4e13-bb4d-bbfff1d3658c/jobs/21101/tests
> {noformat}
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:537)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1098)
> at
> org.apache.cassandra.simulator.ClusterSimulation.close(ClusterSimulation.java:854)
> at
> org.apache.cassandra.simulator.test.SimulationTestBase.simulate(SimulationTestBase.java:206)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.simulate(HarrySimulatorTest.java:361)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest(HarrySimulatorTest.java:135)
> 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)
> Caused by: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:254)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:529)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$47(Instance.java:978)
> at
> org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
> at
> org.apache.cassandra.simulator.systems.SimulatedExecution$NoIntercept$1Run.run(SimulatedExecution.java:82)
> at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$InterceptingPooledExecutor$WaitingThread.lambda$new$1(InterceptingExecutor.java:318)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$46(Instance.java:972)
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$async$10(IsolatedExecutor.java:156)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.hints.HintsService.shutdownBlocking(HintsService.java:282)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$17(Instance.java:901)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$parallelRun$52(Instance.java:1196)
> Caused by: java.lang.OutOfMemoryError: Direct buffer memory
> at
[jira] [Updated] (CASSANDRA-19094) Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19094:
Bug Category: Parent values: Degradation(12984)Level 1 values: Other
Exception(12998)
Complexity: Normal
Component/s: Test/fuzz
Discovered By: Fuzz Test
Severity: Normal
Status: Open (was: Triage Needed)
> Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
> --
>
> Key: CASSANDRA-19094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19094
> Project: Cassandra
> Issue Type: Bug
> Components: Test/fuzz
>Reporter: Michael Semb Wever
>Assignee: Alex Petrov
>Priority: Normal
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> Seen in j11_simulator_dtests in CASSANDRA-19034
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/259/workflows/f343d3e3-00cf-4e13-bb4d-bbfff1d3658c/jobs/21101/tests
> {noformat}
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:537)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1098)
> at
> org.apache.cassandra.simulator.ClusterSimulation.close(ClusterSimulation.java:854)
> at
> org.apache.cassandra.simulator.test.SimulationTestBase.simulate(SimulationTestBase.java:206)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.simulate(HarrySimulatorTest.java:361)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest(HarrySimulatorTest.java:135)
> 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)
> Caused by: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:254)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:529)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$47(Instance.java:978)
> at
> org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
> at
> org.apache.cassandra.simulator.systems.SimulatedExecution$NoIntercept$1Run.run(SimulatedExecution.java:82)
> at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$InterceptingPooledExecutor$WaitingThread.lambda$new$1(InterceptingExecutor.java:318)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$46(Instance.java:972)
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$async$10(IsolatedExecutor.java:156)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.hints.HintsService.shutdownBlocking(HintsService.java:282)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$17(Instance.java:901)
> at
>
[jira] [Updated] (CASSANDRA-19094) Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19094:
Attachment: ci_summary.html
result_details.tar.gz
> Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
> --
>
> Key: CASSANDRA-19094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19094
> Project: Cassandra
> Issue Type: Bug
> Components: Test/fuzz
>Reporter: Michael Semb Wever
>Assignee: Alex Petrov
>Priority: Normal
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> Seen in j11_simulator_dtests in CASSANDRA-19034
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/259/workflows/f343d3e3-00cf-4e13-bb4d-bbfff1d3658c/jobs/21101/tests
> {noformat}
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:537)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1098)
> at
> org.apache.cassandra.simulator.ClusterSimulation.close(ClusterSimulation.java:854)
> at
> org.apache.cassandra.simulator.test.SimulationTestBase.simulate(SimulationTestBase.java:206)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.simulate(HarrySimulatorTest.java:361)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest(HarrySimulatorTest.java:135)
> 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)
> Caused by: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:254)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:529)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$47(Instance.java:978)
> at
> org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
> at
> org.apache.cassandra.simulator.systems.SimulatedExecution$NoIntercept$1Run.run(SimulatedExecution.java:82)
> at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$InterceptingPooledExecutor$WaitingThread.lambda$new$1(InterceptingExecutor.java:318)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$46(Instance.java:972)
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$async$10(IsolatedExecutor.java:156)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.hints.HintsService.shutdownBlocking(HintsService.java:282)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$17(Instance.java:901)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$parallelRun$52(Instance.java:1196)
> Caused by: java.lang.OutOfMemoryError: Direct buffer memory
> at
[jira] [Updated] (CASSANDRA-19094) Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19094:
Test and Documentation Plan: Covered by existing tests
Status: Patch Available (was: Open)
> Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
> --
>
> Key: CASSANDRA-19094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19094
> Project: Cassandra
> Issue Type: Bug
> Components: Test/fuzz
>Reporter: Michael Semb Wever
>Assignee: Alex Petrov
>Priority: Normal
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> Seen in j11_simulator_dtests in CASSANDRA-19034
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/259/workflows/f343d3e3-00cf-4e13-bb4d-bbfff1d3658c/jobs/21101/tests
> {noformat}
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:537)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1098)
> at
> org.apache.cassandra.simulator.ClusterSimulation.close(ClusterSimulation.java:854)
> at
> org.apache.cassandra.simulator.test.SimulationTestBase.simulate(SimulationTestBase.java:206)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.simulate(HarrySimulatorTest.java:361)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest(HarrySimulatorTest.java:135)
> 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)
> Caused by: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:254)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:529)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$47(Instance.java:978)
> at
> org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
> at
> org.apache.cassandra.simulator.systems.SimulatedExecution$NoIntercept$1Run.run(SimulatedExecution.java:82)
> at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$InterceptingPooledExecutor$WaitingThread.lambda$new$1(InterceptingExecutor.java:318)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$46(Instance.java:972)
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$async$10(IsolatedExecutor.java:156)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.hints.HintsService.shutdownBlocking(HintsService.java:282)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$17(Instance.java:901)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$parallelRun$52(Instance.java:1196)
> Caused by: java.lang.OutOfMemoryError:
[jira] [Updated] (CASSANDRA-19058) Test Failure: org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest-_jdk11
[ https://issues.apache.org/jira/browse/CASSANDRA-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-19058: Test and Documentation Plan: Covered by existing tests Status: Patch Available (was: In Progress) > Test Failure: > org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest-_jdk11 > > > Key: CASSANDRA-19058 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19058 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Sam Tunnicliffe >Assignee: Alex Petrov >Priority: Normal > Fix For: 5.1-alpha1 > > Time Spent: 10m > Remaining Estimate: 0h > > butler shows this as failing on J17 but here we see it fail on J11 > [https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20463/tests] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19126) Streaming appears to be incompatible with different storage_compatibility_mode settings
[
https://issues.apache.org/jira/browse/CASSANDRA-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794298#comment-17794298
]
Jacek Lewandowski edited comment on CASSANDRA-19126 at 12/8/23 7:02 AM:
Reading the exception, it looks like there is also a minor problem of
incorrectly handling (actually lack of handling) non-success result in
{{NettyStreamingConnectionFactory}}.
was (Author: jlewandowski):
Reading the exception, it looks like there is also a minor problem of
incorrectly handling (actually lack of handling) non-success result in
{{OutboundConnectionInitiator}}.
> Streaming appears to be incompatible with different
> storage_compatibility_mode settings
> ---
>
> Key: CASSANDRA-19126
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19126
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming, Legacy/Streaming and Messaging,
> Messaging/Internode, Tool/bulk load
>Reporter: Branimir Lambov
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> In particular, SSTableLoader appears to be incompatible with
> storage_compatibility_mode: NONE, which manifests as a failure of
> {{org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest}}
> when the flag is turned on (found during CASSANDRA-18753 testing). Setting
> {{storage_compatibility_mode: NONE}} in the tool configuration yaml does not
> help (according to the docs, this setting is not picked up).
> This is likely a bigger problem as the acceptable streaming version for C* 5
> is 12 only in legacy mode and 13 only in none, i.e. two C* 5 nodes do not
> appear to be able to stream with each other if their setting for the
> compatibility mode is different.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19031: Fix bulk writing when using identifiers that need quotes [cassandra-analytics]
frankgh commented on PR #20: URL: https://github.com/apache/cassandra-analytics/pull/20#issuecomment-1846610941 > lgtm overall. A few nits. Feel free to ignore. Thanks for the review. I've addressed your comments. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19031: Fix bulk writing when using identifiers that need quotes [cassandra-analytics]
frankgh commented on code in PR #20: URL: https://github.com/apache/cassandra-analytics/pull/20#discussion_r1419972095 ## cassandra-analytics-core/src/test/java/org/apache/cassandra/spark/bulkwriter/TableSchemaTest.java: ## @@ -231,4 +234,10 @@ private TableSchemaTestCommon.MockTableSchemaBuilder getValidSchemaBuilder() .withWriteMode(WriteMode.INSERT) .withDataFrameSchema(validDataFrameSchema); } + +// Removes the unique table name to make validation consistent +private static String replaceTableName(String statement) Review Comment: table Id might cause confusion with Cassandra's table ID. I will rename it to `trimUniqueTableName` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19031: Fix bulk writing when using identifiers that need quotes [cassandra-analytics]
frankgh commented on code in PR #20:
URL:
https://github.com/apache/cassandra-analytics/pull/20#discussion_r1419970047
##
cassandra-analytics-integration-tests/src/test/java/org/apache/cassandra/analytics/QuoteIdentifiersWriteTest.java:
##
@@ -0,0 +1,171 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+package org.apache.cassandra.analytics;
+
+import java.nio.ByteBuffer;
+import java.nio.charset.StandardCharsets;
+import java.util.Arrays;
+import java.util.Iterator;
+import java.util.List;
+import java.util.Set;
+import java.util.stream.Collectors;
+import java.util.stream.IntStream;
+import java.util.stream.LongStream;
+
+import com.google.common.collect.ImmutableMap;
+import org.junit.jupiter.api.extension.ExtendWith;
+
+import io.vertx.junit5.VertxExtension;
+import org.apache.cassandra.distributed.api.ConsistencyLevel;
+import org.apache.cassandra.sidecar.testing.QualifiedName;
+import org.apache.cassandra.testing.CassandraIntegrationTest;
+import org.apache.spark.SparkContext;
+import org.apache.spark.api.java.JavaRDD;
+import org.apache.spark.api.java.JavaSparkContext;
+import org.apache.spark.api.java.function.Function2;
+import org.apache.spark.sql.Dataset;
+import org.apache.spark.sql.Row;
+import org.apache.spark.sql.RowFactory;
+import org.apache.spark.sql.SQLContext;
+import org.apache.spark.sql.SparkSession;
+import org.apache.spark.sql.types.StructType;
+
+import static org.apache.spark.sql.types.DataTypes.BinaryType;
+import static org.apache.spark.sql.types.DataTypes.LongType;
+import static org.assertj.core.api.Assertions.assertThat;
+
+/**
+ * Tests the bulk writer behavior when requiring quoted identifiers for
keyspace, table name, and column names.
+ *
+ * These tests exercise a full integration test, which includes testing
Sidecar behavior when dealing with quoted
+ * identifiers.
+ */
+@ExtendWith(VertxExtension.class)
+class QuoteIdentifiersWriteTest extends SparkIntegrationTestBase
+{
+static final int ROW_COUNT = 10_000;
+
+@CassandraIntegrationTest(nodesPerDc = 3, gossip = true)
Review Comment:
good point, we don't need 3 instances. I will lower it to 1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19031: Fix bulk writing when using identifiers that need quotes [cassandra-analytics]
frankgh commented on code in PR #20:
URL:
https://github.com/apache/cassandra-analytics/pull/20#discussion_r1419969685
##
cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/CassandraClusterInfo.java:
##
@@ -535,6 +548,15 @@ protected boolean isReplacement(RingEntry ringEntry)
return false;
}
+protected CassandraBridge bridge()
+{
+if (bridge == null)
+{
+bridge = CassandraBridgeFactory.get(getLowestCassandraVersion());
Review Comment:
yeah, having a local cache saves look ups from the map. But lookups are fast
anyway, so I think we can remove the local field used as a cache
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19031: Fix bulk writing when using identifiers that need quotes [cassandra-analytics]
yifan-c commented on code in PR #20:
URL:
https://github.com/apache/cassandra-analytics/pull/20#discussion_r1419958662
##
cassandra-analytics-core/src/test/java/org/apache/cassandra/spark/bulkwriter/TableSchemaTest.java:
##
@@ -231,4 +234,10 @@ private TableSchemaTestCommon.MockTableSchemaBuilder
getValidSchemaBuilder()
.withWriteMode(WriteMode.INSERT)
.withDataFrameSchema(validDataFrameSchema);
}
+
+// Removes the unique table name to make validation consistent
+private static String replaceTableName(String statement)
Review Comment:
nit: how about rename to `trimTestTableId`?
##
cassandra-analytics-integration-tests/src/test/java/org/apache/cassandra/analytics/QuoteIdentifiersWriteTest.java:
##
@@ -0,0 +1,171 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+package org.apache.cassandra.analytics;
+
+import java.nio.ByteBuffer;
+import java.nio.charset.StandardCharsets;
+import java.util.Arrays;
+import java.util.Iterator;
+import java.util.List;
+import java.util.Set;
+import java.util.stream.Collectors;
+import java.util.stream.IntStream;
+import java.util.stream.LongStream;
+
+import com.google.common.collect.ImmutableMap;
+import org.junit.jupiter.api.extension.ExtendWith;
+
+import io.vertx.junit5.VertxExtension;
+import org.apache.cassandra.distributed.api.ConsistencyLevel;
+import org.apache.cassandra.sidecar.testing.QualifiedName;
+import org.apache.cassandra.testing.CassandraIntegrationTest;
+import org.apache.spark.SparkContext;
+import org.apache.spark.api.java.JavaRDD;
+import org.apache.spark.api.java.JavaSparkContext;
+import org.apache.spark.api.java.function.Function2;
+import org.apache.spark.sql.Dataset;
+import org.apache.spark.sql.Row;
+import org.apache.spark.sql.RowFactory;
+import org.apache.spark.sql.SQLContext;
+import org.apache.spark.sql.SparkSession;
+import org.apache.spark.sql.types.StructType;
+
+import static org.apache.spark.sql.types.DataTypes.BinaryType;
+import static org.apache.spark.sql.types.DataTypes.LongType;
+import static org.assertj.core.api.Assertions.assertThat;
+
+/**
+ * Tests the bulk writer behavior when requiring quoted identifiers for
keyspace, table name, and column names.
+ *
+ * These tests exercise a full integration test, which includes testing
Sidecar behavior when dealing with quoted
+ * identifiers.
+ */
+@ExtendWith(VertxExtension.class)
+class QuoteIdentifiersWriteTest extends SparkIntegrationTestBase
+{
+static final int ROW_COUNT = 10_000;
+
+@CassandraIntegrationTest(nodesPerDc = 3, gossip = true)
Review Comment:
Does the test quire 3 nodes? If not, let's use 1 node to consume less
resources.
##
cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/CassandraClusterInfo.java:
##
@@ -535,6 +548,15 @@ protected boolean isReplacement(RingEntry ringEntry)
return false;
}
+protected CassandraBridge bridge()
+{
+if (bridge == null)
+{
+bridge = CassandraBridgeFactory.get(getLowestCassandraVersion());
Review Comment:
In that case, why not just call
`CassandraBridgeFactory.get(getLowestCassandraVersion())`? Given the value
effectively cached already.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18232) Write docs for CEP-26 Unified Compaction Strategy (UCS)
[ https://issues.apache.org/jira/browse/CASSANDRA-18232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorina Poland updated CASSANDRA-18232: -- Test and Documentation Plan: n/a Status: Patch Available (was: In Progress) > Write docs for CEP-26 Unified Compaction Strategy (UCS) > --- > > Key: CASSANDRA-18232 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18232 > Project: Cassandra > Issue Type: New Feature > Components: Documentation >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: High > Fix For: 5.x > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18232) Write docs for CEP-26 Unified Compaction Strategy (UCS)
[ https://issues.apache.org/jira/browse/CASSANDRA-18232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorina Poland updated CASSANDRA-18232: -- Status: Needs Committer (was: Patch Available) > Write docs for CEP-26 Unified Compaction Strategy (UCS) > --- > > Key: CASSANDRA-18232 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18232 > Project: Cassandra > Issue Type: New Feature > Components: Documentation >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: High > Fix For: 5.x > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] Remove write option VALIDATE_SSTABLES to enforce validation [cassandra-analytics]
jyothsnakonisa opened a new pull request, #24: URL: https://github.com/apache/cassandra-analytics/pull/24 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] Cassandra 18852: Make bulk writer resilient to cluster resize events [cassandra-analytics]
arjunashok commented on code in PR #17:
URL:
https://github.com/apache/cassandra-analytics/pull/17#discussion_r1419770583
##
cassandra-analytics-integration-tests/src/test/java/org/apache/cassandra/analytics/ResiliencyTestBase.java:
##
@@ -0,0 +1,501 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.cassandra.analytics;
+
+import java.io.ByteArrayOutputStream;
+import java.io.Closeable;
+import java.io.File;
+import java.io.IOException;
+import java.io.InputStream;
+import java.io.OutputStream;
+import java.lang.management.ManagementFactory;
+import java.math.BigInteger;
+import java.nio.charset.Charset;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collection;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import java.util.concurrent.CountDownLatch;
+import java.util.concurrent.ExecutorService;
+import java.util.concurrent.Executors;
+import java.util.concurrent.atomic.AtomicReference;
+import java.util.function.BiConsumer;
+import java.util.function.Consumer;
+import java.util.function.Function;
+import java.util.regex.Pattern;
+import java.util.stream.Collectors;
+import java.util.stream.IntStream;
+
+import com.google.common.collect.ImmutableMap;
+import com.google.common.collect.Range;
+import org.junit.jupiter.api.BeforeAll;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import com.datastax.driver.core.ConsistencyLevel;
+import
o.a.c.analytics.sidecar.shaded.testing.adapters.base.StorageJmxOperations;
+import o.a.c.analytics.sidecar.shaded.testing.common.JmxClient;
+import o.a.c.analytics.sidecar.shaded.testing.common.data.QualifiedTableName;
+import org.apache.cassandra.distributed.UpgradeableCluster;
+import org.apache.cassandra.distributed.api.IInstanceConfig;
+import org.apache.cassandra.distributed.api.IUpgradeableInstance;
+import org.apache.cassandra.distributed.api.Row;
+import org.apache.cassandra.distributed.api.SimpleQueryResult;
+import org.apache.cassandra.distributed.api.TokenSupplier;
+import org.apache.cassandra.sidecar.testing.IntegrationTestBase;
+import org.apache.cassandra.spark.bulkwriter.DecoratedKey;
+import org.apache.cassandra.spark.bulkwriter.Tokenizer;
+import org.apache.cassandra.spark.common.schema.ColumnType;
+import org.apache.cassandra.spark.common.schema.ColumnTypes;
+import org.apache.cassandra.testing.CassandraIntegrationTest;
+import org.apache.cassandra.testing.ConfigurableCassandraTestContext;
+import scala.Tuple2;
+
+import static junit.framework.TestCase.assertTrue;
+import static
org.apache.cassandra.distributed.shared.NetworkTopology.dcAndRack;
+import static
org.apache.cassandra.distributed.shared.NetworkTopology.networkTopology;
+import static org.assertj.core.api.Assertions.assertThat;
+
+/**
+ * Base class for resiliency tests. Contains helper methods for data
generation and validation
+ */
+public abstract class ResiliencyTestBase extends IntegrationTestBase
+{
+public static final int rowCount = 1000;
+protected static final String retrieveRows = "select * from " +
TEST_KEYSPACE + ".%s";
+private static final Logger LOGGER =
LoggerFactory.getLogger(ResiliencyTestBase.class);
+private static final String createTableStmt = "create table if not exists
%s (id int, course text, marks int, primary key (id));";
+
+private final ExecutorService executorService =
Executors.newCachedThreadPool();
+private final AtomicReference errorOutput = new
AtomicReference<>();
+private final AtomicReference outputBytes = new
AtomicReference<>();
+
+
+public QualifiedTableName initializeSchema()
+{
+return initializeSchema(ImmutableMap.of("datacenter1", 1));
+}
+
+public QualifiedTableName initializeSchema(Map rf)
+{
+createTestKeyspace(rf);
+return createTestTable(createTableStmt);
+}
+
+public Set getDataForRange(Range range)
+{
+// Iterate through all data entries; filter only entries that belong
to range; convert to strings
+return generateExpectedData().stream()
+ .filter(t ->
range.contains(t._1().getToken()))
+
Re: [PR] Cassandra 18852: Make bulk writer resilient to cluster resize events [cassandra-analytics]
arjunashok commented on code in PR #17:
URL:
https://github.com/apache/cassandra-analytics/pull/17#discussion_r1419767330
##
cassandra-analytics-integration-framework/src/main/java/org/apache/cassandra/sidecar/testing/IntegrationTestBase.java:
##
@@ -231,4 +273,84 @@ protected void waitForKeyspaceAndTable(String
keyspaceName, String tableName)
String.format("Keyspace/table %s/%s did not become visible on all
sidecar instances",
keyspaceName, tableName));
}
+
+/**
+ * A {@link DnsResolver} instance used for tests that provides fast DNS
resolution, to avoid blocking
+ * DNS resolution at the JDK/OS-level.
+ *
+ * NOTE: The resolver assumes that the addresses are of the form
127.0.0.x, which is what is currently
+ * configured for integration tests.
+ */
+static class FastDnsResolver implements DnsResolver
Review Comment:
Renamed to `LocalhostResolver`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19031: Fix bulk writing when using identifiers that need quotes [cassandra-analytics]
frankgh commented on code in PR #20:
URL:
https://github.com/apache/cassandra-analytics/pull/20#discussion_r1419765509
##
cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/CassandraClusterInfo.java:
##
@@ -535,6 +548,15 @@ protected boolean isReplacement(RingEntry ringEntry)
return false;
}
+protected CassandraBridge bridge()
+{
+if (bridge == null)
+{
+bridge = CassandraBridgeFactory.get(getLowestCassandraVersion());
Review Comment:
underlying ConcurrentHashMap in factory guarantees single bridge
initialization here, so no need for synchronization
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-website) branch asf-site updated (3c2f600d -> 30faf9e4)
This is an automated email from the ASF dual-hosted git repository.
mck pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
discard 3c2f600d generate docs for afd7ef66
add 248a060d Adding blog post and text update to Catalyst page
add 30faf9e4 generate docs for 248a060d
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (3c2f600d)
\
N -- N -- N refs/heads/asf-site (30faf9e4)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
content/_/blog.html| 24
...ache-Cassandra-5.0-Features-Vector-Search.html} | 123 ++---
content/_/cassandra-catalyst-program.html | 2 +-
content/search-index.js| 2 +-
site-content/source/modules/ROOT/pages/blog.adoc | 23
...pache-Cassandra-5.0-Features-Vector-Search.adoc | 52 +
.../ROOT/pages/cassandra-catalyst-program.adoc | 2 +-
site-ui/build/ui-bundle.zip| Bin 4883726 -> 4883726
bytes
8 files changed, 160 insertions(+), 68 deletions(-)
copy content/_/blog/{ApacheCon-NA-2022-Call-for-Papers-Open.html =>
Apache-Cassandra-5.0-Features-Vector-Search.html} (69%)
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-5.0-Features-Vector-Search.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] Cassandra 18852: Make bulk writer resilient to cluster resize events [cassandra-analytics]
arjunashok commented on code in PR #17:
URL:
https://github.com/apache/cassandra-analytics/pull/17#discussion_r1419760670
##
cassandra-analytics-integration-tests/src/test/java/org/apache/cassandra/analytics/ResiliencyTestBase.java:
##
@@ -0,0 +1,384 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.cassandra.analytics;
+
+import java.io.IOException;
+import java.math.BigInteger;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collection;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import java.util.function.BiConsumer;
+import java.util.function.Consumer;
+import java.util.function.Function;
+import java.util.stream.Collectors;
+import java.util.stream.IntStream;
+
+import com.google.common.collect.ImmutableMap;
+import com.google.common.collect.Range;
+
+import com.datastax.driver.core.ConsistencyLevel;
+import
o.a.c.analytics.sidecar.shaded.testing.adapters.base.StorageJmxOperations;
+import o.a.c.analytics.sidecar.shaded.testing.common.JmxClient;
+import o.a.c.analytics.sidecar.shaded.testing.common.data.QualifiedTableName;
+import org.apache.cassandra.distributed.UpgradeableCluster;
+import org.apache.cassandra.distributed.api.IInstanceConfig;
+import org.apache.cassandra.distributed.api.IUpgradeableInstance;
+import org.apache.cassandra.distributed.api.Row;
+import org.apache.cassandra.distributed.api.SimpleQueryResult;
+import org.apache.cassandra.distributed.api.TokenSupplier;
+import org.apache.cassandra.sidecar.testing.IntegrationTestBase;
+import org.apache.cassandra.spark.KryoRegister;
+import org.apache.cassandra.spark.bulkwriter.BulkSparkConf;
+import org.apache.cassandra.spark.bulkwriter.DecoratedKey;
+import org.apache.cassandra.spark.bulkwriter.Tokenizer;
+import org.apache.cassandra.spark.common.schema.ColumnType;
+import org.apache.cassandra.spark.common.schema.ColumnTypes;
+import org.apache.cassandra.testing.CassandraIntegrationTest;
+import org.apache.cassandra.testing.ConfigurableCassandraTestContext;
+import org.apache.spark.SparkConf;
+import org.apache.spark.sql.DataFrameWriter;
+import org.apache.spark.sql.Dataset;
+import org.apache.spark.sql.RowFactory;
+import org.apache.spark.sql.SQLContext;
+import org.apache.spark.sql.SparkSession;
+import org.apache.spark.sql.types.StructType;
+import scala.Tuple2;
+
+import static junit.framework.TestCase.assertTrue;
+import static
org.apache.cassandra.distributed.shared.NetworkTopology.dcAndRack;
+import static
org.apache.cassandra.distributed.shared.NetworkTopology.networkTopology;
+import static org.apache.spark.sql.types.DataTypes.IntegerType;
+import static org.apache.spark.sql.types.DataTypes.StringType;
+import static org.assertj.core.api.Assertions.assertThat;
+
+/**
+ * Base class for resiliency tests. Contains helper methods for data
generation and validation
+ */
+public abstract class ResiliencyTestBase extends IntegrationTestBase
+{
+private static final String createTableStmt = "create table if not exists
%s (id int, course text, marks int, primary key (id));";
+protected static final String retrieveRows = "select * from " +
TEST_KEYSPACE + ".%s";
+public static final int rowCount = 1000;
+
+public QualifiedTableName initializeSchema()
+{
+return initializeSchema(ImmutableMap.of("datacenter1", 1));
+}
+
+public QualifiedTableName initializeSchema(Map rf)
+{
+createTestKeyspace(rf);
+return createTestTable(createTableStmt);
+}
+
+public SparkConf generateSparkConf()
+{
+SparkConf sparkConf = new SparkConf()
+ .setAppName("Integration test Spark Cassandra
Bulk Reader Job")
+ .set("spark.serializer",
"org.apache.spark.serializer.KryoSerializer")
+ .set("spark.master", "local[8,4]");
+BulkSparkConf.setupSparkConf(sparkConf, true);
+KryoRegister.setup(sparkConf);
+return sparkConf;
+}
+
+public SparkSession generateSparkSession(SparkConf sparkConf)
+{
+return SparkSession.builder()
+ .config(sparkConf)
+
[jira] [Updated] (CASSANDRA-19095) Test Failure: org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction
[
https://issues.apache.org/jira/browse/CASSANDRA-19095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-19095:
Fix Version/s: 5.0-rc
5.x
(was: 5.1-beta)
> Test Failure:
> org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction
> -
>
> Key: CASSANDRA-19095
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19095
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> Seen in j11_utests_compression in CASSANDRA-19034
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/259/workflows/f343d3e3-00cf-4e13-bb4d-bbfff1d3658c/jobs/21135/tests
> {noformat}
> junit.framework.AssertionFailedError:
> Expecting actual:
> 0.9667
> to be greater than or equal to:
> 0.99
> at
> org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction(VectorSegmentationTest.java:107)
> 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)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19095) Test Failure: org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction
[
https://issues.apache.org/jira/browse/CASSANDRA-19095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-19095:
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990)
Complexity: Normal
Component/s: CI
Discovered By: User Report
Severity: Normal
Status: Open (was: Triage Needed)
> Test Failure:
> org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction
> -
>
> Key: CASSANDRA-19095
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19095
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 5.1-beta
>
>
> Seen in j11_utests_compression in CASSANDRA-19034
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/259/workflows/f343d3e3-00cf-4e13-bb4d-bbfff1d3658c/jobs/21135/tests
> {noformat}
> junit.framework.AssertionFailedError:
> Expecting actual:
> 0.9667
> to be greater than or equal to:
> 0.99
> at
> org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction(VectorSegmentationTest.java:107)
> 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)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19095) Test Failure: org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction
[
https://issues.apache.org/jira/browse/CASSANDRA-19095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794472#comment-17794472
]
Ekaterina Dimitrova commented on CASSANDRA-19095:
-
Known issue from CASSANDRA-18715. It was reported that follow-up tickets will
be opened, though I think that was forgotten, maybe?
CC [~adelapena] , [~mikea]
> Test Failure:
> org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction
> -
>
> Key: CASSANDRA-19095
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19095
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 5.1-beta
>
>
> Seen in j11_utests_compression in CASSANDRA-19034
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/259/workflows/f343d3e3-00cf-4e13-bb4d-bbfff1d3658c/jobs/21135/tests
> {noformat}
> junit.framework.AssertionFailedError:
> Expecting actual:
> 0.9667
> to be greater than or equal to:
> 0.99
> at
> org.apache.cassandra.index.sai.cql.VectorSegmentationTest.testMultipleSegmentsForCompaction(VectorSegmentationTest.java:107)
> 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)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-java-driver) branch 4.x updated: Remove distributionManagement, the apache parent defines this for us
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch 4.x in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git The following commit(s) were added to refs/heads/4.x by this push: new 346cab5b3 Remove distributionManagement, the apache parent defines this for us 346cab5b3 is described below commit 346cab5b3e8a5f1888ba2633fa530c5934009ba0 Author: mck AuthorDate: Fri Dec 8 00:16:34 2023 +0100 Remove distributionManagement, the apache parent defines this for us --- pom.xml | 6 -- 1 file changed, 6 deletions(-) diff --git a/pom.xml b/pom.xml index 350d05184..221e1f69a 100644 --- a/pom.xml +++ b/pom.xml @@ -1004,12 +1004,6 @@ limitations under the License.]]> - - - ossrh - https://oss.sonatype.org/service/local/staging/deploy/maven2/ - - Apache 2 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r65931 - in /dev/cassandra/cassandra-java-driver: ./ 4.18.0/
Author: mck Date: Thu Dec 7 23:14:00 2023 New Revision: 65931 Log: Cassandra Java Driver 4.18.0 Added: dev/cassandra/cassandra-java-driver/4.18.0/ dev/cassandra/cassandra-java-driver/4.18.0/apache-cassandra-java-driver-4.18.0-source.tar.gz - copied unchanged from r65930, dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz dev/cassandra/cassandra-java-driver/4.18.0/apache-cassandra-java-driver-4.18.0-source.tar.gz.asc - copied unchanged from r65930, dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.asc dev/cassandra/cassandra-java-driver/4.18.0/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha256 - copied unchanged from r65930, dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha256 dev/cassandra/cassandra-java-driver/4.18.0/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha512 - copied unchanged from r65930, dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha512 dev/cassandra/cassandra-java-driver/4.18.0/apache-cassandra-java-driver-4.18.0.tar.gz - copied unchanged from r65930, dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz dev/cassandra/cassandra-java-driver/4.18.0/apache-cassandra-java-driver-4.18.0.tar.gz.asc - copied unchanged from r65930, dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.asc dev/cassandra/cassandra-java-driver/4.18.0/apache-cassandra-java-driver-4.18.0.tar.gz.sha256 - copied unchanged from r65930, dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.sha256 dev/cassandra/cassandra-java-driver/4.18.0/apache-cassandra-java-driver-4.18.0.tar.gz.sha512 - copied unchanged from r65930, dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.sha512 Removed: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.asc dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha256 dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha512 dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.asc dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.sha256 dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.sha512 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19182) IR may leak SSTables with pending repair when coming from streaming
[ https://issues.apache.org/jira/browse/CASSANDRA-19182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-19182: -- Bug Category: Parent values: Correctness(12982)Level 1 values: Recoverable Corruption / Loss(12986) Complexity: Challenging Discovered By: User Report Fix Version/s: 4.0.x 4.1.x 5.0.x 5.x Severity: Critical Assignee: David Capwell Status: Open (was: Triage Needed) > IR may leak SSTables with pending repair when coming from streaming > --- > > Key: CASSANDRA-19182 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19182 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Repair >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x > > > There is a race condition where SSTables from streaming may race with pending > repair cleanup in compaction causing us to cleanup the pending repair state > in compaction while the SSTables are being added to it; this leads to IR > failing in the future when those files get selected for repair. > This problem was hard to track down as the in-memory state was wiped, so we > don’t have any details. To better aid these types of investigation we should > make sure the repair vtables get updated when IR session failures are > submitted -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r65930 - /dev/cassandra/cassandra-java-driver/
Author: mck Date: Thu Dec 7 23:09:57 2023 New Revision: 65930 Log: Cassandra Java Driver 4.18.0 Added: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz (with props) dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.asc dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha256 dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha512 dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz (with props) dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.asc dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.sha256 dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.sha512 Added: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.asc == --- dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.asc (added) +++ dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.asc Thu Dec 7 23:09:57 2023 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmVyTT0ACgkQ6RM1134+ +h8sszA//d2RPvDy8hiqkA1dY0XjW47UCgidRhxHJOqoyvhelsb49lQkSnl7sfT43 +YRQqNu0eyYO+sAhRYccD6SjGou8uCz5dVwitXTBYJFfjVex6WKnmnF5VspRqiY9C +SU6isER8dKIu8BK7Bt70pJew99AUW+xZi4woRGWfIJuDIAJOX6IqZFri8o8H0V61 +aVUsRGnIj/5xnwGNtH0e1HzscD4lS1uCfm9DwCaYvsWC0cxPxhbA5gHSsW2AeJak +1zFBFLDGnUEb/6QoYeF60UGhyqdJOvpBvXkW6mWk+fdeNCtsptsCpHZRboKmCfI9 +j3cQWky1UXOAD5TyDSfKtkp1H/fwypS92W9pFXxGUHCayQf01ZMaWNDI4VrJhhND +o7FRi0bAK15i3l3vC3YfHdyJZo8g4q9hWayA/KLsI1fWwAUhY4FwEeuG3nIUm5Hy +MAsOpsKc2U+4Tciw2pM1z2AFYuxWw0LuB0uT8x03xZRyt7RMdNk2agEHvetvD7BR +ljO4CNey1RKQVemrRlyHtQ3/iNYWY+pgvx8pmZZtMK+ZZwEc7ulZWwz/prMRAK3V +aMHKCV3T0/Nf8u9fk54mU7Zg1qP+gKZbTCc8hcwWbWoU6mpbQkRX1SA/e3jXh6Sx +D4ghAIGkDTDJcEYzhyIcqWngj4xERHg9e+ZjmYtNPn+omPu+WQs= +=idpu +-END PGP SIGNATURE- Added: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha256 == --- dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha256 (added) +++ dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha256 Thu Dec 7 23:09:57 2023 @@ -0,0 +1 @@ +e60612af2c21147f9b26afa395e8c0892852ee412e30f4b03800324623df3c5a \ No newline at end of file Added: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha512 == --- dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha512 (added) +++ dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0-source.tar.gz.sha512 Thu Dec 7 23:09:57 2023 @@ -0,0 +1 @@ +f26e542c973b1253baf2e4ff5a88d884021dde9bee119e9ad4f8bcaff9a0d9b1783b088bd01b9d4adadce9185fe1364b3f6afd112c8bcb69d575cd527b588bb1 \ No newline at end of file Added: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.asc == --- dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.asc (added) +++ dev/cassandra/cassandra-java-driver/apache-cassandra-java-driver-4.18.0.tar.gz.asc Thu Dec 7 23:09:57 2023 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmVyTUEACgkQ6RM1134+ +h8uVOA/+LcniU0kU/q0Wk1KsJVc0LahveH1O1iWQDgWVxgdIm4E07ienQMJLZbwl +YhjzzhsnIMkrzNIghdQn44raYiANYiBb6yVlqY4CtUNT27NmFdWH5hf2LI8s/uoP +dtIagFlezy4tzvwTNXn287Yr1Sp27T/TYfW2HDUBh7pa0Gkp5yCBRKPFVkJOuwtz +gPl100YFLhmhpHsqv2fWUftShFFLeCiuPIM9QZfh0RR6B1v/G1030EUHHNE5YBpP +AUvUm84sjMrQQf+jHVL2hir0MRgYsXYzWtOsUDMmKDqe+5786XmJf0TA7SBnX3j7 +7n3J9xSyviJteZLwNef5aU5LiN+UflfFYXhpl8Zg2ocHB/W9CciVT3a0dtJx7xS2
[jira] [Updated] (CASSANDRA-18902) Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest.explicitEndpointIgnore
[ https://issues.apache.org/jira/browse/CASSANDRA-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18902: Reviewers: Ekaterina Dimitrova > Test failure: > org.apache.cassandra.distributed.test.MigrationCoordinatorTest.explicitEndpointIgnore > --- > > Key: CASSANDRA-18902 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18902 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 5.0-rc, 5.x > > > Repeated run from `cassandra-4.1` > [https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/941/workflows/46fc6cb7-135e-4862-b9d3-6996c0993de8] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-website) branch asf-staging updated (32d38213 -> 30faf9e4)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
discard 32d38213 generate docs for afd7ef66
add 248a060d Adding blog post and text update to Catalyst page
new 30faf9e4 generate docs for 248a060d
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (32d38213)
\
N -- N -- N refs/heads/asf-staging (30faf9e4)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
content/_/blog.html| 24
...ache-Cassandra-5.0-Features-Vector-Search.html} | 123 ++---
content/_/cassandra-catalyst-program.html | 2 +-
content/search-index.js| 2 +-
site-content/source/modules/ROOT/pages/blog.adoc | 23
...pache-Cassandra-5.0-Features-Vector-Search.adoc | 52 +
.../ROOT/pages/cassandra-catalyst-program.adoc | 2 +-
site-ui/build/ui-bundle.zip| Bin 4883726 -> 4883726
bytes
8 files changed, 160 insertions(+), 68 deletions(-)
copy content/_/blog/{ApacheCon-NA-2022-Call-for-Papers-Open.html =>
Apache-Cassandra-5.0-Features-Vector-Search.html} (69%)
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-5.0-Features-Vector-Search.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r65929 - /dev/cassandra/cassandra-java-driver/
Author: mck Date: Thu Dec 7 23:04:26 2023 New Revision: 65929 Log: Cassandra Java Driver 4.18.0 Added: dev/cassandra/cassandra-java-driver/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19178) Cluster upgrade 3.x -> 4.x fails due to IP change
[
https://issues.apache.org/jira/browse/CASSANDRA-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794463#comment-17794463
]
Aldo commented on CASSANDRA-19178:
--
{quote}One way out may be to add a new node to the cluster that knows about
cassandra7 and cassandra9 that can "introduce" those nodes to each other once
it knows about their correct addresses. It may not even need to complete
bootstrapping for this to happen.
{quote}
Good to know, thanks. To be honest, my 3-nodes scenario is a test environment
where I'm simulating the 3.x->4.x upgrade. The real production environment is a
5-nodes scenario, with RF=3. So, given the fact that I can temporarily "accept"
the quick downtime of 2 nodes out of 5, I can probably:
# select a seed node X for upgrade: such node will restart, receive a new IP,
and stay of the cluster until another node will discover its IP and communicate
with its inbound
# select another node Y and just restart it (without upgrade) but giving to it
the full list of all 5 nodes as seeds: in this way Y will resolve the
hostnames->IP of all the 5 nodes (including X) thus "introducing" X back into
the cluster, according to your suggestion
I will repeat 1-2 for all the 5 nodes until everything is upgraded to 4.x.
Moreover, after the first 1-2 steps on the very first node, the next iterations
of the 1-2 steps can be simplified: maybe I can use your other suggestion
(nodetool reloadseeds) and perform the step #2 by selecting a Y node of type
4.x and executing "nodetool reloadseeds".
> Cluster upgrade 3.x -> 4.x fails due to IP change
> -
>
> Key: CASSANDRA-19178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19178
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Aldo
>Priority: Normal
> Attachments: cassandra7.downgrade.log, cassandra7.log
>
>
> I have a Docker swarm cluster with 3 distinct Cassandra services (named
> {_}cassandra7{_}, {_}cassandra8{_}, {_}cassandra9{_}) running on 3 different
> servers. The 3 services are running the version 3.11.16, using the official
> Cassandra image 3.11.16 on Docker Hub. The first service is configured just
> with the following environment variables
> {code:java}
> CASSANDRA_LISTEN_ADDRESS="tasks.cassandra7"
> CASSANDRA_SEEDS="tasks.cassandra7,tasks.cassandra9" {code}
> which in turn, at startup, modifies the {_}cassandra.yaml{_}. So for instance
> the _cassandra.yaml_ for the first service contains the following (and the
> rest is the image default):
> {code:java}
> # grep tasks /etc/cassandra/cassandra.yaml
> - seeds: "tasks.cassandra7,tasks.cassandra9"
> listen_address: tasks.cassandra7
> broadcast_address: tasks.cassandra7
> broadcast_rpc_address: tasks.cassandra7 {code}
> Other services (8 and 9) have a similar configuration, obviously with a
> different {{CASSANDRA_LISTEN_ADDRESS }}(\{{{}tasks.cassandra8}} and
> {{{}tasks.cassandra9{}}}).
> The cluster is running smoothly and all the nodes are perfectly able to
> rejoin the cluster whichever event occurs, thanks to the Docker Swarm
> {{tasks.cassandraXXX}} "hostname": i can kill a Docker container waiting for
> Docker swarm to restart it, force update it in order to force a restart,
> scale to 0 and then 1 the service, restart an entire server, turn off and
> then turn on all the 3 servers. Never found an issue on this.
> I also just completed a full upgrade of the cluster from version 2.2.8 to
> 3.11.16 (simply upgrading the Docker official image associated with the
> services) without issues. I was also able, thanks to a 2.2.8 snapshot on each
> server, to perform a full downgrade to 2.2.8 and back to 3.11.16 again. I
> finally issued a {{nodetool upgradesstables}} on all nodes, so my SSTables
> have now the {{me-*}} prefix.
>
> The problem I'm facing right now is the upgrade from 3.11.16 to 4.x. The
> procedure that I follow is very simple:
> # I start from the _cassandra7_ service (which is a seed node)
> # {{nodetool drain}}
> # Wait for the {{DRAINING ... DRAINED}} messages to appear in the log
> # Upgrade the Docker image of _cassandra7_ to the official 4.1.3 version
> The procedure is exactly the same I followed for the upgrade 2.2.8 -->
> 3.11.16, obviously with a different version at step 4. Unfortunately the
> upgrade 3.x --> 4.x is not working, the _cassandra7_ service restarts and
> attempts to communicate with the other seed node ({_}cassandra9{_}) but the
> log of _cassandra7_ shows the following:
> {code:java}
> INFO [Messaging-EventLoop-3-3] 2023-12-06 17:15:04,727
> OutboundConnectionInitiator.java:390 - Failed to connect to peer
> tasks.cassandra9/10.0.2.196:7000(tasks.cassandra9/10.0.2.196:7000)
> io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed:
>
(cassandra-website) branch trunk updated: Adding blog post and text update to Catalyst page
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/trunk by this push: new 248a060d Adding blog post and text update to Catalyst page 248a060d is described below commit 248a060d5ddea38a0151323104e8e7d1d137bff9 Author: Paul Thomas Au AuthorDate: Wed Dec 6 13:22:00 2023 -0800 Adding blog post and text update to Catalyst page --- site-content/source/modules/ROOT/pages/blog.adoc | 23 ++ ...pache-Cassandra-5.0-Features-Vector-Search.adoc | 52 ++ .../ROOT/pages/cassandra-catalyst-program.adoc | 2 +- 3 files changed, 76 insertions(+), 1 deletion(-) diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 1869ba19..45cc0873 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -8,6 +8,29 @@ NOTES FOR CONTENT CREATORS - Replace post tile, date, description and link to you post. +//start card +[openblock,card shadow relative test] + +[openblock,card-header] +-- +[discrete] +=== Apache Cassandra 5.0 Features: Vector Search +[discrete] + December 5, 2023 +-- +[openblock,card-content] +-- +Explore the key Vector Search benefits Apache Cassandra users can look forward to, as well as applications the capability can enable. +[openblock,card-btn card-btn--blog] + +[.btn.btn--alt] +xref:blog/Apache-Cassandra-5.0-Features-Vector-Search.adoc[Read More] + + +-- + +//end card + //start card [openblock,card shadow relative test] diff --git a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-5.0-Features-Vector-Search.adoc b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-5.0-Features-Vector-Search.adoc new file mode 100644 index ..6d19054c --- /dev/null +++ b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-5.0-Features-Vector-Search.adoc @@ -0,0 +1,52 @@ += Apache Cassandra 5.0 Features: Vector Search +:page-layout: single-post +:page-role: blog-post +:page-post-date: December 5, 2023 +:page-post-author: The Apache Cassandra Community +:description: +:keywords: + +__Apache Cassandra 5.0 is the project’s major release for 2023, and it promises some of the biggest changes for Cassandra to date. After more than a decade of engineering work dedicated to stabilizing and building Cassandra as a distributed database, we now look forward to introducing a host of exciting features and enhancements that empower users to take their data-driven applications to the next level - including machine learning and artificial intelligence.__ + +__This blog series aims to give a deeper dive into some of the key features of Cassandra 5.0.__ + +Apache Cassandra is a NoSQL database management system known for its ability to handle massive amounts of data across multiple nodes and provide high availability and fault tolerance. Typically, Cassandra is used for storing structured and semi-structured data, making it ideal for applications like time series data, IoT, and social media platforms. However, Artificial Intelligence (AI) transforms how we interact with data. While Cassandra has become a go-to choice for many AI application [...] + +The Apache Cassandra community is expanding the database’s capabilities to include https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-30%3A+Approximate+Nearest+Neighbor%28ANN%29+Vector+Search+via+Storage-Attached+Indexes[Vector Search^] with the upcoming 5.0 release. With Vector Search, Cassandra will now enable generative AI applications, including high-dimensional data handling, similarity matching, and natural language processing (NLP) functioning. + +In this blog, we will explore the key Vector Search benefits Apache Cassandra users can look forward to, as well as applications the capability can enable. + +== Key Benefits of Apache Cassandra Vector Search + +* *Unstructured data queries*: Vector Search enables users to query unstructured data, including text, audio, pictures, and videos, where Cassandra was previously limited to searching structured data (floats, integers, or full strings). +* *Search accuracy and patterns*: Vector Search allows for similarity-based queries, enabling more accurate and relevant search results. Considering the semantic meaning of data points can uncover hidden relationships and patterns that traditional keyword searches might miss. +* *Efficient query processing*: With Vector Search, Cassandra can perform similarity calculations and ranking directly within the database, which eliminates the need to transfer large amounts of data to external systems (thereby reducing latency and improving overall query performance). +* *Scalability and distributed processing*: Vector Search can
(cassandra-java-driver) branch 4.x updated (105d378fc -> 7637a5b24)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch 4.x in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git from 105d378fc [maven-release-plugin] prepare release 4.18.0 add 7637a5b24 [maven-release-plugin] prepare for next development iteration No new revisions were added by this update. Summary of changes: bom/pom.xml | 18 +- core-shaded/pom.xml | 2 +- core/pom.xml | 2 +- distribution-source/pom.xml | 2 +- distribution-tests/pom.xml | 2 +- distribution/pom.xml | 2 +- examples/pom.xml | 2 +- integration-tests/pom.xml| 2 +- mapper-processor/pom.xml | 2 +- mapper-runtime/pom.xml | 2 +- metrics/micrometer/pom.xml | 2 +- metrics/microprofile/pom.xml | 2 +- osgi-tests/pom.xml | 2 +- pom.xml | 4 ++-- query-builder/pom.xml| 2 +- test-infra/pom.xml | 2 +- 16 files changed, 25 insertions(+), 25 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-java-driver) annotated tag 4.18.0 updated (105d378fc -> 120205565)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to annotated tag 4.18.0 in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git *** WARNING: tag 4.18.0 was modified! *** from 105d378fc (commit) to 120205565 (tag) tagging 105d378fce16804a8af4c26cf732340a0c63b3c9 (commit) replaces 4.17.0 by mck on Thu Dec 7 23:36:51 2023 +0100 - Log - [maven-release-plugin] copy for tag 4.18.0 --- No new revisions were added by this update. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-java-driver) branch 4.x updated (f11622308 -> 105d378fc)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch 4.x in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git from f11622308 Compliance changes for generated source and binary distributable tarballs add 105d378fc [maven-release-plugin] prepare release 4.18.0 No new revisions were added by this update. Summary of changes: bom/pom.xml | 18 +- core-shaded/pom.xml | 2 +- core/pom.xml | 2 +- distribution-source/pom.xml | 2 +- distribution-tests/pom.xml | 2 +- distribution/pom.xml | 2 +- examples/pom.xml | 2 +- integration-tests/pom.xml| 2 +- mapper-processor/pom.xml | 2 +- mapper-runtime/pom.xml | 2 +- metrics/micrometer/pom.xml | 2 +- metrics/microprofile/pom.xml | 2 +- osgi-tests/pom.xml | 2 +- pom.xml | 4 ++-- query-builder/pom.xml| 2 +- test-infra/pom.xml | 2 +- 16 files changed, 25 insertions(+), 25 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18970) Cut ASF releases for cassandra-java-driver 3.x and 4.x
[ https://issues.apache.org/jira/browse/CASSANDRA-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever reassigned CASSANDRA-18970: -- Assignee: Michael Semb Wever (was: Henry Hughes) > Cut ASF releases for cassandra-java-driver 3.x and 4.x > -- > > Key: CASSANDRA-18970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18970 > Project: Cassandra > Issue Type: Sub-task > Components: Client/java-driver >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[
https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794457#comment-17794457
]
Michael Semb Wever commented on CASSANDRA-18969:
latest commit
https://github.com/apache/cassandra-java-driver/commit/f11622308d031bf85047c4811e737aeb6ae236e9
will need to be replicated onto all branches…
> Pre-release required legal changes for cassandra-java-driver
>
>
> Key: CASSANDRA-18969
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18969
> Project: Cassandra
> Issue Type: Sub-task
> Components: Client/java-driver
>Reporter: Michael Semb Wever
>Priority: Urgent
> Time Spent: 37h 20m
> Remaining Estimate: 0h
>
> TODO
> * -there is still code copyrighted to others that isn't mentioned in LICENSE
> (e.g. ci/install-jdk.sh )-
> * -"© DataStax" still appears in the README-
> * -spotbugs is LGPL, in 4.x, and not correctly made provided scope-
> * add any BSD/MIT deps to LICENCE
> * -ensure copyright headers are on all files, use rat plugin-
> * ensure NOTICE propagates NOTICES
> In short…
> {quote}
> LICENSE must contain the ASL, plus references to all code that includes
> someone else's copyright, and all BSD and MIT dependencies (including
> transitive).
> NOTICE must the standard header, plus the shorten content of any NOTICE file
> (minus its header) found in any ASL dependency (including transitive).
> {quote}
> These things must be done before a release.
> Cat X deps we included as build tool by using scope provided we should put a
> test in to ensure they work at runtime without the dep doesn't regress in the
> future.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-java-driver) branch 4.x updated (12e3e3ea0 -> f11622308)
This is an automated email from the ASF dual-hosted git repository.
mck pushed a change to branch 4.x
in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git
from 12e3e3ea0 Add LICENSE and NOTICE.txt/NOTICE_binary to published jars
LICENSE + NOTICE.txt is added to source jars, LICENSE + NOTICE_binary.txt is
added to regular jars. Make parent project inherit from apache pom. Updated
NOTICE wording to "developed at ..." per latest instructions.
add f11622308 Compliance changes for generated source and binary
distributable tarballs
No new revisions were added by this update.
Summary of changes:
.github/workflows/dep-lic-scan.yaml| 16 +
LICENSE => LICENSE_binary | 24 +
README.md | 21 +-
bom/pom.xml| 18 +-
core-shaded/pom.xml| 45 +-
core/pom.xml |3 +-
core/src/main/resources/reference.conf |4 +-
{distribution => distribution-source}/pom.xml | 106 +-
.../src/assembly/source-tarball.xml| 34 +-
distribution-tests/pom.xml | 16 +-
distribution/pom.xml | 62 +-
distribution/src/assembly/binary-tarball.xml | 44 +-
examples/pom.xml |4 +-
integration-tests/pom.xml | 16 +-
licenses/HdrHistogram.txt | 41 +
licenses/asm.txt | 27 +
licenses/jnr-posix.txt | 1076
licenses/jnr-x86asm.txt| 24 +
licenses/reactive-streams.txt |7 +
licenses/slf4j-api.txt | 21 +
manual/core/README.md |2 +-
manual/core/bom/README.md | 12 +-
manual/core/configuration/README.md|2 +-
manual/core/integration/README.md | 18 +-
manual/core/metrics/README.md |8 +-
manual/core/shaded_jar/README.md | 10 +-
manual/mapper/README.md|4 +-
manual/mapper/config/README.md |8 +-
manual/mapper/config/kotlin/README.md |2 +-
manual/query_builder/README.md |2 +-
mapper-processor/pom.xml |7 +-
mapper-runtime/pom.xml |5 +-
metrics/micrometer/pom.xml |7 +-
metrics/microprofile/pom.xml |7 +-
osgi-tests/pom.xml | 12 +-
pom.xml| 39 +-
query-builder/pom.xml |7 +-
test-infra/pom.xml |5 +-
38 files changed, 1438 insertions(+), 328 deletions(-)
copy LICENSE => LICENSE_binary (93%)
copy {distribution => distribution-source}/pom.xml (51%)
copy core-shaded/src/assembly/shaded-jar.xml =>
distribution-source/src/assembly/source-tarball.xml (55%)
create mode 100644 licenses/HdrHistogram.txt
create mode 100644 licenses/asm.txt
create mode 100644 licenses/jnr-posix.txt
create mode 100644 licenses/jnr-x86asm.txt
create mode 100644 licenses/reactive-streams.txt
create mode 100644 licenses/slf4j-api.txt
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-18969: source files missing from sources jars due to maven … [cassandra-java-driver]
michaelsembwever commented on PR #1900: URL: https://github.com/apache/cassandra-java-driver/pull/1900#issuecomment-1846206126 Committed with some small addition changes as https://github.com/apache/cassandra-java-driver/commit/f11622308d031bf85047c4811e737aeb6ae236e9 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-18969: source files missing from sources jars due to maven … [cassandra-java-driver]
michaelsembwever closed pull request #1900: CASSANDRA-18969: source files missing from sources jars due to maven … URL: https://github.com/apache/cassandra-java-driver/pull/1900 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19178) Cluster upgrade 3.x -> 4.x fails due to IP change
[
https://issues.apache.org/jira/browse/CASSANDRA-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794449#comment-17794449
]
Brandon Williams commented on CASSANDRA-19178:
--
One way out may be to add a new node to the cluster that knows about cassandra7
and cassandra9 that can "introduce" those nodes to each other once it knows
about their correct addresses. It may not even need to complete bootstrapping
for this to happen.
> Cluster upgrade 3.x -> 4.x fails due to IP change
> -
>
> Key: CASSANDRA-19178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19178
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Aldo
>Priority: Normal
> Attachments: cassandra7.downgrade.log, cassandra7.log
>
>
> I have a Docker swarm cluster with 3 distinct Cassandra services (named
> {_}cassandra7{_}, {_}cassandra8{_}, {_}cassandra9{_}) running on 3 different
> servers. The 3 services are running the version 3.11.16, using the official
> Cassandra image 3.11.16 on Docker Hub. The first service is configured just
> with the following environment variables
> {code:java}
> CASSANDRA_LISTEN_ADDRESS="tasks.cassandra7"
> CASSANDRA_SEEDS="tasks.cassandra7,tasks.cassandra9" {code}
> which in turn, at startup, modifies the {_}cassandra.yaml{_}. So for instance
> the _cassandra.yaml_ for the first service contains the following (and the
> rest is the image default):
> {code:java}
> # grep tasks /etc/cassandra/cassandra.yaml
> - seeds: "tasks.cassandra7,tasks.cassandra9"
> listen_address: tasks.cassandra7
> broadcast_address: tasks.cassandra7
> broadcast_rpc_address: tasks.cassandra7 {code}
> Other services (8 and 9) have a similar configuration, obviously with a
> different {{CASSANDRA_LISTEN_ADDRESS }}(\{{{}tasks.cassandra8}} and
> {{{}tasks.cassandra9{}}}).
> The cluster is running smoothly and all the nodes are perfectly able to
> rejoin the cluster whichever event occurs, thanks to the Docker Swarm
> {{tasks.cassandraXXX}} "hostname": i can kill a Docker container waiting for
> Docker swarm to restart it, force update it in order to force a restart,
> scale to 0 and then 1 the service, restart an entire server, turn off and
> then turn on all the 3 servers. Never found an issue on this.
> I also just completed a full upgrade of the cluster from version 2.2.8 to
> 3.11.16 (simply upgrading the Docker official image associated with the
> services) without issues. I was also able, thanks to a 2.2.8 snapshot on each
> server, to perform a full downgrade to 2.2.8 and back to 3.11.16 again. I
> finally issued a {{nodetool upgradesstables}} on all nodes, so my SSTables
> have now the {{me-*}} prefix.
>
> The problem I'm facing right now is the upgrade from 3.11.16 to 4.x. The
> procedure that I follow is very simple:
> # I start from the _cassandra7_ service (which is a seed node)
> # {{nodetool drain}}
> # Wait for the {{DRAINING ... DRAINED}} messages to appear in the log
> # Upgrade the Docker image of _cassandra7_ to the official 4.1.3 version
> The procedure is exactly the same I followed for the upgrade 2.2.8 -->
> 3.11.16, obviously with a different version at step 4. Unfortunately the
> upgrade 3.x --> 4.x is not working, the _cassandra7_ service restarts and
> attempts to communicate with the other seed node ({_}cassandra9{_}) but the
> log of _cassandra7_ shows the following:
> {code:java}
> INFO [Messaging-EventLoop-3-3] 2023-12-06 17:15:04,727
> OutboundConnectionInitiator.java:390 - Failed to connect to peer
> tasks.cassandra9/10.0.2.196:7000(tasks.cassandra9/10.0.2.196:7000)
> io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed:
> Connection reset by peer{code}
> The relevant port of the log, related to the missing internode communication,
> is attached in _cassandra7.log_
> In the log of _cassandra9_ there is nothing after the abovementioned step #4.
> So only _cassandra7_ is saying something in the logs.
> I tried with multiple versions (4.0.11 but also 4.0.0) but the outcome is
> always the same. Of course when I follow the steps 1..3, then restore the 3.x
> snapshot and finally perform the step #4 using the official 3.11.16 version
> the node 7 restarts correctly and joins the cluster. I attached the relevant
> part of the log (see {_}cassandra7.downgrade.log{_}) where you can see that
> node 7 and 9 can communicate.
> I suspect this could be related to the port 7000 now (with Cassandra 4.x)
> supporting both encrypted and unencrypted traffic. As stated previously I'm
> using the untouched official Cassandra images so all my cluster, inside the
> Docker Swarm, is not (and has never been) configured with encryption.
> I can also add the following: if I perform the 4 above steps also for the
[jira] [Commented] (CASSANDRA-18839) Catch SSLHandshakeExceptions exceptions
[
https://issues.apache.org/jira/browse/CASSANDRA-18839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794446#comment-17794446
]
Stefan Miklosovic commented on CASSANDRA-18839:
---
Thank you for your contribution! I am running the builds for trunk.
> Catch SSLHandshakeExceptions exceptions
> ---
>
> Key: CASSANDRA-18839
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18839
> Project: Cassandra
> Issue Type: Improvement
> Components: Messaging/Client
>Reporter: Brad Schoening
>Assignee: James Hu
>Priority: Low
> Fix For: 4.0.x, 4.1.x, 5.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When SSL connection errors occur, they tend to flood the log with stack
> traces and lack the identity of the remote client IP. Instead,
> PreV5Handlers.decode() could catch SSLHandshakeException and provide a brief,
> more informative WARN level message instead of the verbose and mostly
> unhelpful stack trace.
> I.e.,
> {code:java}
> [WARN ] [epollEventLoopGroup-5-5] cluster_id=3 ip_address=10.0.0.1
> PreV5Handlers.java:261 - SSLHandshakeException in client networking with peer
> 10.0.0.10:9042 error:10d7:SSL
> routines:OPENSSL_internal:SSL_HANDSHAKE_FAILURE {code}
> instead of the current ones which flood the logs:
> {code:java}
> 2023-09-12 00:00:25,368 [WARN ] [epollEventLoopGroup-5-5] cluster_id=3
> ip_address=10.0.0.1 PreV5Handlers.java:261 - Unknown exception in client
> networking
> io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException:
> error:10d7:SSL routines:OPENSSL_internal:SSL_HANDSHAKE_FAILURE
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:478)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:795)
> at
> io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:480)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:378)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: javax.net.ssl.SSLHandshakeException: error:10d7:SSL
> routines:OPENSSL_internal:SSL_HANDSHAKE_FAILURE
> at
> io.netty.handler.ssl.ReferenceCountedOpenSslEngine.shutdownWithError(ReferenceCountedOpenSslEngine.java:1031)
> at
> io.netty.handler.ssl.ReferenceCountedOpenSslEngine.sslReadErrorResult(ReferenceCountedOpenSslEngine.java:1321)
> at
> io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1270)
> at
> io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1346)
> at
> io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1389)
> at
> io.netty.handler.ssl.SslHandler$SslEngineType$1.unwrap(SslHandler.java:206)
> at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1387)
> at
> io.netty.handler.ssl.SslHandler.decodeNonJdkCompatible(SslHandler.java:1294)
> at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1331)
> at
> io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:508)
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:447)
> ... 15 common frames omitted {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19178) Cluster upgrade 3.x -> 4.x fails due to IP change
[
https://issues.apache.org/jira/browse/CASSANDRA-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794439#comment-17794439
]
Brandon Williams edited comment on CASSANDRA-19178 at 12/7/23 9:31 PM:
---
Yes, you can make the seed provider reload the seeds with 'nodetool
reloadseeds'... but this doesn't exist until 4.0
was (Author: brandon.williams):
Yes, you can make the seed provider reload the seeds with 'nodetool reloadseeds'
> Cluster upgrade 3.x -> 4.x fails due to IP change
> -
>
> Key: CASSANDRA-19178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19178
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Aldo
>Priority: Normal
> Attachments: cassandra7.downgrade.log, cassandra7.log
>
>
> I have a Docker swarm cluster with 3 distinct Cassandra services (named
> {_}cassandra7{_}, {_}cassandra8{_}, {_}cassandra9{_}) running on 3 different
> servers. The 3 services are running the version 3.11.16, using the official
> Cassandra image 3.11.16 on Docker Hub. The first service is configured just
> with the following environment variables
> {code:java}
> CASSANDRA_LISTEN_ADDRESS="tasks.cassandra7"
> CASSANDRA_SEEDS="tasks.cassandra7,tasks.cassandra9" {code}
> which in turn, at startup, modifies the {_}cassandra.yaml{_}. So for instance
> the _cassandra.yaml_ for the first service contains the following (and the
> rest is the image default):
> {code:java}
> # grep tasks /etc/cassandra/cassandra.yaml
> - seeds: "tasks.cassandra7,tasks.cassandra9"
> listen_address: tasks.cassandra7
> broadcast_address: tasks.cassandra7
> broadcast_rpc_address: tasks.cassandra7 {code}
> Other services (8 and 9) have a similar configuration, obviously with a
> different {{CASSANDRA_LISTEN_ADDRESS }}(\{{{}tasks.cassandra8}} and
> {{{}tasks.cassandra9{}}}).
> The cluster is running smoothly and all the nodes are perfectly able to
> rejoin the cluster whichever event occurs, thanks to the Docker Swarm
> {{tasks.cassandraXXX}} "hostname": i can kill a Docker container waiting for
> Docker swarm to restart it, force update it in order to force a restart,
> scale to 0 and then 1 the service, restart an entire server, turn off and
> then turn on all the 3 servers. Never found an issue on this.
> I also just completed a full upgrade of the cluster from version 2.2.8 to
> 3.11.16 (simply upgrading the Docker official image associated with the
> services) without issues. I was also able, thanks to a 2.2.8 snapshot on each
> server, to perform a full downgrade to 2.2.8 and back to 3.11.16 again. I
> finally issued a {{nodetool upgradesstables}} on all nodes, so my SSTables
> have now the {{me-*}} prefix.
>
> The problem I'm facing right now is the upgrade from 3.11.16 to 4.x. The
> procedure that I follow is very simple:
> # I start from the _cassandra7_ service (which is a seed node)
> # {{nodetool drain}}
> # Wait for the {{DRAINING ... DRAINED}} messages to appear in the log
> # Upgrade the Docker image of _cassandra7_ to the official 4.1.3 version
> The procedure is exactly the same I followed for the upgrade 2.2.8 -->
> 3.11.16, obviously with a different version at step 4. Unfortunately the
> upgrade 3.x --> 4.x is not working, the _cassandra7_ service restarts and
> attempts to communicate with the other seed node ({_}cassandra9{_}) but the
> log of _cassandra7_ shows the following:
> {code:java}
> INFO [Messaging-EventLoop-3-3] 2023-12-06 17:15:04,727
> OutboundConnectionInitiator.java:390 - Failed to connect to peer
> tasks.cassandra9/10.0.2.196:7000(tasks.cassandra9/10.0.2.196:7000)
> io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed:
> Connection reset by peer{code}
> The relevant port of the log, related to the missing internode communication,
> is attached in _cassandra7.log_
> In the log of _cassandra9_ there is nothing after the abovementioned step #4.
> So only _cassandra7_ is saying something in the logs.
> I tried with multiple versions (4.0.11 but also 4.0.0) but the outcome is
> always the same. Of course when I follow the steps 1..3, then restore the 3.x
> snapshot and finally perform the step #4 using the official 3.11.16 version
> the node 7 restarts correctly and joins the cluster. I attached the relevant
> part of the log (see {_}cassandra7.downgrade.log{_}) where you can see that
> node 7 and 9 can communicate.
> I suspect this could be related to the port 7000 now (with Cassandra 4.x)
> supporting both encrypted and unencrypted traffic. As stated previously I'm
> using the untouched official Cassandra images so all my cluster, inside the
> Docker Swarm, is not (and has never been) configured with encryption.
> I can also add the following: if I perform
[jira] [Commented] (CASSANDRA-19178) Cluster upgrade 3.x -> 4.x fails due to IP change
[
https://issues.apache.org/jira/browse/CASSANDRA-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794439#comment-17794439
]
Brandon Williams commented on CASSANDRA-19178:
--
Yes, you can make the seed provider reload the seeds with 'nodetool reloadseeds'
> Cluster upgrade 3.x -> 4.x fails due to IP change
> -
>
> Key: CASSANDRA-19178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19178
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Aldo
>Priority: Normal
> Attachments: cassandra7.downgrade.log, cassandra7.log
>
>
> I have a Docker swarm cluster with 3 distinct Cassandra services (named
> {_}cassandra7{_}, {_}cassandra8{_}, {_}cassandra9{_}) running on 3 different
> servers. The 3 services are running the version 3.11.16, using the official
> Cassandra image 3.11.16 on Docker Hub. The first service is configured just
> with the following environment variables
> {code:java}
> CASSANDRA_LISTEN_ADDRESS="tasks.cassandra7"
> CASSANDRA_SEEDS="tasks.cassandra7,tasks.cassandra9" {code}
> which in turn, at startup, modifies the {_}cassandra.yaml{_}. So for instance
> the _cassandra.yaml_ for the first service contains the following (and the
> rest is the image default):
> {code:java}
> # grep tasks /etc/cassandra/cassandra.yaml
> - seeds: "tasks.cassandra7,tasks.cassandra9"
> listen_address: tasks.cassandra7
> broadcast_address: tasks.cassandra7
> broadcast_rpc_address: tasks.cassandra7 {code}
> Other services (8 and 9) have a similar configuration, obviously with a
> different {{CASSANDRA_LISTEN_ADDRESS }}(\{{{}tasks.cassandra8}} and
> {{{}tasks.cassandra9{}}}).
> The cluster is running smoothly and all the nodes are perfectly able to
> rejoin the cluster whichever event occurs, thanks to the Docker Swarm
> {{tasks.cassandraXXX}} "hostname": i can kill a Docker container waiting for
> Docker swarm to restart it, force update it in order to force a restart,
> scale to 0 and then 1 the service, restart an entire server, turn off and
> then turn on all the 3 servers. Never found an issue on this.
> I also just completed a full upgrade of the cluster from version 2.2.8 to
> 3.11.16 (simply upgrading the Docker official image associated with the
> services) without issues. I was also able, thanks to a 2.2.8 snapshot on each
> server, to perform a full downgrade to 2.2.8 and back to 3.11.16 again. I
> finally issued a {{nodetool upgradesstables}} on all nodes, so my SSTables
> have now the {{me-*}} prefix.
>
> The problem I'm facing right now is the upgrade from 3.11.16 to 4.x. The
> procedure that I follow is very simple:
> # I start from the _cassandra7_ service (which is a seed node)
> # {{nodetool drain}}
> # Wait for the {{DRAINING ... DRAINED}} messages to appear in the log
> # Upgrade the Docker image of _cassandra7_ to the official 4.1.3 version
> The procedure is exactly the same I followed for the upgrade 2.2.8 -->
> 3.11.16, obviously with a different version at step 4. Unfortunately the
> upgrade 3.x --> 4.x is not working, the _cassandra7_ service restarts and
> attempts to communicate with the other seed node ({_}cassandra9{_}) but the
> log of _cassandra7_ shows the following:
> {code:java}
> INFO [Messaging-EventLoop-3-3] 2023-12-06 17:15:04,727
> OutboundConnectionInitiator.java:390 - Failed to connect to peer
> tasks.cassandra9/10.0.2.196:7000(tasks.cassandra9/10.0.2.196:7000)
> io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed:
> Connection reset by peer{code}
> The relevant port of the log, related to the missing internode communication,
> is attached in _cassandra7.log_
> In the log of _cassandra9_ there is nothing after the abovementioned step #4.
> So only _cassandra7_ is saying something in the logs.
> I tried with multiple versions (4.0.11 but also 4.0.0) but the outcome is
> always the same. Of course when I follow the steps 1..3, then restore the 3.x
> snapshot and finally perform the step #4 using the official 3.11.16 version
> the node 7 restarts correctly and joins the cluster. I attached the relevant
> part of the log (see {_}cassandra7.downgrade.log{_}) where you can see that
> node 7 and 9 can communicate.
> I suspect this could be related to the port 7000 now (with Cassandra 4.x)
> supporting both encrypted and unencrypted traffic. As stated previously I'm
> using the untouched official Cassandra images so all my cluster, inside the
> Docker Swarm, is not (and has never been) configured with encryption.
> I can also add the following: if I perform the 4 above steps also for the
> _cassandra9_ and _cassandra8_ services, in the end the cluster works. But
> this is not acceptable, because the cluster is unavailable until I finish the
> full upgrade
[jira] [Commented] (CASSANDRA-19178) Cluster upgrade 3.x -> 4.x fails due to IP change
[
https://issues.apache.org/jira/browse/CASSANDRA-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794434#comment-17794434
]
Aldo commented on CASSANDRA-19178:
--
{quote}Is the seed list on cassandra9 up to date with cassandra7?
{quote}
Is there a way to dynamically update the seed list in a living node? In my
configuration I have:
* cassandra 7, just upgraded with 4.x but out-of-the-cluster until it is able
to properly communicate with other peers
* cassandra 8, running with 3.x and paired with cassandra 9. Don't know the
new IP of cassandra7
* cassandra 9, running with 3.x and paired with cassandra 8. Don't know the
new IP of cassandra7
If I can trigger some kind of live seed list refresh on cassandra 9 or 8, this
will result in what you described: cassandra7 will learn the 8 & 9 messaging
version when they communicate with it. But to do it one between 9 or 8 must be
triggered in order to use the new cassandra7 IP. "Triggered" to me means "live
trigger": it's unaccettable to restart another node (8 or 9) when the 7 is
already out of the cluster. Is it possible? Through JMX or something similar ?
> Cluster upgrade 3.x -> 4.x fails due to IP change
> -
>
> Key: CASSANDRA-19178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19178
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Aldo
>Priority: Normal
> Attachments: cassandra7.downgrade.log, cassandra7.log
>
>
> I have a Docker swarm cluster with 3 distinct Cassandra services (named
> {_}cassandra7{_}, {_}cassandra8{_}, {_}cassandra9{_}) running on 3 different
> servers. The 3 services are running the version 3.11.16, using the official
> Cassandra image 3.11.16 on Docker Hub. The first service is configured just
> with the following environment variables
> {code:java}
> CASSANDRA_LISTEN_ADDRESS="tasks.cassandra7"
> CASSANDRA_SEEDS="tasks.cassandra7,tasks.cassandra9" {code}
> which in turn, at startup, modifies the {_}cassandra.yaml{_}. So for instance
> the _cassandra.yaml_ for the first service contains the following (and the
> rest is the image default):
> {code:java}
> # grep tasks /etc/cassandra/cassandra.yaml
> - seeds: "tasks.cassandra7,tasks.cassandra9"
> listen_address: tasks.cassandra7
> broadcast_address: tasks.cassandra7
> broadcast_rpc_address: tasks.cassandra7 {code}
> Other services (8 and 9) have a similar configuration, obviously with a
> different {{CASSANDRA_LISTEN_ADDRESS }}(\{{{}tasks.cassandra8}} and
> {{{}tasks.cassandra9{}}}).
> The cluster is running smoothly and all the nodes are perfectly able to
> rejoin the cluster whichever event occurs, thanks to the Docker Swarm
> {{tasks.cassandraXXX}} "hostname": i can kill a Docker container waiting for
> Docker swarm to restart it, force update it in order to force a restart,
> scale to 0 and then 1 the service, restart an entire server, turn off and
> then turn on all the 3 servers. Never found an issue on this.
> I also just completed a full upgrade of the cluster from version 2.2.8 to
> 3.11.16 (simply upgrading the Docker official image associated with the
> services) without issues. I was also able, thanks to a 2.2.8 snapshot on each
> server, to perform a full downgrade to 2.2.8 and back to 3.11.16 again. I
> finally issued a {{nodetool upgradesstables}} on all nodes, so my SSTables
> have now the {{me-*}} prefix.
>
> The problem I'm facing right now is the upgrade from 3.11.16 to 4.x. The
> procedure that I follow is very simple:
> # I start from the _cassandra7_ service (which is a seed node)
> # {{nodetool drain}}
> # Wait for the {{DRAINING ... DRAINED}} messages to appear in the log
> # Upgrade the Docker image of _cassandra7_ to the official 4.1.3 version
> The procedure is exactly the same I followed for the upgrade 2.2.8 -->
> 3.11.16, obviously with a different version at step 4. Unfortunately the
> upgrade 3.x --> 4.x is not working, the _cassandra7_ service restarts and
> attempts to communicate with the other seed node ({_}cassandra9{_}) but the
> log of _cassandra7_ shows the following:
> {code:java}
> INFO [Messaging-EventLoop-3-3] 2023-12-06 17:15:04,727
> OutboundConnectionInitiator.java:390 - Failed to connect to peer
> tasks.cassandra9/10.0.2.196:7000(tasks.cassandra9/10.0.2.196:7000)
> io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed:
> Connection reset by peer{code}
> The relevant port of the log, related to the missing internode communication,
> is attached in _cassandra7.log_
> In the log of _cassandra9_ there is nothing after the abovementioned step #4.
> So only _cassandra7_ is saying something in the logs.
> I tried with multiple versions (4.0.11 but also 4.0.0) but the outcome is
> always the same. Of course when I follow the
[jira] [Commented] (CASSANDRA-19178) Cluster upgrade 3.x -> 4.x fails due to IP change
[
https://issues.apache.org/jira/browse/CASSANDRA-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794431#comment-17794431
]
Aldo commented on CASSANDRA-19178:
--
Unfortunately the answer is no: cassandra7 just restarted and got a brand new
IP from Docker Swarm. So there is not way for cassandra9 to contact cassandra7
by itself. It is cassandra7 that, just restarted, must communicate with
cassandra9. And according to the code I studied in my last comment above, it
should work. But it instead, in my environment, the cassandra9 answer is
completely masked by the connection reset by peer.
> Cluster upgrade 3.x -> 4.x fails due to IP change
> -
>
> Key: CASSANDRA-19178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19178
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Aldo
>Priority: Normal
> Attachments: cassandra7.downgrade.log, cassandra7.log
>
>
> I have a Docker swarm cluster with 3 distinct Cassandra services (named
> {_}cassandra7{_}, {_}cassandra8{_}, {_}cassandra9{_}) running on 3 different
> servers. The 3 services are running the version 3.11.16, using the official
> Cassandra image 3.11.16 on Docker Hub. The first service is configured just
> with the following environment variables
> {code:java}
> CASSANDRA_LISTEN_ADDRESS="tasks.cassandra7"
> CASSANDRA_SEEDS="tasks.cassandra7,tasks.cassandra9" {code}
> which in turn, at startup, modifies the {_}cassandra.yaml{_}. So for instance
> the _cassandra.yaml_ for the first service contains the following (and the
> rest is the image default):
> {code:java}
> # grep tasks /etc/cassandra/cassandra.yaml
> - seeds: "tasks.cassandra7,tasks.cassandra9"
> listen_address: tasks.cassandra7
> broadcast_address: tasks.cassandra7
> broadcast_rpc_address: tasks.cassandra7 {code}
> Other services (8 and 9) have a similar configuration, obviously with a
> different {{CASSANDRA_LISTEN_ADDRESS }}(\{{{}tasks.cassandra8}} and
> {{{}tasks.cassandra9{}}}).
> The cluster is running smoothly and all the nodes are perfectly able to
> rejoin the cluster whichever event occurs, thanks to the Docker Swarm
> {{tasks.cassandraXXX}} "hostname": i can kill a Docker container waiting for
> Docker swarm to restart it, force update it in order to force a restart,
> scale to 0 and then 1 the service, restart an entire server, turn off and
> then turn on all the 3 servers. Never found an issue on this.
> I also just completed a full upgrade of the cluster from version 2.2.8 to
> 3.11.16 (simply upgrading the Docker official image associated with the
> services) without issues. I was also able, thanks to a 2.2.8 snapshot on each
> server, to perform a full downgrade to 2.2.8 and back to 3.11.16 again. I
> finally issued a {{nodetool upgradesstables}} on all nodes, so my SSTables
> have now the {{me-*}} prefix.
>
> The problem I'm facing right now is the upgrade from 3.11.16 to 4.x. The
> procedure that I follow is very simple:
> # I start from the _cassandra7_ service (which is a seed node)
> # {{nodetool drain}}
> # Wait for the {{DRAINING ... DRAINED}} messages to appear in the log
> # Upgrade the Docker image of _cassandra7_ to the official 4.1.3 version
> The procedure is exactly the same I followed for the upgrade 2.2.8 -->
> 3.11.16, obviously with a different version at step 4. Unfortunately the
> upgrade 3.x --> 4.x is not working, the _cassandra7_ service restarts and
> attempts to communicate with the other seed node ({_}cassandra9{_}) but the
> log of _cassandra7_ shows the following:
> {code:java}
> INFO [Messaging-EventLoop-3-3] 2023-12-06 17:15:04,727
> OutboundConnectionInitiator.java:390 - Failed to connect to peer
> tasks.cassandra9/10.0.2.196:7000(tasks.cassandra9/10.0.2.196:7000)
> io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed:
> Connection reset by peer{code}
> The relevant port of the log, related to the missing internode communication,
> is attached in _cassandra7.log_
> In the log of _cassandra9_ there is nothing after the abovementioned step #4.
> So only _cassandra7_ is saying something in the logs.
> I tried with multiple versions (4.0.11 but also 4.0.0) but the outcome is
> always the same. Of course when I follow the steps 1..3, then restore the 3.x
> snapshot and finally perform the step #4 using the official 3.11.16 version
> the node 7 restarts correctly and joins the cluster. I attached the relevant
> part of the log (see {_}cassandra7.downgrade.log{_}) where you can see that
> node 7 and 9 can communicate.
> I suspect this could be related to the port 7000 now (with Cassandra 4.x)
> supporting both encrypted and unencrypted traffic. As stated previously I'm
> using the untouched official Cassandra images so all my cluster, inside
[jira] [Commented] (CASSANDRA-19178) Cluster upgrade 3.x -> 4.x fails due to IP change
[
https://issues.apache.org/jira/browse/CASSANDRA-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794429#comment-17794429
]
Brandon Williams commented on CASSANDRA-19178:
--
bq. the 4.x node (cassandra7) just sees a connection reset by peer and seems
not capable of downgrade the messaging version and retry the handshake
Cassandra keeps a pair of connections, one inbound and one outbound. In this
case the outbound from 4.x to 3.x will not work until the 4.x knows the version
to use with 3x. It will learn this version from 3.x's outbound connection to
its inbound, and then the 4.x outbound will use that version the next time it
tries to connect to the 3.x side. This is normal and why the version message
is logged at TRACE.
Is the seed list on cassandra9 up to date with cassandra7?
> Cluster upgrade 3.x -> 4.x fails due to IP change
> -
>
> Key: CASSANDRA-19178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19178
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Aldo
>Priority: Normal
> Attachments: cassandra7.downgrade.log, cassandra7.log
>
>
> I have a Docker swarm cluster with 3 distinct Cassandra services (named
> {_}cassandra7{_}, {_}cassandra8{_}, {_}cassandra9{_}) running on 3 different
> servers. The 3 services are running the version 3.11.16, using the official
> Cassandra image 3.11.16 on Docker Hub. The first service is configured just
> with the following environment variables
> {code:java}
> CASSANDRA_LISTEN_ADDRESS="tasks.cassandra7"
> CASSANDRA_SEEDS="tasks.cassandra7,tasks.cassandra9" {code}
> which in turn, at startup, modifies the {_}cassandra.yaml{_}. So for instance
> the _cassandra.yaml_ for the first service contains the following (and the
> rest is the image default):
> {code:java}
> # grep tasks /etc/cassandra/cassandra.yaml
> - seeds: "tasks.cassandra7,tasks.cassandra9"
> listen_address: tasks.cassandra7
> broadcast_address: tasks.cassandra7
> broadcast_rpc_address: tasks.cassandra7 {code}
> Other services (8 and 9) have a similar configuration, obviously with a
> different {{CASSANDRA_LISTEN_ADDRESS }}(\{{{}tasks.cassandra8}} and
> {{{}tasks.cassandra9{}}}).
> The cluster is running smoothly and all the nodes are perfectly able to
> rejoin the cluster whichever event occurs, thanks to the Docker Swarm
> {{tasks.cassandraXXX}} "hostname": i can kill a Docker container waiting for
> Docker swarm to restart it, force update it in order to force a restart,
> scale to 0 and then 1 the service, restart an entire server, turn off and
> then turn on all the 3 servers. Never found an issue on this.
> I also just completed a full upgrade of the cluster from version 2.2.8 to
> 3.11.16 (simply upgrading the Docker official image associated with the
> services) without issues. I was also able, thanks to a 2.2.8 snapshot on each
> server, to perform a full downgrade to 2.2.8 and back to 3.11.16 again. I
> finally issued a {{nodetool upgradesstables}} on all nodes, so my SSTables
> have now the {{me-*}} prefix.
>
> The problem I'm facing right now is the upgrade from 3.11.16 to 4.x. The
> procedure that I follow is very simple:
> # I start from the _cassandra7_ service (which is a seed node)
> # {{nodetool drain}}
> # Wait for the {{DRAINING ... DRAINED}} messages to appear in the log
> # Upgrade the Docker image of _cassandra7_ to the official 4.1.3 version
> The procedure is exactly the same I followed for the upgrade 2.2.8 -->
> 3.11.16, obviously with a different version at step 4. Unfortunately the
> upgrade 3.x --> 4.x is not working, the _cassandra7_ service restarts and
> attempts to communicate with the other seed node ({_}cassandra9{_}) but the
> log of _cassandra7_ shows the following:
> {code:java}
> INFO [Messaging-EventLoop-3-3] 2023-12-06 17:15:04,727
> OutboundConnectionInitiator.java:390 - Failed to connect to peer
> tasks.cassandra9/10.0.2.196:7000(tasks.cassandra9/10.0.2.196:7000)
> io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed:
> Connection reset by peer{code}
> The relevant port of the log, related to the missing internode communication,
> is attached in _cassandra7.log_
> In the log of _cassandra9_ there is nothing after the abovementioned step #4.
> So only _cassandra7_ is saying something in the logs.
> I tried with multiple versions (4.0.11 but also 4.0.0) but the outcome is
> always the same. Of course when I follow the steps 1..3, then restore the 3.x
> snapshot and finally perform the step #4 using the official 3.11.16 version
> the node 7 restarts correctly and joins the cluster. I attached the relevant
> part of the log (see {_}cassandra7.downgrade.log{_}) where you can see that
> node 7 and 9 can communicate.
> I suspect
[jira] [Commented] (CASSANDRA-19178) Cluster upgrade 3.x -> 4.x fails due to IP change
[
https://issues.apache.org/jira/browse/CASSANDRA-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794427#comment-17794427
]
Aldo commented on CASSANDRA-19178:
--
I read carefully the code of _IncomingTcpConnection.java_ (trunk 3.11.16). The
[receiveMessages|https://github.com/apache/cassandra/blob/681b6ca103d91d940a9fecb8cd812f58dd2490d0/src/java/org/apache/cassandra/net/IncomingTcpConnection.java#L142]
method seems to do two things:
# write and flush its current version (11)
# throw an IOException
The IOException results in the socket to be closed.
On the other side, the caller is busy on the _OutboundConnectionInitiator.java_
(trunk 4.1.3). It *for sure* enters the
[decode|https://github.com/apache/cassandra/blob/2a4cd36475de3eb47207cd88d2d472b876c6816d/src/java/org/apache/cassandra/net/OutboundConnectionInitiator.java#L263C27-L263C27]
method and proceeds to [line
267|https://github.com/apache/cassandra/blob/2a4cd36475de3eb47207cd88d2d472b876c6816d/src/java/org/apache/cassandra/net/OutboundConnectionInitiator.java#L267]
where it *should* decode the message, discover the version 11, print
{{received second handshake message from peer}} as per [line
273|https://github.com/apache/cassandra/blob/2a4cd36475de3eb47207cd88d2d472b876c6816d/src/java/org/apache/cassandra/net/OutboundConnectionInitiator.java#L273]
and then re-contact the peer this time with version 11. But according to my
log snippet of cassandra7 above, the _OutboundConnectionInitiator.decode()_
method instead is unable to execute the code at line 267, which result in an
exception being thrown and catched at [line
363|https://github.com/apache/cassandra/blob/2a4cd36475de3eb47207cd88d2d472b876c6816d/src/java/org/apache/cassandra/net/OutboundConnectionInitiator.java#L363].
From there the
[exceptionCaught|https://github.com/apache/cassandra/blob/2a4cd36475de3eb47207cd88d2d472b876c6816d/src/java/org/apache/cassandra/net/OutboundConnectionInitiator.java#L368]
method is invoked and we can see the exception log with {{{}Failed to connect
to peer ... Connection reset by peer{}}}.
I wonder what is causing this kind of behavior:
# Is it a good practice, in version 3.11.16, write and flush the correct
messaging version (11) and then abruptly close the socket?
# How can the caller (4.1.3) be guaranteed to receive the few bytes indicating
the correct messaging? In my environment it seems that the socket abruptly
closed by the other peer is "winning" over such few response bytes.
# Is there something at netty-level (some kind of System properties) able to
mitigate such kind of behavior, either in the 4.1.3 node or on the 3.11.16 node?
# Is it possible that my environment (AWS servers, Docker Swarm) triggered
something similar to what is documented at [line
372|https://github.com/apache/cassandra/blob/2a4cd36475de3eb47207cd88d2d472b876c6816d/src/java/org/apache/cassandra/net/OutboundConnectionInitiator.java#L372]?
The comment relates to {{SslClosedEngineException}} (which is not my case),
but the reference to {{io.netty.channel.unix.Errors$NativeIoException:
readAddress(..) }}is matching my logs.
> Cluster upgrade 3.x -> 4.x fails due to IP change
> -
>
> Key: CASSANDRA-19178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19178
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Aldo
>Priority: Normal
> Attachments: cassandra7.downgrade.log, cassandra7.log
>
>
> I have a Docker swarm cluster with 3 distinct Cassandra services (named
> {_}cassandra7{_}, {_}cassandra8{_}, {_}cassandra9{_}) running on 3 different
> servers. The 3 services are running the version 3.11.16, using the official
> Cassandra image 3.11.16 on Docker Hub. The first service is configured just
> with the following environment variables
> {code:java}
> CASSANDRA_LISTEN_ADDRESS="tasks.cassandra7"
> CASSANDRA_SEEDS="tasks.cassandra7,tasks.cassandra9" {code}
> which in turn, at startup, modifies the {_}cassandra.yaml{_}. So for instance
> the _cassandra.yaml_ for the first service contains the following (and the
> rest is the image default):
> {code:java}
> # grep tasks /etc/cassandra/cassandra.yaml
> - seeds: "tasks.cassandra7,tasks.cassandra9"
> listen_address: tasks.cassandra7
> broadcast_address: tasks.cassandra7
> broadcast_rpc_address: tasks.cassandra7 {code}
> Other services (8 and 9) have a similar configuration, obviously with a
> different {{CASSANDRA_LISTEN_ADDRESS }}(\{{{}tasks.cassandra8}} and
> {{{}tasks.cassandra9{}}}).
> The cluster is running smoothly and all the nodes are perfectly able to
> rejoin the cluster whichever event occurs, thanks to the Docker Swarm
> {{tasks.cassandraXXX}} "hostname": i can kill a Docker container waiting for
> Docker swarm to restart it, force
[jira] [Updated] (CASSANDRA-19016) CEP-15: (C*) per-table transactional configuration
[ https://issues.apache.org/jira/browse/CASSANDRA-19016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-19016: Change Category: Operability Complexity: Normal Fix Version/s: 5.x Status: Open (was: Triage Needed) > CEP-15: (C*) per-table transactional configuration > -- > > Key: CASSANDRA-19016 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19016 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Normal > Fix For: 5.x > > > Accord configuration options should be rolled into as few options as > possible, with as few touch points as possible and, with support for > per-table configuration -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18902) Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest.explicitEndpointIgnore
[ https://issues.apache.org/jira/browse/CASSANDRA-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794413#comment-17794413 ] Jacek Lewandowski commented on CASSANDRA-18902: --- https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/1157/workflows/db16c4ca-a05b-4bdb-9627-fc587e87ce4c > Test failure: > org.apache.cassandra.distributed.test.MigrationCoordinatorTest.explicitEndpointIgnore > --- > > Key: CASSANDRA-18902 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18902 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 5.0-rc, 5.x > > > Repeated run from `cassandra-4.1` > [https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/941/workflows/46fc6cb7-135e-4862-b9d3-6996c0993de8] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16895) Build with Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794412#comment-17794412
]
Ekaterina Dimitrova commented on CASSANDRA-16895:
-
Pending closure of the epic on CASSANDRA-18239
I understand it will be merged after Accord is merged to save some work for the
authors. CASSANDRA-18239 has already been assigned to another epic, so I mark
it only as a related ticket here. Jira does not allow more than one epic
assigned to a ticket.
> Build with Java 17
> --
>
> Key: CASSANDRA-16895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16895
> Project: Cassandra
> Issue Type: Epic
> Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> This ticket is intended to group all issues found to support Java 17 in the
> future.
> Upgrade steps:
> * [Dependencies
> |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
> be updated (not all but at least those that require an update in order to
> work with Java 17)
> * More encapsulated JDK internal APIs. Some of the issues might be solved
> with the dependencies updates
> * Currently trunk compiles if we remove the Nashorn dependency (ant script
> tag, used for the test environment; UDFs) . The oracle recommendation to use
> Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
> we will opt in for graal-sdk licensed under UPL
> * All tests to be cleaned
> * CI environment to be setup
> *NOTE:* GC tuning, performance testing were never agreed to be part of this
> ticket.
> Below is a snapshot of current CI failures with JDK17, it will be updated on
> a regular basis with a date of update
> *July 15th 2023*
> || ||Failing Test Classes||Ticket Numbers||
> | |_Python DTests_| |
> |1|-test_sjk-|CASSANDRA-18343|
> | |_Java Ditributed Tests_| |
> |1-6|-org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest - all
> tests,-
> -org.apache.cassandra.distributed.test.PrepareBatchStatementsTest - all
> tests,-
> -org.apache.cassandra.distributed.test.IPMembershipTest - both tests,-
> -org.apache.cassandra.distributed.test.MixedModeFuzzTest,-
> -org.apache.cassandra.distributed.test.ReprepareFuzzTest,-
> -org.apache.cassandra.distributed.test.ReprepareNewBehaviourTest-|CASSANDRA-16304|
> |7,8|-org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
> - all tests-
> -org.apache.cassandra.distributed.test.InternodeEncryptionOptionsTest - all
> tests-|Both tests suffer from CASSANDRA-18180 -
> *ready to commit; blocked on being ready to drop JDK8*
>
> fwiw, using the CASSANDRA-18180 branch, only the
> negotiatedProtocolMustBeAcceptedProtocolTest fails in both these tests.
>
> EDIT: We will need a ticket for this one post CASSANDRA-18180. TLSv1.1 failed
> to negotiate (netty complains about certificate_unknown). Changes in JDK17
> config to be checked - done
>
> EDIT2: CASSANDRA-18540|
> |-9-|-org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest
> - 2 tests-|CASSANDRA-18180 ready to commit; blocked on being ready to drop
> JDK8|
> | |_Unit Tests_| |
> |1|-org.apache.cassandra.repair.RepairJobTest - 1 test-|CASSANDRA-18329|
> |2|-org.apache.cassandra.security.SSLFactoryTest - all tests-|CASSANDRA-17992|
> |3,4|-org.apache.cassandra.db.memtable.MemtableSizeOffheapBuffersTest,-
> -org.apache.cassandra.utils.concurrent.RefCountedTest-|CASSANDRA-18329|
> |5,6|-org.apache.cassandra.cql3.validation.entities.UFJavaTest,-
> -org.apache.cassandra.cql3.validation.entities.UFSecurityTest-|CASSANDRA-18190;
> ready to commit; blocked on being ready to drop JDK8|
> |7|-org.apache.cassandra.cql3.EmptyValuesTest-|CASSANDRA-18436|
> |8|{-}org.apache.cassandra.transport.MessagePayloadTest{-}.jdk17-|CASSANDRA-18437|
> |9|-StandaloneSplitterWithCQLTesterTest/testSplittingMultipleSSTables-|CASSANDRA-18685|
> | |_Burn tests_| |
> |1|-org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression-|CASSANDRA-18570|
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19031) [Analytics] Fix bulk writing when using identifiers that need quotes
[ https://issues.apache.org/jira/browse/CASSANDRA-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Guerrero updated CASSANDRA-19031: --- Test and Documentation Plan: Added unit and integration tests validating mixed case or keywords in column names, keyspace and table names. Status: Patch Available (was: In Progress) PR: https://github.com/apache/cassandra-analytics/pull/20 > [Analytics] Fix bulk writing when using identifiers that need quotes > > > Key: CASSANDRA-19031 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19031 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > In the Cassandra Analytics library, when writing tables that need quoted > identifiers, writes to Spark Cassandra Bulk Analytics fails. We need to make > sure that mixed-case and reserved words are properly quoted when writing > keyspaces / tables as well as column names that need quotes. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] Cassandra 18852: Make bulk writer resilient to cluster resize events [cassandra-analytics]
yifan-c commented on code in PR #17:
URL:
https://github.com/apache/cassandra-analytics/pull/17#discussion_r1419342286
##
cassandra-analytics-integration-tests/src/test/java/org/apache/cassandra/analytics/expansion/JoiningDoubleClusterTest.java:
##
@@ -0,0 +1,194 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.cassandra.analytics.expansion;
+
+import java.util.Collection;
+import java.util.concurrent.Callable;
+import java.util.concurrent.CountDownLatch;
+import java.util.concurrent.TimeUnit;
+
+import com.google.common.util.concurrent.Uninterruptibles;
+import org.junit.jupiter.api.TestInfo;
+
+import com.datastax.driver.core.ConsistencyLevel;
+import net.bytebuddy.ByteBuddy;
+import net.bytebuddy.description.type.TypeDescription;
+import net.bytebuddy.dynamic.ClassFileLocator;
+import net.bytebuddy.dynamic.TypeResolutionStrategy;
+import net.bytebuddy.dynamic.loading.ClassLoadingStrategy;
+import net.bytebuddy.implementation.MethodDelegation;
+import net.bytebuddy.implementation.bind.annotation.SuperCall;
+import net.bytebuddy.pool.TypePool;
+import org.apache.cassandra.analytics.TestUninterruptibles;
+import org.apache.cassandra.testing.CassandraIntegrationTest;
+import org.apache.cassandra.testing.ConfigurableCassandraTestContext;
+import org.apache.cassandra.utils.Shared;
+
+import static net.bytebuddy.matcher.ElementMatchers.named;
+import static net.bytebuddy.matcher.ElementMatchers.takesArguments;
+
+
+public class JoiningDoubleClusterTest extends JoiningTestBase
+{
+@CassandraIntegrationTest(nodesPerDc = 5, newNodesPerDc = 5, network =
true, buildCluster = false)
+void oneReadAllWrite(ConfigurableCassandraTestContext
cassandraTestContext, TestInfo testInfo) throws Exception
+{
+BBHelperDoubleClusterSize.reset();
+runJoiningTestScenario(cassandraTestContext,
+ BBHelperDoubleClusterSize::install,
+ BBHelperDoubleClusterSize.transientStateStart,
+ BBHelperDoubleClusterSize.transientStateEnd,
+ ConsistencyLevel.ONE,
+ ConsistencyLevel.ALL,
+ false,
+ testInfo.getDisplayName());
+}
+
+@CassandraIntegrationTest(nodesPerDc = 5, newNodesPerDc = 5, network =
true, buildCluster = false)
+void oneReadAllWriteFailure(ConfigurableCassandraTestContext
cassandraTestContext, TestInfo testInfo) throws Exception
+{
+BBHelperDoubleClusterSizeFailure.reset();
+runJoiningTestScenario(cassandraTestContext,
+ BBHelperDoubleClusterSizeFailure::install,
+
BBHelperDoubleClusterSizeFailure.transientStateStart,
+
BBHelperDoubleClusterSizeFailure.transientStateEnd,
+ ConsistencyLevel.ONE,
+ ConsistencyLevel.ALL,
+ true,
+ testInfo.getDisplayName());
+}
+
+@CassandraIntegrationTest(nodesPerDc = 5, newNodesPerDc = 5, network =
true, buildCluster = false)
+void quorumReadQuorumWrite(ConfigurableCassandraTestContext
cassandraTestContext, TestInfo testInfo) throws Exception
+{
+BBHelperDoubleClusterSize.reset();
+runJoiningTestScenario(cassandraTestContext,
+ BBHelperDoubleClusterSize::install,
+ BBHelperDoubleClusterSize.transientStateStart,
+ BBHelperDoubleClusterSize.transientStateEnd,
+ ConsistencyLevel.QUORUM,
+ ConsistencyLevel.QUORUM,
+ false,
+ testInfo.getDisplayName());
+}
+
+@CassandraIntegrationTest(nodesPerDc = 5, newNodesPerDc = 5, network =
true, buildCluster = false)
+void quorumReadQuorumWriteFailure(ConfigurableCassandraTestContext
cassandraTestContext, TestInfo testInfo) throws Exception
+{
+BBHelperDoubleClusterSizeFailure.reset();
+
[jira] [Comment Edited] (CASSANDRA-18796) Optionally fail when a non-partition-restricted query is issued against a storage-attached index with a backing table using LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-18796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794117#comment-17794117
]
Stefan Miklosovic edited comment on CASSANDRA-18796 at 12/7/23 6:24 PM:
Thank you all for the guidance, I reworked the patch to reflect this new
approach. I opened the patch for the review (1)
Couple points though:
1) It is done only for SAI, I think that it would be cool to do this for all
indexes, "old" secondary indexes too. Tell me if this is a must in this patch
or not.
2) I am not completely sure how to know if underlying query is without
partition keys in QueryController.maybeTriggerGuardrails method.
QueryController just knows what is the first and the last PrimaryKey of such
query. The trick I did is that it is a range query (hence without partition
keys) if the firstPrimaryKey is equal to lastPrimaryKey. In that case it is
basically whole ring, that's how I understand it. Maybe there is better way but
I am not sure about that. Keep in mind that this is also happening on replicas
only. This is not an issue in SelectStatement where we have more rich API to
work with. We may completely get rid of this check on replicas if we think that
check in SelectStatement is enough.
3) There is a test case checking warning path for 3 nodes. Failure path has to
be still finished.
4) it would be cool to know exactly what the violations were, per violated
replica. The way Warnings and its Counter is done for now is that as it merges
responses from replicas, it will always merge it in such a way that we only
know maximum. So if there are three nodes, one read from 5 referenced indexes,
the second one from 10 and the third one from 15, we will see all replicas here
but the maximum showed will be 15 - and we do not know what node it is. This
would require further refactoring, like a gauge, per node, or still counter,
but we can not choose max.
5) Lastly, we debugged this quite in depth with [~maedhroz] yesterday but I
noticed upon testing that warnings and failures do not produce same message to
client.
Warning looks like this:
{code}
LogResult{mark=346824, result=[WARN [node1_isolatedExecutor:1] node1
2023-12-07 11:18:46,539 All nodes [/127.0.0.1:7012, /127.0.0.2:7012,
/127.0.0.3:7012] referenced more than allowed number of indexes without
restrictions on partition key, maximum on a node being 3 indexes, and issued
warnings for query SELECT * FROM distributed_test_keyspace.t_0 WHERE v1 =
1701944326319 ALLOW FILTERING (see
maximum_sstables_with_non_paritition_key_restricted_query_warn_threshold)]}
{code}
However, failure looks like this:
{code}
stefan@cqlsh> select * from cycling.cyclist_semi_pro2 where country = 'ITA';
ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read]
message="Operation failed - received 0 responses and 1 failures:
READ_TOO_MANY_INDEXES from localhost/127.0.0.1:7000" info={'consistency':
'ONE', 'required_responses': 1, 'received_responses': 0, 'failures': 1,
'error_code_map': {'127.0.0.1': '0x0007'}}
{code}
The reason why this is happening is unknown yet, I think it is a bug but we do
not know where yet. For starters, when this is called upon failure (2), it will
not trigger this (3) which will not update ClientWarnings and it will go with
that raw message only which is quite a bummer. I would love if [~dcapwell] took
a look to have a fresh set of eyes on this as we are not sure what is happening
there.
(1) https://github.com/apache/cassandra/pull/2961
(2)
https://github.com/apache/cassandra/blob/cassandra-5.0/src/java/org/apache/cassandra/service/reads/ReadCallback.java#L181
(3)
https://github.com/apache/cassandra/blob/cassandra-5.0/src/java/org/apache/cassandra/service/reads/ReadCallback.java#L130-L141
was (Author: smiklosovic):
Thank you all for the guidance, I reworked the patch to reflect this new
approach. I opened the patch for the review (1)
Couple points though:
1) It is done only for SAI, I think that it would be cool to do this for all
indexes, "old" secondary indexes too. Tell me if this is a must in this patch
or not.
2) I am not completely sure how to know if underlying query is without
partition keys in QueryController.maybeTriggerGuardrails method.
QueryController just knows what is the first and the last PrimaryKey of such
query. The trick I did is that it is a range query (hence without partition
keys) if the firstPrimaryKey is equal to lastPrimaryKey. In that case it is
basically whole ring, that's how I understand it. Maybe there is better way but
I am not sure about that. Keep in mind that this is also happening on replicas
only. This is not an issue in SelectStatement where we have more rich API to
work with. We may completely get rid of this check on replicas if we think that
check in SelectStatement is enough.
3) There is a test case checking warning
[jira] [Assigned] (CASSANDRA-19058) Test Failure: org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest-_jdk11
[ https://issues.apache.org/jira/browse/CASSANDRA-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe reassigned CASSANDRA-19058: --- Assignee: Alex Petrov (was: Sam Tunnicliffe) > Test Failure: > org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest-_jdk11 > > > Key: CASSANDRA-19058 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19058 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Sam Tunnicliffe >Assignee: Alex Petrov >Priority: Normal > Fix For: 5.1-alpha1 > > > butler shows this as failing on J17 but here we see it fail on J11 > [https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20463/tests] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19024 Fix bulk reading when using identifiers that need quotes [cassandra-analytics]
frankgh closed pull request #19: CASSANDRA-19024 Fix bulk reading when using identifiers that need quotes URL: https://github.com/apache/cassandra-analytics/pull/19 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19024 Fix bulk reading when using identifiers that need quotes [cassandra-analytics]
frankgh commented on PR #19: URL: https://github.com/apache/cassandra-analytics/pull/19#issuecomment-1845780320 Closed via https://github.com/apache/cassandra-analytics/commit/457b36bcb3c8a865cca83ca6c402246798113ab4 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19024) [Analytics] Fix bulk reading when using identifiers that need quotes
[ https://issues.apache.org/jira/browse/CASSANDRA-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Guerrero updated CASSANDRA-19024: --- Fix Version/s: NA Since Version: NA Source Control Link: https://github.com/apache/cassandra-analytics/commit/457b36bcb3c8a865cca83ca6c402246798113ab4 Resolution: Fixed Status: Resolved (was: Ready to Commit) > [Analytics] Fix bulk reading when using identifiers that need quotes > > > Key: CASSANDRA-19024 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19024 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Fix For: NA > > Time Spent: 3.5h > Remaining Estimate: 0h > > In the Cassandra Analytics library, when reading tables that need quoted > identifiers, reading from Spark Cassandra Bulk Analytics fails. We need to > make sure that mixed-case and reserved words are properly quoted when reading > keyspaces / tables that need quotes. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19024) [Analytics] Fix bulk reading when using identifiers that need quotes
[ https://issues.apache.org/jira/browse/CASSANDRA-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Guerrero updated CASSANDRA-19024: --- Status: Ready to Commit (was: Review In Progress) > [Analytics] Fix bulk reading when using identifiers that need quotes > > > Key: CASSANDRA-19024 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19024 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Time Spent: 3.5h > Remaining Estimate: 0h > > In the Cassandra Analytics library, when reading tables that need quoted > identifiers, reading from Spark Cassandra Bulk Analytics fails. We need to > make sure that mixed-case and reserved words are properly quoted when reading > keyspaces / tables that need quotes. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19169) Don't NPE when initializing CFSs for local system keyspaces with UCS
[ https://issues.apache.org/jira/browse/CASSANDRA-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-19169: Since Version: NA Source Control Link: https://github.com/apache/cassandra/commit/8d6d1774e4008263bb381ae9d6b14b8f10f12fca Resolution: Fixed Status: Resolved (was: Ready to Commit) > Don't NPE when initializing CFSs for local system keyspaces with UCS > > > Key: CASSANDRA-19169 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19169 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 5.1-alpha1 > > > When UnifiedCompactionStrategy is used as the default, NPEs are thrown when > flushing the system keyspace tables early during startup. The system keyspace > is > initialised before the cluster metadata, but UCS currently tries to access the > current epoch when initialising the shard manager, to determine whether the > local ranges are out of date. This isn't necessary for the system keyspaces as > they use LocalStrategy and cover the whole token space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19024) [Analytics] Fix bulk reading when using identifiers that need quotes
[ https://issues.apache.org/jira/browse/CASSANDRA-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRA-19024: -- Reviewers: Yifan Cai (was: Yifan Cai, Yifan Cai) > [Analytics] Fix bulk reading when using identifiers that need quotes > > > Key: CASSANDRA-19024 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19024 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Time Spent: 3.5h > Remaining Estimate: 0h > > In the Cassandra Analytics library, when reading tables that need quoted > identifiers, reading from Spark Cassandra Bulk Analytics fails. We need to > make sure that mixed-case and reserved words are properly quoted when reading > keyspaces / tables that need quotes. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19171) Test Failure: org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig-cdc_jdk17_x86_64
[
https://issues.apache.org/jira/browse/CASSANDRA-19171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-19171:
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/b4701177335216fc6131b9303cfe926da9016129
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Test Failure:
> org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig-cdc_jdk17_x86_64
> -
>
> Key: CASSANDRA-19171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19171
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-beta
>
>
> h3.
> {code:java}
> Error Message
> Multiple entries with same key: 127.0.0.1:7012=OTHER_DC1:OTHER_RAC1 and
> 127.0.0.1:7012=DC1:RAC1
> Stacktrace
> java.lang.IllegalArgumentException: Multiple entries with same key:
> 127.0.0.1:7012=OTHER_DC1:OTHER_RAC1 and 127.0.0.1:7012=DC1:RAC1 at
> com.google.common.collect.ImmutableMap.conflictException(ImmutableMap.java:378)
> at
> com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:372)
> at
> com.google.common.collect.RegularImmutableMap.checkNoConflictInKeyBucket(RegularImmutableMap.java:246)
> at
> com.google.common.collect.RegularImmutableMap.fromEntryArrayCheckingBucketOverflow(RegularImmutableMap.java:133)
> at
> com.google.common.collect.RegularImmutableMap.fromEntryArray(RegularImmutableMap.java:95)
> at
> com.google.common.collect.RegularImmutableMap.fromEntries(RegularImmutableMap.java:78)
> at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:139) at
> org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig(PropertyFileSnitchTest.java:121)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19102) Test Failure: org.apache.cassandra.distributed.test.ReadRepairTest#readRepairRTRangeMovementTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-19102:
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/28630ccbbf48a484284c0e7a9a6a7aa097136af0
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Test Failure:
> org.apache.cassandra.distributed.test.ReadRepairTest#readRepairRTRangeMovementTest
>
>
> Key: CASSANDRA-19102
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19102
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Jacek Lewandowski
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-beta
>
>
> {noformat}
> java.lang.AssertionError: Expected a different error message, but got
> Operation failed - received 2 responses and 1 failures: INVALID_ROUTING from
> /127.0.0.2:7012
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> org.apache.cassandra.distributed.test.ReadRepairTest.readRepairRTRangeMovementTest(ReadRepairTest.java:424)
> 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)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
> at
> com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
> at
> com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:232)
> at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:55)
> {noformat}
> Manual testing in IntelliJ / trunk. Detected during investigation of test
> failures of CASSANDRA-18464
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19072) Test failure: org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-19072:
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/1df9148ed177ddefd5ffae893756944661419464
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
thanks!
> Test failure:
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
> --
>
> Key: CASSANDRA-19072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19072
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> CircleCI failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20464/tests
> Also failing on 17: Circleci Failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20500/tests
> {code}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest(FetchLogFromPeersTest.java:217)
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) 01/04: Avoid NPEs when initializing CFSs from local keyspaces before ClusterMetadata is available
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
commit 8d6d1774e4008263bb381ae9d6b14b8f10f12fca
Author: Sam Tunnicliffe
AuthorDate: Tue Dec 5 12:54:05 2023 +
Avoid NPEs when initializing CFSs from local keyspaces before
ClusterMetadata is available
Patch by Sam Tunnicliffe; reviewed by Alex Petrov for CASSANDRA-19169
---
src/java/org/apache/cassandra/db/ColumnFamilyStore.java | 3 +--
.../cassandra/db/compaction/UnifiedCompactionStrategy.java| 11 ---
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
b/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
index 83957a6260..1dc2687c40 100644
--- a/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
+++ b/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
@@ -1495,9 +1495,8 @@ public class ColumnFamilyStore implements
ColumnFamilyStoreMBean, Memtable.Owner
public VersionedLocalRanges localRangesWeighted()
{
-ClusterMetadata metadata = ClusterMetadata.current();
if (!SchemaConstants.isLocalSystemKeyspace(getKeyspaceName())
-&& getPartitioner() == metadata.partitioner)
+&& getPartitioner() == ClusterMetadata.current().partitioner)
{
DiskBoundaryManager.VersionedRangesAtEndpoint versionedLocalRanges
= DiskBoundaryManager.getVersionedLocalRanges(this);
Set> localRanges =
versionedLocalRanges.rangesAtEndpoint.ranges();
diff --git
a/src/java/org/apache/cassandra/db/compaction/UnifiedCompactionStrategy.java
b/src/java/org/apache/cassandra/db/compaction/UnifiedCompactionStrategy.java
index 0cb1f46cc8..361f67d8cb 100644
--- a/src/java/org/apache/cassandra/db/compaction/UnifiedCompactionStrategy.java
+++ b/src/java/org/apache/cassandra/db/compaction/UnifiedCompactionStrategy.java
@@ -302,10 +302,15 @@ public class UnifiedCompactionStrategy extends
AbstractCompactionStrategy
synchronized (this)
{
// Recheck after entering critical section, another thread may
have beaten us to it.
-while (shardManager == null ||
shardManager.isOutOfDate(ClusterMetadata.current().epoch.getEpoch()))
+while (shardManager == null ||
+ // Short circuit for local keyspaces which may be
initialised before ClusterMetadata
+ (cfs.localRangesWeighted().ringVersion !=
ColumnFamilyStore.RING_VERSION_IRRELEVANT
+&&
shardManager.isOutOfDate(ClusterMetadata.current().epoch.getEpoch(
+{
shardManager = ShardManager.create(cfs);
-// Note: this can just as well be done without the synchronization
(races would be benign, just doing some
-// redundant work). For the current usages of this blocking is
fine and expected to perform no worse.
+// Note: this can just as well be done without the
synchronization (races would be benign, just doing some
+// redundant work). For the current usages of this blocking is
fine and expected to perform no worse.
+}
}
}
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) 02/04: Update expected error message which is too specific
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
commit 28630ccbbf48a484284c0e7a9a6a7aa097136af0
Author: Sam Tunnicliffe
AuthorDate: Tue Dec 5 17:03:24 2023 +
Update expected error message which is too specific
Patch by Sam Tunnicliffe; reviewed by Alex Petrov for CASSANDRA-19102
---
.../org/apache/cassandra/distributed/test/ReadRepairTest.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/test/distributed/org/apache/cassandra/distributed/test/ReadRepairTest.java
b/test/distributed/org/apache/cassandra/distributed/test/ReadRepairTest.java
index 7d459d511d..aa676717db 100644
--- a/test/distributed/org/apache/cassandra/distributed/test/ReadRepairTest.java
+++ b/test/distributed/org/apache/cassandra/distributed/test/ReadRepairTest.java
@@ -422,7 +422,7 @@ public class ReadRepairTest extends TestBaseImpl
{
Throwable cause = e.getCause();
Assert.assertTrue("Expected a different error message, but got " +
cause.getMessage(),
- cause.getMessage().contains("Operation failed -
received 1 responses and 1 failures: INVALID_ROUTING from /127.0.0.2:7012"));
+ cause.getMessage().contains("INVALID_ROUTING
from /127.0.0.2:7012"));
}
catch (InterruptedException e)
{
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) 03/04: Fix potential for unintended address clash in test case
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 commit b4701177335216fc6131b9303cfe926da9016129 Author: Sam Tunnicliffe AuthorDate: Wed Dec 6 09:10:26 2023 + Fix potential for unintended address clash in test case Patch by Sam Tunnicliffe; reviewed by Alex Petrov for CASSANDRA-19171 --- test/unit/org/apache/cassandra/locator/PropertyFileSnitchTest.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/unit/org/apache/cassandra/locator/PropertyFileSnitchTest.java b/test/unit/org/apache/cassandra/locator/PropertyFileSnitchTest.java index d05c7efea0..1b4b4311b0 100644 --- a/test/unit/org/apache/cassandra/locator/PropertyFileSnitchTest.java +++ b/test/unit/org/apache/cassandra/locator/PropertyFileSnitchTest.java @@ -117,7 +117,7 @@ public class PropertyFileSnitchTest // Locations of remote peers should not be accessible from this snitch unless // they are present in ClusterMetadata Random r = new Random(System.nanoTime()); -InetAddressAndPort peer = MembershipUtils.randomEndpoint(r); +InetAddressAndPort peer = MembershipUtils.endpoint(99); replaceConfigFile(ImmutableMap.of(localAddress.getHostAddressAndPort(), "DC1:RAC1", peer.getHostAddressAndPort(), "OTHER_DC1:OTHER_RAC1")); PropertyFileSnitch snitch = new PropertyFileSnitch(); - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) 04/04: Fix FetchLogFromPeersTest with vnodes
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
commit 1df9148ed177ddefd5ffae893756944661419464
Author: Sam Tunnicliffe
AuthorDate: Wed Dec 6 14:14:24 2023 +
Fix FetchLogFromPeersTest with vnodes
Patch by Sam Tunnicliffe; reviewed by Alex Petrov for CASSANDRA-19072
---
.../distributed/test/log/FetchLogFromPeersTest.java| 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git
a/test/distributed/org/apache/cassandra/distributed/test/log/FetchLogFromPeersTest.java
b/test/distributed/org/apache/cassandra/distributed/test/log/FetchLogFromPeersTest.java
index d0ad1f2f34..91218e4fbb 100644
---
a/test/distributed/org/apache/cassandra/distributed/test/log/FetchLogFromPeersTest.java
+++
b/test/distributed/org/apache/cassandra/distributed/test/log/FetchLogFromPeersTest.java
@@ -165,7 +165,11 @@ public class FetchLogFromPeersTest extends TestBaseImpl
@Test
public void catchupCoordinatorBehindTestPlacements() throws Exception
{
+// Only runs in non-vnode configuration, because whether node2 is a
replica or not before/after
+// depends on the number of tokens but this is set externally to the
test. The actual behaviour
+// under test is completely orthogonal to the actual number of tokens
though.
try (Cluster cluster = init(builder().withNodes(3)
+ .withoutVNodes()
.withTokenSupplier(TokenSupplier.evenlyDistributedTokens(4))
.withNodeIdTopology(NetworkTopology.singleDcNetworkTopology(4, "dc0", "rack0"))
.start()))
@@ -181,7 +185,7 @@ public class FetchLogFromPeersTest extends TestBaseImpl
cluster.get(1).shutdown().get();
-// node2 is behind, reading from it will cause a failure, but it
will then catch up
+// node2 is behind, writing to it will cause a failure, but it
will then catch up
try
{
cluster.coordinator(2).execute(withKeyspace("insert into
%s.tbl (id) values (3)"), ConsistencyLevel.QUORUM);
@@ -196,7 +200,11 @@ public class FetchLogFromPeersTest extends TestBaseImpl
@Test
public void catchupCoordinatorAheadPlacementsReadTest() throws Exception
{
+// Only runs in non-vnode configuration, because whether node2 is a
replica or not before/after
+// depends on the number of tokens but this is set externally to the
test. The actual behaviour
+// under test is completely orthogonal to the actual number of tokens
though.
try (Cluster cluster = init(builder().withNodes(4)
+ .withoutVNodes()
.start()))
{
cluster.schemaChange(withKeyspace("alter keyspace %s with
replication = {'class':'SimpleStrategy', 'replication_factor':3}"));
@@ -221,7 +229,11 @@ public class FetchLogFromPeersTest extends TestBaseImpl
@Test
public void catchupCoordinatorAheadPlacementsWriteTest() throws Throwable
{
+// Only runs in non-vnode configuration, because whether node2 is a
replica or not before/after
+// depends on the number of tokens but this is set externally to the
test. The actual behaviour
+// under test is completely orthogonal to the actual number of tokens
though.
try (Cluster cluster = init(builder().withNodes(4)
+ .withoutVNodes()
.start()))
{
cluster.schemaChange(withKeyspace("alter keyspace %s with
replication = {'class':'SimpleStrategy', 'replication_factor':3}"));
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) branch trunk updated (a75814c8f4 -> 1df9148ed1)
This is an automated email from the ASF dual-hosted git repository. samt pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from a75814c8f4 Merge branch 'cassandra-5.0' into trunk new 8d6d1774e4 Avoid NPEs when initializing CFSs from local keyspaces before ClusterMetadata is available new 28630ccbbf Update expected error message which is too specific new b470117733 Fix potential for unintended address clash in test case new 1df9148ed1 Fix FetchLogFromPeersTest with vnodes The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: src/java/org/apache/cassandra/db/ColumnFamilyStore.java| 3 +-- .../cassandra/db/compaction/UnifiedCompactionStrategy.java | 11 --- .../apache/cassandra/distributed/test/ReadRepairTest.java | 2 +- .../distributed/test/log/FetchLogFromPeersTest.java| 14 +- .../apache/cassandra/locator/PropertyFileSnitchTest.java | 2 +- 5 files changed, 24 insertions(+), 8 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19072) Test failure: org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794356#comment-17794356
]
Sam Tunnicliffe commented on CASSANDRA-19072:
-
I've switched the two newly modified tests to just use {{withoutVNodes}} as
it's probably a bit clearer. For clarity/consistency I've also added that to
{{catchupCoordinatorBehindTestPlacements}}, even though it's actually redundant.
> Test failure:
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
> --
>
> Key: CASSANDRA-19072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19072
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> CircleCI failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20464/tests
> Also failing on 17: Circleci Failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20500/tests
> {code}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest(FetchLogFromPeersTest.java:217)
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19024) [Analytics] Fix bulk reading when using identifiers that need quotes
[ https://issues.apache.org/jira/browse/CASSANDRA-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794357#comment-17794357 ] Yifan Cai commented on CASSANDRA-19024: --- +1 on the patch. > [Analytics] Fix bulk reading when using identifiers that need quotes > > > Key: CASSANDRA-19024 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19024 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Time Spent: 3.5h > Remaining Estimate: 0h > > In the Cassandra Analytics library, when reading tables that need quoted > identifiers, reading from Spark Cassandra Bulk Analytics fails. We need to > make sure that mixed-case and reserved words are properly quoted when reading > keyspaces / tables that need quotes. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19024) [Analytics] Fix bulk reading when using identifiers that need quotes
[ https://issues.apache.org/jira/browse/CASSANDRA-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRA-19024: -- Reviewers: Yifan Cai, Yifan Cai Status: Review In Progress (was: Patch Available) > [Analytics] Fix bulk reading when using identifiers that need quotes > > > Key: CASSANDRA-19024 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19024 > Project: Cassandra > Issue Type: Bug > Components: Analytics Library >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Time Spent: 3.5h > Remaining Estimate: 0h > > In the Cassandra Analytics library, when reading tables that need quoted > identifiers, reading from Spark Cassandra Bulk Analytics fails. We need to > make sure that mixed-case and reserved words are properly quoted when reading > keyspaces / tables that need quotes. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-19094) Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov reassigned CASSANDRA-19094:
---
Assignee: Alex Petrov
> Test Failure: org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest
> --
>
> Key: CASSANDRA-19094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19094
> Project: Cassandra
> Issue Type: Bug
>Reporter: Michael Semb Wever
>Assignee: Alex Petrov
>Priority: Normal
>
> Seen in j11_simulator_dtests in CASSANDRA-19034
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/259/workflows/f343d3e3-00cf-4e13-bb4d-bbfff1d3658c/jobs/21101/tests
> {noformat}
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:537)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1098)
> at
> org.apache.cassandra.simulator.ClusterSimulation.close(ClusterSimulation.java:854)
> at
> org.apache.cassandra.simulator.test.SimulationTestBase.simulate(SimulationTestBase.java:206)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.simulate(HarrySimulatorTest.java:361)
> at
> org.apache.cassandra.simulator.test.HarrySimulatorTest.harryTest(HarrySimulatorTest.java:135)
> 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)
> Caused by: java.util.concurrent.ExecutionException:
> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:254)
> at
> org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:529)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$47(Instance.java:978)
> at
> org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
> at
> org.apache.cassandra.simulator.systems.SimulatedExecution$NoIntercept$1Run.run(SimulatedExecution.java:82)
> at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$InterceptingPooledExecutor$WaitingThread.lambda$new$1(InterceptingExecutor.java:318)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.RuntimeException:
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Direct
> buffer memory
> at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$46(Instance.java:972)
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$async$10(IsolatedExecutor.java:156)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.OutOfMemoryError: Direct buffer memory
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.getWhenDone(AbstractFuture.java:239)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:246)
> at
> org.apache.cassandra.hints.HintsService.shutdownBlocking(HintsService.java:282)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$shutdown$17(Instance.java:901)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$parallelRun$52(Instance.java:1196)
> Caused by: java.lang.OutOfMemoryError: Direct buffer memory
> at java.base/java.nio.Bits.reserveMemory(Bits.java:175)
> at java.base/java.nio.DirectByteBuffer.(DirectByteBuffer.java:118)
> at
[jira] [Commented] (CASSANDRA-19169) Don't NPE when initializing CFSs for local system keyspaces with UCS
[
https://issues.apache.org/jira/browse/CASSANDRA-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794354#comment-17794354
]
Sam Tunnicliffe commented on CASSANDRA-19169:
-
yep, definitely and {{cfs.localRangesWeighted()}} includes a similar check
which results in them using {{{}RING_VERSION_IRRELEVANT{}}}. In the end I went
with this as it seemed more to be more explicitly showing that the
{{shardManager}} can't be out of date because the version is irrelevant.
> Don't NPE when initializing CFSs for local system keyspaces with UCS
>
>
> Key: CASSANDRA-19169
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19169
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
>
> When UnifiedCompactionStrategy is used as the default, NPEs are thrown when
> flushing the system keyspace tables early during startup. The system keyspace
> is
> initialised before the cluster metadata, but UCS currently tries to access the
> current epoch when initialising the shard manager, to determine whether the
> local ranges are out of date. This isn't necessary for the system keyspaces as
> they use LocalStrategy and cover the whole token space.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19072) Test failure: org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794347#comment-17794347
]
Alex Petrov commented on CASSANDRA-19072:
-
I haven't realised your approach would also result in
{{AssumptionViolatedException}}, I assumed it would force a single token test.
+1 then.
> Test failure:
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
> --
>
> Key: CASSANDRA-19072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19072
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> CircleCI failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20464/tests
> Also failing on 17: Circleci Failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20500/tests
> {code}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest(FetchLogFromPeersTest.java:217)
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19072) Test failure: org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19072:
Reviewers: Alex Petrov, Alex Petrov
Alex Petrov, Alex Petrov (was: Alex Petrov)
Status: Review In Progress (was: Patch Available)
> Test failure:
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
> --
>
> Key: CASSANDRA-19072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19072
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> CircleCI failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20464/tests
> Also failing on 17: Circleci Failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20500/tests
> {code}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest(FetchLogFromPeersTest.java:217)
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19072) Test failure: org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19072:
Status: Ready to Commit (was: Review In Progress)
> Test failure:
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
> --
>
> Key: CASSANDRA-19072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19072
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> CircleCI failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20464/tests
> Also failing on 17: Circleci Failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20500/tests
> {code}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest(FetchLogFromPeersTest.java:217)
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19072) Test failure: org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794344#comment-17794344
]
Sam Tunnicliffe commented on CASSANDRA-19072:
-
I used the same approach as {{catchupCoordinatorBehindTestPlacements}} which
was preexisting in the test class and also requires a single token. That one
_does_ need to configure the token supplier explicitly because it adds a node
to the cluster after starting. This particular fix would indeed work with
{{{}withoutVNodes(){}}}, but this seems to be essentially equivalent to what I
did here as both methods ultimately result in the test being skipped with
{{{}AssumptionViolatedException{}}}.
I don't quite follow what you mean about overriding tests and re-running with
unexpected config.
> Test failure:
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
> --
>
> Key: CASSANDRA-19072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19072
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> CircleCI failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20464/tests
> Also failing on 17: Circleci Failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20500/tests
> {code}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest(FetchLogFromPeersTest.java:217)
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19173) Test Failure: dtest-novnode.cqlsh_tests.test_cqlsh_copy.TestCqlshCopy.test_round_trip_with_sub_second_precision
[
https://issues.apache.org/jira/browse/CASSANDRA-19173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794340#comment-17794340
]
Brandon Williams commented on CASSANDRA-19173:
--
I haven't been able to reproduce this locally.
> Test Failure:
> dtest-novnode.cqlsh_tests.test_cqlsh_copy.TestCqlshCopy.test_round_trip_with_sub_second_precision
> ---
>
> Key: CASSANDRA-19173
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19173
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.1-beta
>
>
> {quote}
> h3.
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1785/testReport/dtest-novnode.cqlsh_tests.test_cqlsh_copy/TestCqlshCopy/test_round_trip_with_sub_second_precision/
> Error Message
> AssertionError: assert [['1', '1943-06-19 11:21:01.000+'], ['2',
> '1943-06-19 11:21:01.123+'], ['3', '1943-06-19 11:21:01.124+']] ==
> [['3', '1943-06-19 11:21:01.124+']] At index 0 diff: ['1', '1943-06-19
> 11:21:01.000+'] != ['3', '1943-06-19 11:21:01.124+'] Left contains 2
> more items, first extra item: ['2', '1943-06-19 11:21:01.123+'] Full
> diff: [ + ['1', + '1943-06-19 11:21:01.000+'], + ['2', + '1943-06-19
> 11:21:01.123+'], ['3', '1943-06-19 11:21:01.124+'], ]
> h3. Stacktrace
> self =
> @since('3.4') def test_round_trip_with_sub_second_precision(self): """ Test
> that we can import and export timestamp values with millisecond precision: -
> create a csv file and import it - export the data and check the values are as
> expected @jira_ticket CASSANDRA-10428 """ self.prepare()
> self.session.execute("create TABLE testsubsecond(id int PRIMARY KEY, subid
> timestamp)") tempfile1 = self.get_temp_file() tempfile2 =
> self.get_temp_file() with open(tempfile1.name, 'w') as csvfile: writer =
> csv.writer(csvfile) writer.writerow([1, '1943-06-19 11:21:01+'])
> writer.writerow([2, '1943-06-19 11:21:01.123+']) writer.writerow([3,
> '1943-06-19 11:21:01.123456+']) logger.debug('Importing from csv file:
> {}'.format(tempfile1.name)) self.run_cqlsh(cmds="COPY ks.testsubsecond FROM
> '{}'".format(tempfile1.name)) logger.debug('Exporting to csv file:
> {}'.format(tempfile2.name)) self.run_cqlsh(cmds="COPY ks.testsubsecond TO
> '{}'".format(tempfile2.name)) csv_results =
> sorted(list(csv_rows(tempfile2.name))) > assert [['1', '1943-06-19
> 11:21:01.000+'], ['2', '1943-06-19 11:21:01.123+'], ['3', '1943-06-19
> 11:21:01.124+']] == csv_results E AssertionError: assert [['1',
> '1943-06-19 11:21:01.000+'], ['2', '1943-06-19 11:21:01.123+'], ['3',
> '1943-06-19 11:21:01.124+']] == [['3', '1943-06-19 11:21:01.124+']] E
> At index 0 diff: ['1', '1943-06-19 11:21:01.000+'] != ['3', '1943-06-19
> 11:21:01.124+'] E Left contains 2 more items, first extra item: ['2',
> '1943-06-19 11:21:01.123+'] E Full diff: E [ E + ['1', E + '1943-06-19
> 11:21:01.000+'], E + ['2', E + '1943-06-19 11:21:01.123+'], E ['3', E
> '1943-06-19 11:21:01.124+'], E ] cqlsh_tests/test_cqlsh_copy.py:2005:
> AssertionError
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19104) Standardize tablestats formatting and data units
[ https://issues.apache.org/jira/browse/CASSANDRA-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794334#comment-17794334 ] Leo Toff commented on CASSANDRA-19104: -- [~bschoeni] Yeah, some questionable marketing tricks forced the industry to clearly define binary prefixes KiB/MiB/GiB. What is 500GB? Is it 500,000,000,000 bytes (500 * 10^9) or 536,870,912,000 bytes (500 * 2^30)? I think it could be either while 500 * 10^9 is ~7% less which is a significant cost reduction "strategy" for the manufacturer. At the same time, 500GiB is definitively 500 * 2^30 bytes. > Standardize tablestats formatting and data units > > > Key: CASSANDRA-19104 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19104 > Project: Cassandra > Issue Type: Bug > Components: Tool/nodetool >Reporter: Brad Schoening >Assignee: Leo Toff >Priority: Normal > > Tablestats reports output in plaintext, JSON or YAML. The human readable > output currently has a mix of KiB, bytes with inconsistent spacing > Simplify and default output to 'human readable'. Machine readable output is > available as an option and the current mixed output formatting is neither > friendly for human or machine reading and can be replaced. > !image-2023-11-27-13-49-14-247.png! > *Not a goal now (consider a follow up Jira):* > Fix inconsistencies with KiB/MiB/GiB and KB/MB/GB formatting: > * gcstats - uses MB > * getcompactionthroughput - uses MB/s > * getstreamthroughput - uses MB/s > * info - uses MiB/GiB -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19163) Test Failure: org.apache.cassandra.db.DiskBoundaryManagerTest.alterKeyspaceTest-cdc_jdk17_x86_64
[
https://issues.apache.org/jira/browse/CASSANDRA-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19163:
Resolution: Duplicate
Status: Resolved (was: Open)
> Test Failure:
> org.apache.cassandra.db.DiskBoundaryManagerTest.alterKeyspaceTest-cdc_jdk17_x86_64
>
> -
>
> Key: CASSANDRA-19163
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19163
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1801/testReport/org.apache.cassandra.db/DiskBoundaryManagerTest/alterKeyspaceTest_cdc_jdk17_x86_64/]
> {code:java}
> Error Message
> expected not same
> Stacktrace
> junit.framework.AssertionFailedError: expected not same at
> org.apache.cassandra.db.DiskBoundaryManagerTest.alterKeyspaceTest(DiskBoundaryManagerTest.java:140)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19163) Test Failure: org.apache.cassandra.db.DiskBoundaryManagerTest.alterKeyspaceTest-cdc_jdk17_x86_64
[
https://issues.apache.org/jira/browse/CASSANDRA-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794310#comment-17794310
]
Alex Petrov commented on CASSANDRA-19163:
-
Test is different, but I believe the root cause is the same, especially given
the error is the same.
> Test Failure:
> org.apache.cassandra.db.DiskBoundaryManagerTest.alterKeyspaceTest-cdc_jdk17_x86_64
>
> -
>
> Key: CASSANDRA-19163
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19163
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.1-beta
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1801/testReport/org.apache.cassandra.db/DiskBoundaryManagerTest/alterKeyspaceTest_cdc_jdk17_x86_64/]
> {code:java}
> Error Message
> expected not same
> Stacktrace
> junit.framework.AssertionFailedError: expected not same at
> org.apache.cassandra.db.DiskBoundaryManagerTest.alterKeyspaceTest(DiskBoundaryManagerTest.java:140)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19171) Test Failure: org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig-cdc_jdk17_x86_64
[
https://issues.apache.org/jira/browse/CASSANDRA-19171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19171:
Status: Ready to Commit (was: Review In Progress)
+1
> Test Failure:
> org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig-cdc_jdk17_x86_64
> -
>
> Key: CASSANDRA-19171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19171
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-beta
>
>
> h3.
> {code:java}
> Error Message
> Multiple entries with same key: 127.0.0.1:7012=OTHER_DC1:OTHER_RAC1 and
> 127.0.0.1:7012=DC1:RAC1
> Stacktrace
> java.lang.IllegalArgumentException: Multiple entries with same key:
> 127.0.0.1:7012=OTHER_DC1:OTHER_RAC1 and 127.0.0.1:7012=DC1:RAC1 at
> com.google.common.collect.ImmutableMap.conflictException(ImmutableMap.java:378)
> at
> com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:372)
> at
> com.google.common.collect.RegularImmutableMap.checkNoConflictInKeyBucket(RegularImmutableMap.java:246)
> at
> com.google.common.collect.RegularImmutableMap.fromEntryArrayCheckingBucketOverflow(RegularImmutableMap.java:133)
> at
> com.google.common.collect.RegularImmutableMap.fromEntryArray(RegularImmutableMap.java:95)
> at
> com.google.common.collect.RegularImmutableMap.fromEntries(RegularImmutableMap.java:78)
> at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:139) at
> org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig(PropertyFileSnitchTest.java:121)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19171) Test Failure: org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig-cdc_jdk17_x86_64
[
https://issues.apache.org/jira/browse/CASSANDRA-19171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19171:
Reviewers: Alex Petrov, Alex Petrov
Alex Petrov, Alex Petrov (was: Alex Petrov)
Status: Review In Progress (was: Patch Available)
> Test Failure:
> org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig-cdc_jdk17_x86_64
> -
>
> Key: CASSANDRA-19171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19171
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-beta
>
>
> h3.
> {code:java}
> Error Message
> Multiple entries with same key: 127.0.0.1:7012=OTHER_DC1:OTHER_RAC1 and
> 127.0.0.1:7012=DC1:RAC1
> Stacktrace
> java.lang.IllegalArgumentException: Multiple entries with same key:
> 127.0.0.1:7012=OTHER_DC1:OTHER_RAC1 and 127.0.0.1:7012=DC1:RAC1 at
> com.google.common.collect.ImmutableMap.conflictException(ImmutableMap.java:378)
> at
> com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:372)
> at
> com.google.common.collect.RegularImmutableMap.checkNoConflictInKeyBucket(RegularImmutableMap.java:246)
> at
> com.google.common.collect.RegularImmutableMap.fromEntryArrayCheckingBucketOverflow(RegularImmutableMap.java:133)
> at
> com.google.common.collect.RegularImmutableMap.fromEntryArray(RegularImmutableMap.java:95)
> at
> com.google.common.collect.RegularImmutableMap.fromEntries(RegularImmutableMap.java:78)
> at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:139) at
> org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig(PropertyFileSnitchTest.java:121)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19169) Don't NPE when initializing CFSs for local system keyspaces with UCS
[ https://issues.apache.org/jira/browse/CASSANDRA-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-19169: Reviewers: Alex Petrov, Alex Petrov Alex Petrov, Alex Petrov (was: Alex Petrov) Status: Review In Progress (was: Patch Available) > Don't NPE when initializing CFSs for local system keyspaces with UCS > > > Key: CASSANDRA-19169 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19169 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 5.1-alpha1 > > > When UnifiedCompactionStrategy is used as the default, NPEs are thrown when > flushing the system keyspace tables early during startup. The system keyspace > is > initialised before the cluster metadata, but UCS currently tries to access the > current epoch when initialising the shard manager, to determine whether the > local ranges are out of date. This isn't necessary for the system keyspaces as > they use LocalStrategy and cover the whole token space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19169) Don't NPE when initializing CFSs for local system keyspaces with UCS
[ https://issues.apache.org/jira/browse/CASSANDRA-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-19169: Status: Ready to Commit (was: Review In Progress) > Don't NPE when initializing CFSs for local system keyspaces with UCS > > > Key: CASSANDRA-19169 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19169 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 5.1-alpha1 > > > When UnifiedCompactionStrategy is used as the default, NPEs are thrown when > flushing the system keyspace tables early during startup. The system keyspace > is > initialised before the cluster metadata, but UCS currently tries to access the > current epoch when initialising the shard manager, to determine whether the > local ranges are out of date. This isn't necessary for the system keyspaces as > they use LocalStrategy and cover the whole token space. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18999) Gossiper::hasMajorVersion3Nodes returns true when a cluster is upgrading patch version without Cassandra 3 nodes.
[
https://issues.apache.org/jira/browse/CASSANDRA-18999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isaac Reath updated CASSANDRA-18999:
Test and Documentation Plan: Added new test cases to GossiperTest.java
which validate that the Gossiper works correctly given the behavior described
in the ticket.
Status: Patch Available (was: Open)
> Gossiper::hasMajorVersion3Nodes returns true when a cluster is upgrading
> patch version without Cassandra 3 nodes.
> -
>
> Key: CASSANDRA-18999
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18999
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Distributed Metadata
>Reporter: Isaac Reath
>Assignee: Isaac Reath
>Priority: Low
> Labels: lhf
> Fix For: 4.0.x, 4.1.x, 5.0.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When working on https://issues.apache.org/jira/browse/CASSANDRA-18968 we
> found that {{Gossiper::hasMajorVersion3Nodes}} will return true when the
> cluster is undergoing an upgrade from a patch version even if the cluster has
> no Cassandra 3 nodes in it.
> This can be reproduced by running this Gossiper test:
> {code:java}
> @Test
> public void
> testHasVersion3NodesShouldReturnFalseWhenNoVersion3NodesDetectedAndCassandra4UpgradeInProgress()
> throws Exception
> {
> Gossiper.instance.start(0);
> Gossiper.instance.expireUpgradeFromVersion();
> VersionedValue.VersionedValueFactory factory = new
> VersionedValue.VersionedValueFactory(null);
> EndpointState es = new EndpointState((HeartBeatState) null);
> es.addApplicationState(ApplicationState.RELEASE_VERSION,
> factory.releaseVersion(CURRENT_VERSION.toString()));
>
> Gossiper.instance.endpointStateMap.put(InetAddressAndPort.getByName("127.0.0.1"),
> es);
>
> Gossiper.instance.liveEndpoints.add(InetAddressAndPort.getByName("127.0.0.1"));
> es = new EndpointState((HeartBeatState) null);
> String previousPatchVersion = String.valueOf(CURRENT_VERSION.major) +
> '.' + (CURRENT_VERSION.minor) + '.' + (CURRENT_VERSION.patch - 1);
> es.addApplicationState(ApplicationState.RELEASE_VERSION,
> factory.releaseVersion(previousPatchVersion));
>
> Gossiper.instance.endpointStateMap.put(InetAddressAndPort.getByName("127.0.0.2"),
> es);
>
> Gossiper.instance.liveEndpoints.add(InetAddressAndPort.getByName("127.0.0.2"));
> assertFalse(Gossiper.instance.hasMajorVersion3Nodes());
> }
> {code}
> This seems to be because of
> [https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L2360],
> where an upgrade in progress is possible but we are not upgrading from a
> lower family version (i.e from 4.1.1 to 4.1.2).
> From the comment in this function, it seems instead of the existing check, we
> would want to iterate over all known endpoints in gossip and return true if
> any of them do not have a version (similar to
> [https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L227-L236)
>
> |https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L227-L236).]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18999) Gossiper::hasMajorVersion3Nodes returns true when a cluster is upgrading patch version without Cassandra 3 nodes.
[
https://issues.apache.org/jira/browse/CASSANDRA-18999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794303#comment-17794303
]
Isaac Reath commented on CASSANDRA-18999:
-
Looks like this function was removed on trunk in
[https://github.com/apache/cassandra/commit/ae0842372ff6dd1437d026f82968a3749f555ff4#diff-99267a2170b04fd7dd24d6c6bf2ba1fc26d6dc896cd74f8c5bd56c476e2540e4L2458-L2464]
as part of adding TCM. Since it's all removed there, I applied the same fix
as 4.0 and 4.1 instead of removing the code entirely on the patch to 5.0.
> Gossiper::hasMajorVersion3Nodes returns true when a cluster is upgrading
> patch version without Cassandra 3 nodes.
> -
>
> Key: CASSANDRA-18999
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18999
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Distributed Metadata
>Reporter: Isaac Reath
>Assignee: Isaac Reath
>Priority: Low
> Labels: lhf
> Fix For: 4.0.x, 4.1.x, 5.0.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When working on https://issues.apache.org/jira/browse/CASSANDRA-18968 we
> found that {{Gossiper::hasMajorVersion3Nodes}} will return true when the
> cluster is undergoing an upgrade from a patch version even if the cluster has
> no Cassandra 3 nodes in it.
> This can be reproduced by running this Gossiper test:
> {code:java}
> @Test
> public void
> testHasVersion3NodesShouldReturnFalseWhenNoVersion3NodesDetectedAndCassandra4UpgradeInProgress()
> throws Exception
> {
> Gossiper.instance.start(0);
> Gossiper.instance.expireUpgradeFromVersion();
> VersionedValue.VersionedValueFactory factory = new
> VersionedValue.VersionedValueFactory(null);
> EndpointState es = new EndpointState((HeartBeatState) null);
> es.addApplicationState(ApplicationState.RELEASE_VERSION,
> factory.releaseVersion(CURRENT_VERSION.toString()));
>
> Gossiper.instance.endpointStateMap.put(InetAddressAndPort.getByName("127.0.0.1"),
> es);
>
> Gossiper.instance.liveEndpoints.add(InetAddressAndPort.getByName("127.0.0.1"));
> es = new EndpointState((HeartBeatState) null);
> String previousPatchVersion = String.valueOf(CURRENT_VERSION.major) +
> '.' + (CURRENT_VERSION.minor) + '.' + (CURRENT_VERSION.patch - 1);
> es.addApplicationState(ApplicationState.RELEASE_VERSION,
> factory.releaseVersion(previousPatchVersion));
>
> Gossiper.instance.endpointStateMap.put(InetAddressAndPort.getByName("127.0.0.2"),
> es);
>
> Gossiper.instance.liveEndpoints.add(InetAddressAndPort.getByName("127.0.0.2"));
> assertFalse(Gossiper.instance.hasMajorVersion3Nodes());
> }
> {code}
> This seems to be because of
> [https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L2360],
> where an upgrade in progress is possible but we are not upgrading from a
> lower family version (i.e from 4.1.1 to 4.1.2).
> From the comment in this function, it seems instead of the existing check, we
> would want to iterate over all known endpoints in gossip and return true if
> any of them do not have a version (similar to
> [https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L227-L236)
>
> |https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L227-L236).]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18999) Gossiper::hasMajorVersion3Nodes returns true when a cluster is upgrading patch version without Cassandra 3 nodes.
[
https://issues.apache.org/jira/browse/CASSANDRA-18999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isaac Reath updated CASSANDRA-18999:
Fix Version/s: (was: 5.x)
> Gossiper::hasMajorVersion3Nodes returns true when a cluster is upgrading
> patch version without Cassandra 3 nodes.
> -
>
> Key: CASSANDRA-18999
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18999
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Distributed Metadata
>Reporter: Isaac Reath
>Assignee: Isaac Reath
>Priority: Low
> Labels: lhf
> Fix For: 4.0.x, 4.1.x, 5.0.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When working on https://issues.apache.org/jira/browse/CASSANDRA-18968 we
> found that {{Gossiper::hasMajorVersion3Nodes}} will return true when the
> cluster is undergoing an upgrade from a patch version even if the cluster has
> no Cassandra 3 nodes in it.
> This can be reproduced by running this Gossiper test:
> {code:java}
> @Test
> public void
> testHasVersion3NodesShouldReturnFalseWhenNoVersion3NodesDetectedAndCassandra4UpgradeInProgress()
> throws Exception
> {
> Gossiper.instance.start(0);
> Gossiper.instance.expireUpgradeFromVersion();
> VersionedValue.VersionedValueFactory factory = new
> VersionedValue.VersionedValueFactory(null);
> EndpointState es = new EndpointState((HeartBeatState) null);
> es.addApplicationState(ApplicationState.RELEASE_VERSION,
> factory.releaseVersion(CURRENT_VERSION.toString()));
>
> Gossiper.instance.endpointStateMap.put(InetAddressAndPort.getByName("127.0.0.1"),
> es);
>
> Gossiper.instance.liveEndpoints.add(InetAddressAndPort.getByName("127.0.0.1"));
> es = new EndpointState((HeartBeatState) null);
> String previousPatchVersion = String.valueOf(CURRENT_VERSION.major) +
> '.' + (CURRENT_VERSION.minor) + '.' + (CURRENT_VERSION.patch - 1);
> es.addApplicationState(ApplicationState.RELEASE_VERSION,
> factory.releaseVersion(previousPatchVersion));
>
> Gossiper.instance.endpointStateMap.put(InetAddressAndPort.getByName("127.0.0.2"),
> es);
>
> Gossiper.instance.liveEndpoints.add(InetAddressAndPort.getByName("127.0.0.2"));
> assertFalse(Gossiper.instance.hasMajorVersion3Nodes());
> }
> {code}
> This seems to be because of
> [https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L2360],
> where an upgrade in progress is possible but we are not upgrading from a
> lower family version (i.e from 4.1.1 to 4.1.2).
> From the comment in this function, it seems instead of the existing check, we
> would want to iterate over all known endpoints in gossip and return true if
> any of them do not have a version (similar to
> [https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L227-L236)
>
> |https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/gms/Gossiper.java#L227-L236).]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19102) Test Failure: org.apache.cassandra.distributed.test.ReadRepairTest#readRepairRTRangeMovementTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19102:
Status: Ready to Commit (was: Review In Progress)
+1, LGTM
> Test Failure:
> org.apache.cassandra.distributed.test.ReadRepairTest#readRepairRTRangeMovementTest
>
>
> Key: CASSANDRA-19102
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19102
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Jacek Lewandowski
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-beta
>
>
> {noformat}
> java.lang.AssertionError: Expected a different error message, but got
> Operation failed - received 2 responses and 1 failures: INVALID_ROUTING from
> /127.0.0.2:7012
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> org.apache.cassandra.distributed.test.ReadRepairTest.readRepairRTRangeMovementTest(ReadRepairTest.java:424)
> 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)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
> at
> com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
> at
> com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:232)
> at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:55)
> {noformat}
> Manual testing in IntelliJ / trunk. Detected during investigation of test
> failures of CASSANDRA-18464
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19102) Test Failure: org.apache.cassandra.distributed.test.ReadRepairTest#readRepairRTRangeMovementTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19102:
Reviewers: Alex Petrov, Alex Petrov
Alex Petrov, Alex Petrov (was: Alex Petrov)
Status: Review In Progress (was: Patch Available)
> Test Failure:
> org.apache.cassandra.distributed.test.ReadRepairTest#readRepairRTRangeMovementTest
>
>
> Key: CASSANDRA-19102
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19102
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Jacek Lewandowski
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-beta
>
>
> {noformat}
> java.lang.AssertionError: Expected a different error message, but got
> Operation failed - received 2 responses and 1 failures: INVALID_ROUTING from
> /127.0.0.2:7012
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> org.apache.cassandra.distributed.test.ReadRepairTest.readRepairRTRangeMovementTest(ReadRepairTest.java:424)
> 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)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
> at
> com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
> at
> com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:232)
> at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:55)
> {noformat}
> Manual testing in IntelliJ / trunk. Detected during investigation of test
> failures of CASSANDRA-18464
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19126) Streaming appears to be incompatible with different storage_compatibility_mode settings
[
https://issues.apache.org/jira/browse/CASSANDRA-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794298#comment-17794298
]
Jacek Lewandowski commented on CASSANDRA-19126:
---
Reading the exception, it looks like there is also a minor problem of
incorrectly handling (actually lack of handling) non-success result in
{{OutboundConnectionInitiator}}.
> Streaming appears to be incompatible with different
> storage_compatibility_mode settings
> ---
>
> Key: CASSANDRA-19126
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19126
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming, Legacy/Streaming and Messaging,
> Messaging/Internode, Tool/bulk load
>Reporter: Branimir Lambov
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> In particular, SSTableLoader appears to be incompatible with
> storage_compatibility_mode: NONE, which manifests as a failure of
> {{org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest}}
> when the flag is turned on (found during CASSANDRA-18753 testing). Setting
> {{storage_compatibility_mode: NONE}} in the tool configuration yaml does not
> help (according to the docs, this setting is not picked up).
> This is likely a bigger problem as the acceptable streaming version for C* 5
> is 12 only in legacy mode and 13 only in none, i.e. two C* 5 nodes do not
> appear to be able to stream with each other if their setting for the
> compatibility mode is different.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19072) Test failure: org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794299#comment-17794299
]
Alex Petrov commented on CASSANDRA-19072:
-
Just wondering, why not use `.withoutVNodes();` assumption, and instead
override tests? If we use an assumption, the test will simply be skipped as
opposted to run again with an unexpected configuration.
> Test failure:
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest-_jdk11
> --
>
> Key: CASSANDRA-19072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19072
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Alex Petrov
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> CircleCI failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20464/tests
> Also failing on 17: Circleci Failure:
> https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/256/workflows/c4fda8f1-a8d6-4523-be83-5e30b9de39fe/jobs/20500/tests
> {code}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.distributed.test.log.FetchLogFromPeersTest.catchupCoordinatorAheadPlacementsReadTest(FetchLogFromPeersTest.java:217)
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] Cassandra 18852: Make bulk writer resilient to cluster resize events [cassandra-analytics]
yifan-c commented on code in PR #17:
URL:
https://github.com/apache/cassandra-analytics/pull/17#discussion_r1419125362
##
cassandra-analytics-core/src/test/java/org/apache/cassandra/spark/bulkwriter/RecordWriterTest.java:
##
@@ -346,19 +366,22 @@ void writeBuffered()
private void validateSuccessfulWrite(MockBulkWriterContext writerContext,
Iterator> data,
- String[] columnNames)
+ String[] columnNames) throws
InterruptedException
{
validateSuccessfulWrite(writerContext, data, columnNames,
UPLOADED_TABLES);
}
private void validateSuccessfulWrite(MockBulkWriterContext writerContext,
Iterator> data,
String[] columnNames,
- int uploadedTables)
+ int uploadedTables) throws
InterruptedException
{
RecordWriter rw = new RecordWriter(writerContext, columnNames, () ->
tc, SSTableWriter::new);
rw.write(data);
+// Wait for uploads to finish
+Thread.sleep(500);
Review Comment:
Thanks for the improvement!
##
cassandra-analytics-core/src/test/java/org/apache/cassandra/spark/bulkwriter/RecordWriterTest.java:
##
@@ -346,19 +366,22 @@ void writeBuffered()
private void validateSuccessfulWrite(MockBulkWriterContext writerContext,
Iterator> data,
- String[] columnNames)
+ String[] columnNames) throws
InterruptedException
{
validateSuccessfulWrite(writerContext, data, columnNames,
UPLOADED_TABLES);
}
private void validateSuccessfulWrite(MockBulkWriterContext writerContext,
Iterator> data,
String[] columnNames,
- int uploadedTables)
+ int uploadedTables) throws
InterruptedException
{
RecordWriter rw = new RecordWriter(writerContext, columnNames, () ->
tc, SSTableWriter::new);
rw.write(data);
+// Wait for uploads to finish
+Thread.sleep(500);
Review Comment:
Thanks for making the improvement!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-19126) Streaming appears to be incompatible with different storage_compatibility_mode settings
[
https://issues.apache.org/jira/browse/CASSANDRA-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski reassigned CASSANDRA-19126:
-
Assignee: Jacek Lewandowski
> Streaming appears to be incompatible with different
> storage_compatibility_mode settings
> ---
>
> Key: CASSANDRA-19126
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19126
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming, Legacy/Streaming and Messaging,
> Messaging/Internode, Tool/bulk load
>Reporter: Branimir Lambov
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> In particular, SSTableLoader appears to be incompatible with
> storage_compatibility_mode: NONE, which manifests as a failure of
> {{org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest}}
> when the flag is turned on (found during CASSANDRA-18753 testing). Setting
> {{storage_compatibility_mode: NONE}} in the tool configuration yaml does not
> help (according to the docs, this setting is not picked up).
> This is likely a bigger problem as the acceptable streaming version for C* 5
> is 12 only in legacy mode and 13 only in none, i.e. two C* 5 nodes do not
> appear to be able to stream with each other if their setting for the
> compatibility mode is different.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-19039) Test failure: org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski reassigned CASSANDRA-19039:
-
Assignee: Jacek Lewandowski
> Test failure: org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest
> --
>
> Key: CASSANDRA-19039
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19039
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Change Data Capture, Test/unit
>Reporter: Berenguer Blasi
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0-rc, 5.x
>
>
> CommitLogSegmentManagerCDCTest presents a number of failures. Some were test
> errors and some product problems which were addressed in CASSANDRA-18948 but
> some remain and they smell like product a problem:
> -
> [testReplayLogic|https://app.circleci.com/pipelines/github/bereng/cassandra/1112/workflows/caf6d499-bf31-4ce8-8c60-32a8d3daeef3/jobs/33581/tests]
> {noformat}
> junit.framework.AssertionFailedError: Expected 0 files in CDC folder after
> deletion. expected:<0> but was:<1>
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testReplayLogic(CommitLogSegmentManagerCDCTest.java:277)
> 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)
> {noformat}
> -
> [testCompletedFlag|https://app.circleci.com/pipelines/github/bereng/cassandra/1112/workflows/caf6d499-bf31-4ce8-8c60-32a8d3daeef3/jobs/33567/tests]
> {noformat}
> junit.framework.AssertionFailedError: Timeout occurred. Please note the time
> in the report does not reflect the time until the timeout.
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.util.Vector.forEach(Vector.java:1365)
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.util.Vector.forEach(Vector.java:1365)
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
> -
> [testNonblockingShouldMaintainSteadyDiskUsage|https://app.circleci.com/pipelines/github/bereng/cassandra/1112/workflows/2f918b36-6d43-4708-988a-9da3bc0df545/jobs/33551/tests]
> {noformat}
> junit.framework.AssertionFailedError: Actual size (0) should be at least the
> mutation size (1747626)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.lambda$testNonblockingShouldMaintainSteadyDiskUsage$1(CommitLogSegmentManagerCDCTest.java:128)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testWithCDCSpaceInMb(CommitLogSegmentManagerCDCTest.java:427)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.lambda$testNonblockingShouldMaintainSteadyDiskUsage$2(CommitLogSegmentManagerCDCTest.java:119)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testWithNonblockingMode(CommitLogSegmentManagerCDCTest.java:413)
> at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage(CommitLogSegmentManagerCDCTest.java:119)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
> -
> [testSwitchingCDCWriteModes|https://app.circleci.com/pipelines/github/bereng/cassandra/1115/workflows/b53b04f0-609b-451e-a964-ac3dfc173b82/jobs/33854/tests]
> {noformat}
> junit.framework.AssertionFailedError: Timeout occurred. Please note the time
> in the report does not reflect the time until the timeout.
>
