[jira] [Updated] (CASSANDRA-18924) TCM: Allow unknown nodes during discovery
[ https://issues.apache.org/jira/browse/CASSANDRA-18924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-18924: Status: Ready to Commit (was: Review In Progress) +1 > TCM: Allow unknown nodes during discovery > - > > Key: CASSANDRA-18924 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18924 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: High > > * avoid discovered.addAll(DatabaseDescriptor.getSeeds()) when starting > discovery to exclude them from the final result > * add responded node to discovered set, even if it responds with an > empty set > * Implement a simple simulation for discovery that does not involve > setting up entire clusters > * Allow _any_ seed to start up first -- 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-18924) TCM: Allow unknown nodes during discovery
[ https://issues.apache.org/jira/browse/CASSANDRA-18924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-18924: Reviewers: Sam Tunnicliffe Status: Review In Progress (was: Patch Available) > TCM: Allow unknown nodes during discovery > - > > Key: CASSANDRA-18924 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18924 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: High > > * avoid discovered.addAll(DatabaseDescriptor.getSeeds()) when starting > discovery to exclude them from the final result > * add responded node to discovered set, even if it responds with an > empty set > * Implement a simple simulation for discovery that does not involve > setting up entire clusters > * Allow _any_ seed to start up first -- 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-18933) Correct comment for nc SSTable format
[
https://issues.apache.org/jira/browse/CASSANDRA-18933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1076#comment-1076
]
Berenguer Blasi commented on CASSANDRA-18933:
-
CI run is missing?
> Correct comment for nc SSTable format
> -
>
> Key: CASSANDRA-18933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18933
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In [CASSANDRA-18134 |https://issues.apache.org/jira/browse/CASSANDRA-18134],
> the {{nc}} SSTable format was introduced. The patch was merged into {{5.0+}},
> however the comment in source incorrectly mentions that the format was added
> to version {{4.1}}.
--
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] [Created] (CASSANDRA-18942) Repetable test runs
Berenguer Blasi created CASSANDRA-18942: --- Summary: Repetable test runs Key: CASSANDRA-18942 URL: https://issues.apache.org/jira/browse/CASSANDRA-18942 Project: Cassandra Issue Type: New Feature Reporter: Berenguer Blasi Assignee: Berenguer Blasi It is our policy to loop new introduced tests to avoid introducing flakies. We also want to add the possibility to repeat a test N number of times to test robustness, debug flakies, etc. -- 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-18942) Repetable test runs
[ https://issues.apache.org/jira/browse/CASSANDRA-18942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-18942: Component/s: Build CI Epic Link: CASSANDRA-18137 Fix Version/s: 5.0 5.0.x > Repetable test runs > --- > > Key: CASSANDRA-18942 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18942 > Project: Cassandra > Issue Type: New Feature > Components: Build, CI >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 5.0, 5.0.x > > > It is our policy to loop new introduced tests to avoid introducing flakies. > We also want to add the possibility to repeat a test N number of times to > test robustness, debug flakies, etc. -- 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-18942) Repetable test runs
[ https://issues.apache.org/jira/browse/CASSANDRA-18942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-18942: Change Category: Operability Complexity: Normal Status: Open (was: Triage Needed) > Repetable test runs > --- > > Key: CASSANDRA-18942 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18942 > Project: Cassandra > Issue Type: New Feature > Components: Build, CI >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 5.0, 5.0.x > > > It is our policy to loop new introduced tests to avoid introducing flakies. > We also want to add the possibility to repeat a test N number of times to > test robustness, debug flakies, etc. -- 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-builds] branch trunk updated: ninja-fix: negate condition on version filtering (CASSANDRA-18133)
This is an automated email from the ASF dual-hosted git repository.
smiklosovic pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-builds.git
The following commit(s) were added to refs/heads/trunk by this push:
new f63d4a2 ninja-fix: negate condition on version filtering
(CASSANDRA-18133)
f63d4a2 is described below
commit f63d4a27c92e8578c3ecd78dd0d2218a1c69966d
Author: Stefan Miklosovic
AuthorDate: Thu Oct 19 09:17:48 2023 +0200
ninja-fix: negate condition on version filtering (CASSANDRA-18133)
---
build-scripts/cassandra-dtest-pytest.sh | 2 +-
build-scripts/cassandra-test.sh | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/build-scripts/cassandra-dtest-pytest.sh
b/build-scripts/cassandra-dtest-pytest.sh
index 208b14a..824d09a 100755
--- a/build-scripts/cassandra-dtest-pytest.sh
+++ b/build-scripts/cassandra-dtest-pytest.sh
@@ -33,7 +33,7 @@ java_version=$(java -version 2>&1 | awk -F '"' '/version/
{print $2}' | awk -F.
version=$(grep 'property\s*name=\"base.version\"' build.xml |sed -ne
's/.*value=\"\([^"]*\)\".*/\1/p')
regx_version="(2.2|3.0|3.11|4.0|4.1)(.([0-9]+))?$"
-if [[ $version =~ $regx_version ]] ; then
+if [[ ! $version =~ $regx_version ]] ; then
echo "This script is deprecated, having been migrated to be in-tree since
5.0, see .build/run-python-dtests.sh"
exit 1
fi
diff --git a/build-scripts/cassandra-test.sh b/build-scripts/cassandra-test.sh
index e623cc3..a0046c5 100755
--- a/build-scripts/cassandra-test.sh
+++ b/build-scripts/cassandra-test.sh
@@ -88,7 +88,7 @@ _main() {
local -r version=$(grep 'property\s*name=\"base.version\"' build.xml |sed
-ne 's/.*value=\"\([^"]*\)\".*/\1/p')
local -r regx_version="(2.2|3.0|3.11|4.0|4.1)(.([0-9]+))?$"
- if [[ $version =~ $regx_version ]] ; then
+ if [[ ! $version =~ $regx_version ]] ; then
echo "This script is deprecated, having been migrated to be in-tree
since 5.0, see .build/run-tests.sh"
exit 1
fi
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cep-21-tcm-review updated (064f07b13d -> 4e23ee87ad)
This is an automated email from the ASF dual-hosted git repository. blerer pushed a change to branch cep-21-tcm-review in repository https://gitbox.apache.org/repos/asf/cassandra.git from 064f07b13d JAVADOC: Startup and Discovery add 6d1a20f91a Add implementation overview doc add 4e23ee87ad Guaranty the ordering of entries within Replication instances No new revisions were added by this update. Summary of changes: .../schema/DistributedMetadataLogKeyspace.java | 3 +- .../org/apache/cassandra/tcm/TCM_implementation.md | 57 ++ .../org/apache/cassandra/tcm/log/Replication.java | 39 +-- .../cassandra/tcm/log/SystemKeyspaceStorage.java | 4 +- .../test/log/SystemKeyspaceStorageTest.java| 9 ++-- .../apache/cassandra/tcm/log/LogStateTestBase.java | 10 ++-- 6 files changed, 84 insertions(+), 38 deletions(-) create mode 100644 src/java/org/apache/cassandra/tcm/TCM_implementation.md - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18145) Run entire Cassandra Jenkins in an independent GKE account
[ https://issues.apache.org/jira/browse/CASSANDRA-18145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18145: --- Summary: Run entire Cassandra Jenkins in an independent GKE account (was: Run entire Cassandra Jenkins in an independent EC2/EKS account) > Run entire Cassandra Jenkins in an independent GKE account > -- > > Key: CASSANDRA-18145 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18145 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Henrik Ingo >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 5.0.x, 5.x > > > This exercise will help clarify whether the flakiness we're seeing in ASF CI > is due to the heterogenous execution environment (hardware), or due to the > configuration environment / runtime / DSL / etc (software). -- 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-18145) Run entire Cassandra Jenkins in an independent GKE account
[ https://issues.apache.org/jira/browse/CASSANDRA-18145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18145: --- Reviewers: Aleksandr Volochnev > Run entire Cassandra Jenkins in an independent GKE account > -- > > Key: CASSANDRA-18145 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18145 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Henrik Ingo >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 5.0.x, 5.x > > > This exercise will help clarify whether the flakiness we're seeing in ASF CI > is due to the heterogenous execution environment (hardware), or due to the > configuration environment / runtime / DSL / etc (software). -- 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-18747) Test failure: Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.ca
[
https://issues.apache.org/jira/browse/CASSANDRA-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1150#comment-1150
]
Jacek Lewandowski commented on CASSANDRA-18747:
---
Few problems with testing...
On 4.1, one junit test failed but I don't believe that is related:
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/977/workflows/f6f81939-5b1e-4e17-b756-bfb8791dc23d/jobs/38838/tests
On 5.0, it turned out that {{ShortPaxosSimulationTest}} is failing. I've
retried both locally and on CI with {{cassandra-5.0}} and it fails there as
well:
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/1013/workflows/132ec030-5eae-4622-ad92-ffea76cbb5a4/jobs/39718
Additionally, {{LeaveAndBootstrapTest}} turned out to be flaky. I did some
investigation and discovered that this particular test is very sensitive to the
execution speed - when the test is executed a bit slower, it fails consistently
in the same way (both {{cassandra-5.0}} and this feature branch). The key
temporal option in this case is either Gossiper delay/interval or quarantine
delay. The failed runs were slower and Gossiper check state task was executed
wiping some endpoint from the state map due to elapsed quarantine time. Thas is
clearly visible in the logs. I'm hoping to fix this issue by increasing the
quarantine time so that it is less likely to elapse during the test.
On trunk, all tests passed.
> Test failure: Fix assertion error AssertionError: Unknown keyspace
> system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
> ---
>
> Key: CASSANDRA-18747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema, Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> I've been seeing this assertion error in different tests lately.
> Full error message:
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
> 16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
> node logs (see stdout for full details). Errors: [[node2] 'ERROR
> [PendingRangeCalculator:1] 2023-08-11 16:35:14,445
> JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeast
[jira] [Commented] (CASSANDRA-18747) Test failure: Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.ca
[
https://issues.apache.org/jira/browse/CASSANDRA-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1157#comment-1157
]
Jacek Lewandowski commented on CASSANDRA-18747:
---
Test links in the PRs
> Test failure: Fix assertion error AssertionError: Unknown keyspace
> system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
> ---
>
> Key: CASSANDRA-18747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema, Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> I've been seeing this assertion error in different tests lately.
> Full error message:
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
> 16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
> node logs (see stdout for full details). Errors: [[node2] 'ERROR
> [PendingRangeCalculator:1] 2023-08-11 16:35:14,445
> JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']{code}
> Example failures:
> test_failed_snitch_update_property_file_snitch -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2475/workflows/2086619e-0f21-464b-a866-84aca516b5e5/jobs/36716/tests]
> test_gcgs_validation -
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1666/testReport/junit/dtest.materialized_views_test/TestMaterializedViews/test_gcgs_validation/]
--
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-18747) Test failure: Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.cass
[
https://issues.apache.org/jira/browse/CASSANDRA-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-18747:
--
Status: Ready to Commit (was: Changes Suggested)
> Test failure: Fix assertion error AssertionError: Unknown keyspace
> system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
> ---
>
> Key: CASSANDRA-18747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema, Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> I've been seeing this assertion error in different tests lately.
> Full error message:
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
> 16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
> node logs (see stdout for full details). Errors: [[node2] 'ERROR
> [PendingRangeCalculator:1] 2023-08-11 16:35:14,445
> JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']{code}
> Example failures:
> test_failed_snitch_update_property_file_snitch -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2475/workflows/2086619e-0f21-464b-a866-84aca516b5e5/jobs/36716/tests]
> test_gcgs_validation -
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1666/testReport/junit/dtest.materialized_views_test/TestMaterializedViews/test_gcgs_validation/]
--
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-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1188#comment-1188 ] Maxim Muzafarov commented on CASSANDRA-18891: - [~tsteinmaurer] Hey, so, I tested the patch on my local Apple M1. It works. I have requested a few nodes from AWS (including gravitron instances) to verify the patch on different architectures and do some testing, so I'm waiting for the instances now. I'm sure we can get these changes out pretty quickly, but I don't know what version they'll ship in. > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 4.0.x > > Time Spent: 10m > Remaining Estimate: 0h > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- 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] [Created] (CASSANDRA-18943) http/2 vulnerability: CVE-2023-44487
Brandon Williams created CASSANDRA-18943: Summary: http/2 vulnerability: CVE-2023-44487 Key: CASSANDRA-18943 URL: https://issues.apache.org/jira/browse/CASSANDRA-18943 Project: Cassandra Issue Type: Bug Reporter: Brandon Williams https://nvd.nist.gov/vuln/detail/CVE-2023-44487 Basically anything using http/2 is covered by this, but we don't use it. -- 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-18943) http/2 vulnerability: CVE-2023-44487
[ https://issues.apache.org/jira/browse/CASSANDRA-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18943: - Bug Category: Parent values: Security(12985)Level 1 values: Denial of Service(13001) Complexity: Normal Component/s: Dependencies Discovered By: User Report Fix Version/s: 3.0.x 3.11.x 4.0.x 4.1.x 5.0.x 5.x Severity: Normal Assignee: Brandon Williams Status: Open (was: Triage Needed) > http/2 vulnerability: CVE-2023-44487 > > > Key: CASSANDRA-18943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18943 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > https://nvd.nist.gov/vuln/detail/CVE-2023-44487 > Basically anything using http/2 is covered by this, but we don't use it. -- 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-18942) Repeatable test runs
[ https://issues.apache.org/jira/browse/CASSANDRA-18942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18942: - Summary: Repeatable test runs (was: Repetable test runs) > Repeatable test runs > > > Key: CASSANDRA-18942 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18942 > Project: Cassandra > Issue Type: New Feature > Components: Build, CI >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 5.0, 5.0.x > > > It is our policy to loop new introduced tests to avoid introducing flakies. > We also want to add the possibility to repeat a test N number of times to > test robustness, debug flakies, etc. -- 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] branch trunk updated (7d3a8d5312 -> c2c20ab843)
This is an automated email from the ASF dual-hosted git repository. jlewandowski pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 7d3a8d5312 Merge branch 'cassandra-5.0' into trunk add ac71d0f56e Fixed the inconsistency between distributedKeyspaces and distributedAndLocalKeyspaces add 57f494d8d4 Merge branch 'cassandra-4.1' into cassandra-5.0 new c2c20ab843 Merge branch 'cassandra-5.0' into trunk 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: CHANGES.txt| 2 + .../cql3/statements/DescribeStatement.java | 3 +- .../statements/schema/CreateTableStatement.java| 1 - src/java/org/apache/cassandra/db/Keyspace.java | 7 +-- .../cassandra/db/compaction/CompactionManager.java | 2 +- .../org/apache/cassandra/dht/BootStrapper.java | 2 +- .../index/sai/virtual/ColumnIndexesSystemView.java | 9 ++- .../sai/virtual/SSTableIndexesSystemView.java | 11 ++-- .../index/sai/virtual/SegmentsSystemView.java | 9 ++- .../org/apache/cassandra/metrics/TableMetrics.java | 2 +- .../repair/consistent/admin/SchemaArgsParser.java | 2 +- src/java/org/apache/cassandra/schema/Schema.java | 65 +++--- .../org/apache/cassandra/schema/SchemaEvent.java | 4 +- .../service/PendingRangeCalculatorService.java | 2 +- .../apache/cassandra/service/StorageService.java | 42 +++--- .../org/apache/cassandra/dht/BootStrapperTest.java | 2 +- .../cassandra/locator/SimpleStrategyTest.java | 4 +- .../cassandra/schema/SchemaKeyspaceTest.java | 2 +- .../org/apache/cassandra/schema/SchemaTest.java| 2 +- .../cassandra/service/LeaveAndBootstrapTest.java | 4 +- .../org/apache/cassandra/service/MoveTest.java | 4 +- 21 files changed, 77 insertions(+), 104 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (ede18e6c9f -> ac71d0f56e)
This is an automated email from the ASF dual-hosted git repository. jlewandowski pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from ede18e6c9f Merge branch 'cassandra-4.0' into cassandra-4.1 add ac71d0f56e Fixed the inconsistency between distributedKeyspaces and distributedAndLocalKeyspaces No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../cql3/statements/DescribeStatement.java | 3 +- .../statements/schema/CreateTableStatement.java| 1 - src/java/org/apache/cassandra/db/Keyspace.java | 7 +- .../cassandra/db/compaction/CompactionManager.java | 2 +- .../org/apache/cassandra/dht/BootStrapper.java | 2 +- .../org/apache/cassandra/metrics/TableMetrics.java | 2 +- .../repair/consistent/admin/SchemaArgsParser.java | 2 +- src/java/org/apache/cassandra/schema/Schema.java | 87 +- .../org/apache/cassandra/schema/SchemaEvent.java | 4 +- .../service/PendingRangeCalculatorService.java | 2 +- .../apache/cassandra/service/StorageService.java | 34 - .../org/apache/cassandra/dht/BootStrapperTest.java | 2 +- .../cassandra/locator/SimpleStrategyTest.java | 4 +- .../cassandra/schema/SchemaKeyspaceTest.java | 2 +- .../org/apache/cassandra/schema/SchemaTest.java| 2 +- .../cassandra/service/LeaveAndBootstrapTest.java | 4 +- .../org/apache/cassandra/service/MoveTest.java | 4 +- 18 files changed, 75 insertions(+), 90 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository. jlewandowski pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit c2c20ab8430246c38e375966c1c8c9d9e10dec23 Merge: 7d3a8d5312 57f494d8d4 Author: Jacek Lewandowski AuthorDate: Thu Oct 19 12:56:10 2023 +0200 Merge branch 'cassandra-5.0' into trunk * cassandra-5.0: Fixed the inconsistency between distributedKeyspaces and distributedAndLocalKeyspaces CHANGES.txt| 2 + .../cql3/statements/DescribeStatement.java | 3 +- .../statements/schema/CreateTableStatement.java| 1 - src/java/org/apache/cassandra/db/Keyspace.java | 7 +-- .../cassandra/db/compaction/CompactionManager.java | 2 +- .../org/apache/cassandra/dht/BootStrapper.java | 2 +- .../index/sai/virtual/ColumnIndexesSystemView.java | 9 ++- .../sai/virtual/SSTableIndexesSystemView.java | 11 ++-- .../index/sai/virtual/SegmentsSystemView.java | 9 ++- .../org/apache/cassandra/metrics/TableMetrics.java | 2 +- .../repair/consistent/admin/SchemaArgsParser.java | 2 +- src/java/org/apache/cassandra/schema/Schema.java | 65 +++--- .../org/apache/cassandra/schema/SchemaEvent.java | 4 +- .../service/PendingRangeCalculatorService.java | 2 +- .../apache/cassandra/service/StorageService.java | 42 +++--- .../org/apache/cassandra/dht/BootStrapperTest.java | 2 +- .../cassandra/locator/SimpleStrategyTest.java | 4 +- .../cassandra/schema/SchemaKeyspaceTest.java | 2 +- .../org/apache/cassandra/schema/SchemaTest.java| 2 +- .../cassandra/service/LeaveAndBootstrapTest.java | 4 +- .../org/apache/cassandra/service/MoveTest.java | 4 +- 21 files changed, 77 insertions(+), 104 deletions(-) diff --cc CHANGES.txt index 0a8684d7d6,89d1163f83..ed18ef6962 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -51,24 -47,6 +52,25 @@@ Merged from 3.0 * Remove commitlog_sync_batch_window_in_ms (CASSANDRA-17161) * Upgrade JMH from 1.21 to 1.36 (CASSANDRA-18696) * Add guardrail for vector dimensions (CASSANDRA-18730) +Merged from 4.1: ++ * Fixed the inconsistency between distributedKeyspaces and distributedAndLocalKeyspaces (CASSANDRA-18747) + * Waiting indefinitely on ReceivedMessage response in StreamSession#receive() can cause deadlock (CASSANDRA-18733) + * Allow empty keystore_password in encryption_options (CASSANDRA-18778) +Merged from 4.0: + * JMH improvements - faster build and async profiler (CASSANDRA-18871) +Merged from 3.11: + * Fix NPE when using udfContext in UDF after a restart of a node (CASSANDRA-18739) +Merged from 3.0: + * Add cqlshrc.sample and credentials.sample into Debian package (CASSANDRA-18818) + * Refactor validation logic in StorageService.rebuild (CASSANDRA-18803) + * Make alternation of a user type validate the same way as creation of a user type does (CASSANDRA-18585) + * Fix missing speculative retries in tablestats (CASSANDRA-18767) + * Fix Requires for Java for RPM package (CASSANDRA-18751) + * Fix CQLSH online help topic link (CASSANDRA-17534) + * Remove unused suppressions (CASSANDRA-18724) + + +5.0 * Upgraded Netty to 4.1.96, added BouncyCastle dependency (CASSANDRA-17992) * Fix for (unsupported) big endian unaligned architecture, eg s390x (CASSANDRA-17723) * CIDR filtering authorizer (CASSANDRA-18592) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-5.0 updated (e45c1092f9 -> 57f494d8d4)
This is an automated email from the ASF dual-hosted git repository. jlewandowski pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from e45c1092f9 Correctly remove Index.Group from IndexRegistry add ac71d0f56e Fixed the inconsistency between distributedKeyspaces and distributedAndLocalKeyspaces add 57f494d8d4 Merge branch 'cassandra-4.1' into cassandra-5.0 No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../cql3/statements/DescribeStatement.java | 3 +- .../statements/schema/CreateTableStatement.java| 1 - src/java/org/apache/cassandra/db/Keyspace.java | 7 +-- .../cassandra/db/compaction/CompactionManager.java | 2 +- .../org/apache/cassandra/dht/BootStrapper.java | 2 +- .../index/sai/virtual/ColumnIndexesSystemView.java | 9 ++- .../sai/virtual/SSTableIndexesSystemView.java | 11 ++-- .../index/sai/virtual/SegmentsSystemView.java | 9 ++- .../org/apache/cassandra/metrics/TableMetrics.java | 2 +- .../repair/consistent/admin/SchemaArgsParser.java | 2 +- src/java/org/apache/cassandra/schema/Schema.java | 65 +++--- .../org/apache/cassandra/schema/SchemaEvent.java | 4 +- .../service/PendingRangeCalculatorService.java | 2 +- .../apache/cassandra/service/StorageService.java | 42 +++--- .../org/apache/cassandra/dht/BootStrapperTest.java | 2 +- .../cassandra/locator/SimpleStrategyTest.java | 4 +- .../cassandra/schema/SchemaKeyspaceTest.java | 2 +- .../org/apache/cassandra/schema/SchemaTest.java| 2 +- .../cassandra/service/LeaveAndBootstrapTest.java | 4 +- .../org/apache/cassandra/service/MoveTest.java | 4 +- 21 files changed, 76 insertions(+), 104 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18747) Test failure: Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.cass
[
https://issues.apache.org/jira/browse/CASSANDRA-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-18747:
--
Fix Version/s: 4.1.4
5.0-alpha2
5.1
(was: 5.x)
(was: 4.1.x)
(was: 5.0.x)
Since Version: 4.1.0
Source Control Link:
https://github.com/apache/cassandra/commit/ac71d0f56efda081cf3c602eae8897b64cf84dac
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Test failure: Fix assertion error AssertionError: Unknown keyspace
> system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
> ---
>
> Key: CASSANDRA-18747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema, Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1.4, 5.0-alpha2, 5.1
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> I've been seeing this assertion error in different tests lately.
> Full error message:
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
> 16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
> node logs (see stdout for full details). Errors: [[node2] 'ERROR
> [PendingRangeCalculator:1] 2023-08-11 16:35:14,445
> JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']{code}
> Example failures:
> test_failed_snitch_update_property_file_snitch -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2475/workflows/2086619e-0f21-464b-a866-84aca516b5e5/jobs/36716/tests]
> test_gcgs_validation -
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1666/testReport/junit/dtest.materialized_views_test/
[jira] [Commented] (CASSANDRA-18942) Repeatable test runs
[ https://issues.apache.org/jira/browse/CASSANDRA-18942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1200#comment-1200 ] Brandon Williams commented on CASSANDRA-18942: -- Dupe of CASSANDRA-17932? > Repeatable test runs > > > Key: CASSANDRA-18942 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18942 > Project: Cassandra > Issue Type: New Feature > Components: Build, CI >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 5.0, 5.0.x > > > It is our policy to loop new introduced tests to avoid introducing flakies. > We also want to add the possibility to repeat a test N number of times to > test robustness, debug flakies, etc. -- 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-18836) Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1207#comment-1207 ] Maxim Muzafarov commented on CASSANDRA-18836: - [~maedhroz] Thank you for your attention to this issue, it's really hard to get any. This is a friendly ping :-) [~claude] Thank you for the review! > Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter > > > Key: CASSANDRA-18836 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18836 > Project: Cassandra > Issue Type: Improvement > Components: Feature/2i Index, Feature/SAI >Reporter: Caleb Rackliffe >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0-alpha2, 5.x > > Time Spent: 0.5h > Remaining Estimate: 0h > > It seems that now we're on Java 11 for 5.0, there isn't much reason not to > use CRC32C as a drop-in replacement for CRC32. SAI isn't even released, so > has no binary compatibility entanglements, and this should be pretty > straightforward. > See https://github.com/apache/bookkeeper/pull/3309 -- 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-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] miklosovic updated CASSANDRA-18891: --- Attachment: signature.asc Dont we have arm machines in our Jenkins pipeline for 4.x already? I guess that running a build there will test it in and out way more than you will ever be able to by running it manually, or? Sent from ProtonMail mobile \ > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 4.0.x > > Attachments: signature.asc > > Time Spent: 10m > Remaining Estimate: 0h > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- 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-18935) Fix nodetool enable/disablebinary to correctly set rpc
[
https://issues.apache.org/jira/browse/CASSANDRA-18935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1220#comment-1220
]
Stefan Miklosovic commented on CASSANDRA-18935:
---
[trunk
j17|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3369/workflows/b1dceb9a-e45d-4b1a-b4db-394f361f2689]
[5.0
j17|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3368/workflows/8309cbb1-cd5b-4945-b590-329617e44c92]
[4.1
j11|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3367/workflows/8d968041-fd54-4cba-87e2-0d939b7376ca]
[4.0
j11|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3366/workflows/e4d5c713-cb48-46e5-979b-fc139a6c0733]
[3.11
j8|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3350/workflows/8416bbd5-a736-49ee-aa50-0a98f5c9eee2]
[3.0
j8|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3365/workflows/689b2ed4-a32b-4ee7-9b1e-f5bfd53d1d9c]
> Fix nodetool enable/disablebinary to correctly set rpc
> --
>
> Key: CASSANDRA-18935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18935
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Attachments: 18935-3.11.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
>
> {code:java}
> if ((nativeFlag != null && Boolean.parseBoolean(nativeFlag)) ||
> (nativeFlag == null && DatabaseDescriptor.startNativeTransport()))
> {
> startNativeTransport();
> StorageService.instance.setRpcReady(true);
> } {code}
> The startup code here only sets RpcReady if native transport is enabled. If
> you call
> {code:java}
> nodetool enablebinary{code}
> then this flag doesn't get set.
> But with the change from CASSANDRA-13043 it requires RpcReady set to true in
> order to get a leader for the counter update.
> Not sure what the correct fix is here, seems to only really use this flag for
> counters. So thinking perhaps the fix is to just move this outside the if
> condition.
>
--
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-18935) Fix nodetool enable/disablebinary to correctly set rpc
[
https://issues.apache.org/jira/browse/CASSANDRA-18935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18935:
--
Status: Needs Committer (was: Patch Available)
> Fix nodetool enable/disablebinary to correctly set rpc
> --
>
> Key: CASSANDRA-18935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18935
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Attachments: 18935-3.11.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
>
> {code:java}
> if ((nativeFlag != null && Boolean.parseBoolean(nativeFlag)) ||
> (nativeFlag == null && DatabaseDescriptor.startNativeTransport()))
> {
> startNativeTransport();
> StorageService.instance.setRpcReady(true);
> } {code}
> The startup code here only sets RpcReady if native transport is enabled. If
> you call
> {code:java}
> nodetool enablebinary{code}
> then this flag doesn't get set.
> But with the change from CASSANDRA-13043 it requires RpcReady set to true in
> order to get a leader for the counter update.
> Not sure what the correct fix is here, seems to only really use this flag for
> counters. So thinking perhaps the fix is to just move this outside the if
> condition.
>
--
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-18747) Test failure: Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.cass
[
https://issues.apache.org/jira/browse/CASSANDRA-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18747:
---
Fix Version/s: 5.0
> Test failure: Fix assertion error AssertionError: Unknown keyspace
> system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
> ---
>
> Key: CASSANDRA-18747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema, Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1.4, 5.0-alpha2, 5.0, 5.1
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> I've been seeing this assertion error in different tests lately.
> Full error message:
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
> 16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
> node logs (see stdout for full details). Errors: [[node2] 'ERROR
> [PendingRangeCalculator:1] 2023-08-11 16:35:14,445
> JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']{code}
> Example failures:
> test_failed_snitch_update_property_file_snitch -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2475/workflows/2086619e-0f21-464b-a866-84aca516b5e5/jobs/36716/tests]
> test_gcgs_validation -
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1666/testReport/junit/dtest.materialized_views_test/TestMaterializedViews/test_gcgs_validation/]
--
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-accord] branch trunk updated: CEP-15: Add Accord configuration stub
This is an automated email from the ASF dual-hosted git repository.
jlewandowski pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-accord.git
The following commit(s) were added to refs/heads/trunk by this push:
new 5ffe3d50 CEP-15: Add Accord configuration stub
5ffe3d50 is described below
commit 5ffe3d504bb5aa1ff1c2b96d817791e40f7ced0f
Author: Jacek Lewandowski
AuthorDate: Mon Oct 9 14:56:57 2023 +0200
CEP-15: Add Accord configuration stub
Patch by Jacek Lewandowski; reviewed by David Capwell for CASSANDRA-18221
---
.../src/main/java/accord/config/LocalConfig.java | 29
.../java/accord/config/MutableLocalConfig.java | 40 ++
.../main/java/accord/impl/SimpleProgressLog.java | 4 ++-
accord-core/src/main/java/accord/local/Node.java | 10 +-
accord-core/src/test/java/accord/Utils.java| 6 +++-
.../src/test/java/accord/impl/basic/Cluster.java | 5 ++-
.../test/java/accord/impl/mock/MockCluster.java| 6 +++-
.../java/accord/local/ImmutableCommandTest.java| 5 ++-
.../src/main/java/accord/maelstrom/Cluster.java| 5 ++-
.../src/main/java/accord/maelstrom/Main.java | 5 ++-
10 files changed, 107 insertions(+), 8 deletions(-)
diff --git a/accord-core/src/main/java/accord/config/LocalConfig.java
b/accord-core/src/main/java/accord/config/LocalConfig.java
new file mode 100644
index ..0ced3b98
--- /dev/null
+++ b/accord-core/src/main/java/accord/config/LocalConfig.java
@@ -0,0 +1,29 @@
+/*
+ * 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 accord.config;
+
+import java.time.Duration;
+
+public interface LocalConfig
+{
+default Duration getProgressLogScheduleDelay()
+{
+return Duration.ofSeconds(1);
+}
+}
diff --git a/accord-core/src/main/java/accord/config/MutableLocalConfig.java
b/accord-core/src/main/java/accord/config/MutableLocalConfig.java
new file mode 100644
index ..f3c42782
--- /dev/null
+++ b/accord-core/src/main/java/accord/config/MutableLocalConfig.java
@@ -0,0 +1,40 @@
+/*
+ * 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 accord.config;
+
+import java.time.Duration;
+
+import com.google.common.annotations.VisibleForTesting;
+
+@VisibleForTesting
+public class MutableLocalConfig implements LocalConfig
+{
+private volatile Duration progressLogScheduleDelay =
LocalConfig.super.getProgressLogScheduleDelay();
+
+public void setProgressLogScheduleDelay(Duration progressLogScheduleDelay)
+{
+this.progressLogScheduleDelay = progressLogScheduleDelay;
+}
+
+@Override
+public Duration getProgressLogScheduleDelay()
+{
+return progressLogScheduleDelay;
+}
+}
diff --git a/accord-core/src/main/java/accord/impl/SimpleProgressLog.java
b/accord-core/src/main/java/accord/impl/SimpleProgressLog.java
index 89291a1e..420d54db 100644
--- a/accord-core/src/main/java/accord/impl/SimpleProgressLog.java
+++ b/accord-core/src/main/java/accord/impl/SimpleProgressLog.java
@@ -18,6 +18,7 @@
package accord.impl;
+import java.time.Duration;
import java.util.List;
import java.util.Map;
import java.util.TreeMap;
@@ -679,7 +680,8 @@ public class SimpleProgressLog implements
ProgressLog.Factory
return;
isScheduled = true;
-node.scheduler().once(() -> commandStore.execute(empty(), ignore
-> run()).begin(commandStore.agent()),
[jira] [Updated] (CASSANDRA-18936) CI jvm-dtest-upgrade breakage
[ https://issues.apache.org/jira/browse/CASSANDRA-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18936: -- Reviewers: Stefan Miklosovic, Stefan Miklosovic Stefan Miklosovic, Stefan Miklosovic (was: Stefan Miklosovic) Status: Review In Progress (was: Patch Available) > CI jvm-dtest-upgrade breakage > - > > Key: CASSANDRA-18936 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18936 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 5.0.x, 5.x > > > git clean failing when reusing the dtest sub clone. > ref: https://the-asf.slack.com/archives/CK23JSY2K/p1697465832946299 -- 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-18936) CI jvm-dtest-upgrade breakage
[
https://issues.apache.org/jira/browse/CASSANDRA-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1227#comment-1227
]
Stefan Miklosovic commented on CASSANDRA-18936:
---
I run it locally by
{code:java}
.build/run-tests.sh jvm-dtest-upgrade 1/64 {code}
and it just all passed fine.
+1 and I am going to ship it to 5.0 and trunk.
> CI jvm-dtest-upgrade breakage
> -
>
> Key: CASSANDRA-18936
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18936
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> git clean failing when reusing the dtest sub clone.
> ref: https://the-asf.slack.com/archives/CK23JSY2K/p1697465832946299
--
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-18944) Test failure: org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18944:
--
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990)
Discovered By: Unit Test
> Test failure:
> org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest
> -
>
> Key: CASSANDRA-18944
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18944
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The simulator test
> {{org.apache.cassandra.simulator.test.ShortPaxosSimulationTest#simulationTest}}
> is flaky on 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/332/workflows/946e28f4-2dec-4384-ac38-de011093f6c6/jobs/25735/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3253/workflows/e48b49e9-cf36-412a-a811-d813031e6f01/jobs/83735/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3254/workflows/69f451ef-fb39-48e4-b1d1-40ee4141b0c1/jobs/83739/tests
> {code}
> org.apache.cassandra.simulator.SimulationException: Failed on seed
> 0xb01206bb3b021127
> Caused by: java.lang.ClassCastException: class
> org.apache.cassandra.net.NoPayload cannot be cast to class
> org.apache.cassandra.gms.GossipShutdown (org.apache.cassandra.net.NoPayload
> and org.apache.cassandra.gms.GossipShutdown are in unnamed module of loader
> org.apache.cassandra.distributed.shared.InstanceClassLoader @68801feb)
> at
> org.apache.cassandra.gms.GossipShutdown$Serializer.serialize(GossipShutdown.java:41)
> at
> org.apache.cassandra.net.Message$Serializer.serialize(Message.java:722)
> at
> org.apache.cassandra.distributed.impl.Instance.serializeMessage(Instance.java:427)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$registerOutboundFilter$5(Instance.java:370)
> at
> org.apache.cassandra.net.OutboundSink$Filtered.accept(OutboundSink.java:54)
> at org.apache.cassandra.net.OutboundSink.accept(OutboundSink.java:70)
> at
> org.apache.cassandra.net.MessagingService.send(MessagingService.java:449)
> at
> org.apache.cassandra.net.MessagingService.send(MessagingService.java:419)
> at
> org.apache.cassandra.gms.Gossiper.unsafeSendShutdown(Gossiper.java:2634)
> at
> org.apache.cassandra.simulator.cluster.OnInstanceSendShutdown.lambda$invokableSendShutdown$1(OnInstanceSendShutdown.java:48)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> at
> org.apache.cassandra.concurrent.SyncFutureTask$1.call(SyncFutureTask.java:46)
> at
> org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
> at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$AbstractSingleThreadedExecutorPlus.lambda$new$0(InterceptingExecutor.java:584)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> The test failure can easily be reproduced on CircleCI with:
> {code}
> .circleci/generate.sh -sp \
> -e
> REPEATED_SIMULATOR_DTESTS=org.apache.cassandra.simulator.test.ShortPaxosSimulationTest
> \
> -e REPEATED_SIMULATOR_DTESTS_COUNT=100
> {code}
> Flakiness seems ~18%.
> The test failure is not reported on Butler because simulator tests are not
> run by Jenkins.
--
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-18936) CI jvm-dtest-upgrade breakage
[
https://issues.apache.org/jira/browse/CASSANDRA-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1227#comment-1227
]
Stefan Miklosovic edited comment on CASSANDRA-18936 at 10/19/23 12:11 PM:
--
I run it locally by
{code:java}
.build/run-tests.sh jvm-dtest-upgrade 1/64 {code}
and it just all passed fine.
I have also rerun the very same command (same command, run twice).
+1 and I am going to ship it to 5.0 and trunk.
was (Author: smiklosovic):
I run it locally by
{code:java}
.build/run-tests.sh jvm-dtest-upgrade 1/64 {code}
and it just all passed fine.
+1 and I am going to ship it to 5.0 and trunk.
> CI jvm-dtest-upgrade breakage
> -
>
> Key: CASSANDRA-18936
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18936
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> git clean failing when reusing the dtest sub clone.
> ref: https://the-asf.slack.com/archives/CK23JSY2K/p1697465832946299
--
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] branch cep-15-accord updated: CEP-15: Add Accord configuration stub
This is an automated email from the ASF dual-hosted git repository. jlewandowski pushed a commit to branch cep-15-accord in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cep-15-accord by this push: new a7cd114435 CEP-15: Add Accord configuration stub a7cd114435 is described below commit a7cd114435704b988c81f47ef53d0bfd6441f38b Author: Jacek Lewandowski AuthorDate: Mon Oct 9 15:05:57 2023 +0200 CEP-15: Add Accord configuration stub Patch by Jacek Lewandowski; reviewed by David Capwell for CASSANDRA-18221 --- CHANGES.txt| 1 + conf/cassandra.yaml| 16 +++-- modules/accord | 2 +- .../org/apache/cassandra/config/AccordSpec.java| 30 src/java/org/apache/cassandra/config/Config.java | 8 ++--- .../cassandra/config/DatabaseDescriptor.java | 42 +++--- .../org/apache/cassandra/config/DurationSpec.java | 6 .../cql3/statements/TransactionStatement.java | 2 +- .../service/accord/AccordConfiguration.java| 40 + .../cassandra/service/accord/AccordService.java| 12 --- test/conf/cassandra-mtls.yaml | 3 +- test/conf/cassandra-murmur.yaml| 3 +- test/conf/cassandra-old.yaml | 3 +- test/conf/cassandra-pem-jks-sslcontextfactory.yaml | 3 +- ...pem-sslcontextfactory-invalidconfiguration.yaml | 3 +- test/conf/cassandra-pem-sslcontextfactory.yaml | 3 +- test/conf/cassandra-seeds.yaml | 3 +- ...dra-sslcontextfactory-invalidconfiguration.yaml | 3 +- test/conf/cassandra-sslcontextfactory.yaml | 3 +- test/conf/cassandra.yaml | 8 +++-- .../cassandra/distributed/impl/InstanceConfig.java | 16 ++--- .../test/accord/AccordBootstrapTest.java | 2 +- .../test/accord/AccordFeatureFlagTest.java | 11 +++--- .../config/DatabaseDescriptorRefTest.java | 25 ++--- .../config/YamlConfigurationLoaderTest.java| 6 ++-- 25 files changed, 181 insertions(+), 73 deletions(-) diff --git a/CHANGES.txt b/CHANGES.txt index 69eb1f833b..dc7de36c99 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ accord + * Add Accord configuration stub (CASSANDRA-18221) * Improve transaction statement validation (CASSANDRA-18302) * Add support for prepared statements for accord transactions (CASSANDRA-18299) * Fix statement validation against partition range queries (CASSANDRA-18240) diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 2bd927ecf4..e24672d04c 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -1818,9 +1818,6 @@ drop_compact_storage_enabled: false # Whether or not USE is allowed. This is enabled by default to avoid failure on upgrade. #use_statements_enabled: true -# Enables the execution of Accord (multi-key) transactions on this node. -accord_transactions_enabled: false - # When the client triggers a protocol exception or unknown issue (Cassandra bug) we increment # a client metric showing this; this logic will exclude specific subnets from updating these # metrics @@ -2113,3 +2110,16 @@ accord_transactions_enabled: false # a stable cluster. If a node from a previous version was started by accident we won't any longer toggle behaviors as when UPGRADING. # storage_compatibility_mode: NONE + +#accord: +# # Enables the execution of Accord (multi-key) transactions on this node. +# enabled: false +# +# # Journal directory for Accord +# journal_directory: +# +# # The number of Accord shards on this node; -1 means use the number of cores +# shard_count: -1 +# +# # Progress log scheduling delay +# progress_log_schedule_delay: 1s diff --git a/modules/accord b/modules/accord index 0419858bd1..5ffe3d504b 16 --- a/modules/accord +++ b/modules/accord @@ -1 +1 @@ -Subproject commit 0419858bd1f6761f08fd1369477f7c142f5bbb4f +Subproject commit 5ffe3d504bb5aa1ff1c2b96d817791e40f7ced0f diff --git a/src/java/org/apache/cassandra/config/AccordSpec.java b/src/java/org/apache/cassandra/config/AccordSpec.java new file mode 100644 index 00..b025d561b6 --- /dev/null +++ b/src/java/org/apache/cassandra/config/AccordSpec.java @@ -0,0 +1,30 @@ +/* + * 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
[jira] [Commented] (CASSANDRA-18942) Repeatable test runs
[ https://issues.apache.org/jira/browse/CASSANDRA-18942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1225#comment-1225 ] Berenguer Blasi commented on CASSANDRA-18942: - Possibly! > Repeatable test runs > > > Key: CASSANDRA-18942 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18942 > Project: Cassandra > Issue Type: New Feature > Components: Build, CI >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 5.0, 5.0.x > > > It is our policy to loop new introduced tests to avoid introducing flakies. > We also want to add the possibility to repeat a test N number of times to > test robustness, debug flakies, etc. -- 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-18944) Test failure: org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18944:
--
Fix Version/s: 5.0.x
5.x
> Test failure:
> org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest
> -
>
> Key: CASSANDRA-18944
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18944
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The simulator test
> {{org.apache.cassandra.simulator.test.ShortPaxosSimulationTest#simulationTest}}
> is flaky on 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/332/workflows/946e28f4-2dec-4384-ac38-de011093f6c6/jobs/25735/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3253/workflows/e48b49e9-cf36-412a-a811-d813031e6f01/jobs/83735/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3254/workflows/69f451ef-fb39-48e4-b1d1-40ee4141b0c1/jobs/83739/tests
> {code}
> org.apache.cassandra.simulator.SimulationException: Failed on seed
> 0xb01206bb3b021127
> Caused by: java.lang.ClassCastException: class
> org.apache.cassandra.net.NoPayload cannot be cast to class
> org.apache.cassandra.gms.GossipShutdown (org.apache.cassandra.net.NoPayload
> and org.apache.cassandra.gms.GossipShutdown are in unnamed module of loader
> org.apache.cassandra.distributed.shared.InstanceClassLoader @68801feb)
> at
> org.apache.cassandra.gms.GossipShutdown$Serializer.serialize(GossipShutdown.java:41)
> at
> org.apache.cassandra.net.Message$Serializer.serialize(Message.java:722)
> at
> org.apache.cassandra.distributed.impl.Instance.serializeMessage(Instance.java:427)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$registerOutboundFilter$5(Instance.java:370)
> at
> org.apache.cassandra.net.OutboundSink$Filtered.accept(OutboundSink.java:54)
> at org.apache.cassandra.net.OutboundSink.accept(OutboundSink.java:70)
> at
> org.apache.cassandra.net.MessagingService.send(MessagingService.java:449)
> at
> org.apache.cassandra.net.MessagingService.send(MessagingService.java:419)
> at
> org.apache.cassandra.gms.Gossiper.unsafeSendShutdown(Gossiper.java:2634)
> at
> org.apache.cassandra.simulator.cluster.OnInstanceSendShutdown.lambda$invokableSendShutdown$1(OnInstanceSendShutdown.java:48)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> at
> org.apache.cassandra.concurrent.SyncFutureTask$1.call(SyncFutureTask.java:46)
> at
> org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
> at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$AbstractSingleThreadedExecutorPlus.lambda$new$0(InterceptingExecutor.java:584)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> The test failure can easily be reproduced on CircleCI with:
> {code}
> .circleci/generate.sh -sp \
> -e
> REPEATED_SIMULATOR_DTESTS=org.apache.cassandra.simulator.test.ShortPaxosSimulationTest
> \
> -e REPEATED_SIMULATOR_DTESTS_COUNT=100
> {code}
> Flakiness seems ~18%.
> The test failure is not reported on Butler because simulator tests are not
> run by Jenkins.
--
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] [Created] (CASSANDRA-18944) Test failure: org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest
Andres de la Peña created CASSANDRA-18944:
-
Summary: Test failure:
org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest
Key: CASSANDRA-18944
URL: https://issues.apache.org/jira/browse/CASSANDRA-18944
Project: Cassandra
Issue Type: Bug
Components: Test/unit
Reporter: Andres de la Peña
The simulator test
{{org.apache.cassandra.simulator.test.ShortPaxosSimulationTest#simulationTest}}
is flaky on 5.0 and trunk:
*
https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/332/workflows/946e28f4-2dec-4384-ac38-de011093f6c6/jobs/25735/tests
*
https://app.circleci.com/pipelines/github/adelapena/cassandra/3253/workflows/e48b49e9-cf36-412a-a811-d813031e6f01/jobs/83735/tests
*
https://app.circleci.com/pipelines/github/adelapena/cassandra/3254/workflows/69f451ef-fb39-48e4-b1d1-40ee4141b0c1/jobs/83739/tests
{code}
org.apache.cassandra.simulator.SimulationException: Failed on seed
0xb01206bb3b021127
Caused by: java.lang.ClassCastException: class
org.apache.cassandra.net.NoPayload cannot be cast to class
org.apache.cassandra.gms.GossipShutdown (org.apache.cassandra.net.NoPayload and
org.apache.cassandra.gms.GossipShutdown are in unnamed module of loader
org.apache.cassandra.distributed.shared.InstanceClassLoader @68801feb)
at
org.apache.cassandra.gms.GossipShutdown$Serializer.serialize(GossipShutdown.java:41)
at
org.apache.cassandra.net.Message$Serializer.serialize(Message.java:722)
at
org.apache.cassandra.distributed.impl.Instance.serializeMessage(Instance.java:427)
at
org.apache.cassandra.distributed.impl.Instance.lambda$registerOutboundFilter$5(Instance.java:370)
at
org.apache.cassandra.net.OutboundSink$Filtered.accept(OutboundSink.java:54)
at org.apache.cassandra.net.OutboundSink.accept(OutboundSink.java:70)
at
org.apache.cassandra.net.MessagingService.send(MessagingService.java:449)
at
org.apache.cassandra.net.MessagingService.send(MessagingService.java:419)
at
org.apache.cassandra.gms.Gossiper.unsafeSendShutdown(Gossiper.java:2634)
at
org.apache.cassandra.simulator.cluster.OnInstanceSendShutdown.lambda$invokableSendShutdown$1(OnInstanceSendShutdown.java:48)
at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
at
org.apache.cassandra.concurrent.SyncFutureTask$1.call(SyncFutureTask.java:46)
at
org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
at
org.apache.cassandra.simulator.systems.InterceptingExecutor$AbstractSingleThreadedExecutorPlus.lambda$new$0(InterceptingExecutor.java:584)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:829)
{code}
The test failure can easily be reproduced on CircleCI with:
{code}
.circleci/generate.sh -sp \
-e
REPEATED_SIMULATOR_DTESTS=org.apache.cassandra.simulator.test.ShortPaxosSimulationTest
\
-e REPEATED_SIMULATOR_DTESTS_COUNT=100
{code}
Flakiness seems ~18%.
The test failure is not reported on Butler because simulator tests are not run
by Jenkins.
--
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-18936) CI jvm-dtest-upgrade breakage
[ https://issues.apache.org/jira/browse/CASSANDRA-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18936: -- Status: Ready to Commit (was: Review In Progress) > CI jvm-dtest-upgrade breakage > - > > Key: CASSANDRA-18936 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18936 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 5.0.x, 5.x > > > git clean failing when reusing the dtest sub clone. > ref: https://the-asf.slack.com/archives/CK23JSY2K/p1697465832946299 -- 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-18221) CEP-15: (Accord) Define a configuration system for Accord to allow overriding of internal configs and integrate with Cassandra yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Lewandowski updated CASSANDRA-18221: -- Source Control Link: https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b Resolution: Fixed Status: Resolved (was: Ready to Commit) > CEP-15: (Accord) Define a configuration system for Accord to allow overriding > of internal configs and integrate with Cassandra yaml > --- > > Key: CASSANDRA-18221 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18221 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: David Capwell >Assignee: Jacek Lewandowski >Priority: Normal > Labels: pull-request-available > Fix For: 5.x > > Time Spent: 1h > Remaining Estimate: 0h > > Users are used to modifying cassandra via yaml and JMX (for dynamic configs) > but accord does not integrate with this right now; we should enhance Accord > to expose configs that are defined in cassandra yaml. > As an extension on this, we should figure out which configs are “dynamic” and > allow overriding via JMX or system vtable. -- 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
[
https://issues.apache.org/jira/browse/CASSANDRA-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1236#comment-1236
]
Andres de la Peña commented on CASSANDRA-18902:
---
Seen also in trunk:
*
https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/332/workflows/946e28f4-2dec-4384-ac38-de011093f6c6/jobs/25738/tests
*
https://app.circleci.com/pipelines/github/adelapena/cassandra/3254/workflows/69f451ef-fb39-48e4-b1d1-40ee4141b0c1/jobs/83737/tests
*
https://app.circleci.com/pipelines/github/adelapena/cassandra/3254/workflows/69f451ef-fb39-48e4-b1d1-40ee4141b0c1/jobs/83738/tests
{code}
java.lang.IllegalStateException: Could not achieve schema readiness in PT30S
at
org.apache.cassandra.service.StorageService.waitForSchema(StorageService.java:1194)
at
org.apache.cassandra.service.StorageService.prepareForBootstrap(StorageService.java:1967)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1238)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1199)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:978)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:895)
at
org.apache.cassandra.distributed.impl.Instance.lambda$startup$12(Instance.java:701)
at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
Suppressed: org.apache.cassandra.distributed.shared.ShutdownException:
Uncaught exceptions were thrown during test
at
org.apache.cassandra.distributed.impl.AbstractCluster.checkAndResetUncaughtExceptions(AbstractCluster.java:1117)
at
org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1103)
at
org.apache.cassandra.distributed.test.MigrationCoordinatorTest.explicitEndpointIgnore(MigrationCoordinatorTest.java:78)
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)
Suppressed: java.lang.AssertionError: Release version is unknown
at
org.apache.cassandra.utils.FBUtilities.getReleaseVersionMajor(FBUtilities.java:473)
at
org.apache.cassandra.schema.MigrationCoordinator.shouldPullFromEndpoint(MigrationCoordinator.java:371)
at
org.apache.cassandra.schema.MigrationCoordinator.maybePullSchema(MigrationCoordinator.java:303)
at
org.apache.cassandra.schema.MigrationCoordinator.pullComplete(MigrationCoordinator.java:686)
at
org.apache.cassandra.schema.MigrationCoordinator$Callback.fail(MigrationCoordinator.java:615)
at
org.apache.cassandra.schema.MigrationCoordinator$Callback.onFailure(MigrationCoordinator.java:610)
at
org.apache.cassandra.schema.MigrationCoordinator.pullSchema(MigrationCoordinator.java:654)
at
org.apache.cassandra.schema.MigrationCoordinator.lambda$scheduleSchemaPull$2(MigrationCoordinator.java:548)
at
org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
at
org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
at
org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
at
org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
at
org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
at
org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
{code}
I haven't se
[jira] [Updated] (CASSANDRA-18902) Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest
[ https://issues.apache.org/jira/browse/CASSANDRA-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-18902: -- Fix Version/s: 5.0.x 5.x > Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest > > > Key: CASSANDRA-18902 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18902 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Jacek Lewandowski >Priority: Normal > Fix For: 5.0.x, 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] [Updated] (CASSANDRA-18902) Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest
[ https://issues.apache.org/jira/browse/CASSANDRA-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-18902: -- Bug Category: Parent values: Correctness(12982)Level 1 values: Test Failure(12990) > Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest > > > Key: CASSANDRA-18902 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18902 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Jacek Lewandowski >Priority: Normal > > 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] [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 ] Andres de la Peña updated CASSANDRA-18902: -- Summary: Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest.explicitEndpointIgnore (was: Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest) > 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 >Priority: Normal > Fix For: 5.0.x, 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] branch cassandra-5.0 updated (57f494d8d4 -> 0aff36fc74)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 57f494d8d4 Merge branch 'cassandra-4.1' into cassandra-5.0 add 0aff36fc74 When generating dtest jars and switching between branches, do git clean before git reset No new revisions were added by this update. Summary of changes: .build/run-tests.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository.
smiklosovic pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 088f3ea3e9df188129032b076718c55cdcd9690a
Merge: c2c20ab843 0aff36fc74
Author: Stefan Miklosovic
AuthorDate: Thu Oct 19 15:26:53 2023 +0200
Merge branch 'cassandra-5.0' into trunk
.build/run-tests.sh | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --cc .build/run-tests.sh
index 35b166f863,6736a159b5..821d6ac448
--- a/.build/run-tests.sh
+++ b/.build/run-tests.sh
@@@ -105,8 -103,8 +104,8 @@@ _build_all_dtest_jars()
[ "${java_version}" -eq 11 ] && export CASSANDRA_USE_JDK11=true
pushd ${TMP_DIR}/cassandra-dtest-jars >/dev/null
-for branch in cassandra-4.0 cassandra-4.1 cassandra-5.0 ; do
+for branch in cassandra-4.0 cassandra-4.1 cassandra-5.0 trunk ; do
- git reset --hard HEAD && git clean -qxdff || echo "failed to
reset/clean ${TMP_DIR}/cassandra-dtest-jars… continuing…"
+ git clean -qxdff && git reset --hard HEAD || echo "failed to
reset/clean ${TMP_DIR}/cassandra-dtest-jars… continuing…"
git checkout --quiet $branch
dtest_jar_version=$(grep 'property\s*name=\"base.version\"' build.xml
|sed -ne 's/.*value=\"\([^"]*\)\".*/\1/p')
if [ -f "${DIST_DIR}/dtest-${dtest_jar_version}.jar" ] ; then
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (c2c20ab843 -> 088f3ea3e9)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from c2c20ab843 Merge branch 'cassandra-5.0' into trunk add 0aff36fc74 When generating dtest jars and switching between branches, do git clean before git reset new 088f3ea3e9 Merge branch 'cassandra-5.0' into trunk 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: .build/run-tests.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18936) CI jvm-dtest-upgrade breakage
[ https://issues.apache.org/jira/browse/CASSANDRA-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18936: -- Fix Version/s: 5.0-alpha2 5.1 (was: 5.x) (was: 5.0.x) Since Version: 5.0-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/0aff36fc745e28ecdc0905ecaa9cf5ab8344206b Resolution: Fixed Status: Resolved (was: Ready to Commit) > CI jvm-dtest-upgrade breakage > - > > Key: CASSANDRA-18936 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18936 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 5.0-alpha2, 5.1 > > > git clean failing when reusing the dtest sub clone. > ref: https://the-asf.slack.com/archives/CK23JSY2K/p1697465832946299 -- 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-18933) Correct comment for nc SSTable format
[
https://issues.apache.org/jira/browse/CASSANDRA-18933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1293#comment-1293
]
Brandon Williams commented on CASSANDRA-18933:
--
For a comment? I think this could have been ninja'd, personally.
> Correct comment for nc SSTable format
> -
>
> Key: CASSANDRA-18933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18933
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In [CASSANDRA-18134 |https://issues.apache.org/jira/browse/CASSANDRA-18134],
> the {{nc}} SSTable format was introduced. The patch was merged into {{5.0+}},
> however the comment in source incorrectly mentions that the format was added
> to version {{4.1}}.
--
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-18933) Correct comment for nc SSTable format
[
https://issues.apache.org/jira/browse/CASSANDRA-18933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1297#comment-1297
]
Berenguer Blasi commented on CASSANDRA-18933:
-
Doh! you're right. I was looking at BigFormat and wires crossed in my brain
thinking I was looking at code. Ignore me lol. +1
> Correct comment for nc SSTable format
> -
>
> Key: CASSANDRA-18933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18933
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In [CASSANDRA-18134 |https://issues.apache.org/jira/browse/CASSANDRA-18134],
> the {{nc}} SSTable format was introduced. The patch was merged into {{5.0+}},
> however the comment in source incorrectly mentions that the format was added
> to version {{4.1}}.
--
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-18935) Fix nodetool enable/disablebinary to correctly set rpc
[
https://issues.apache.org/jira/browse/CASSANDRA-18935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1308#comment-1308
]
Brandon Williams commented on CASSANDRA-18935:
--
Missing some JDK runs?
> Fix nodetool enable/disablebinary to correctly set rpc
> --
>
> Key: CASSANDRA-18935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18935
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Attachments: 18935-3.11.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
>
> {code:java}
> if ((nativeFlag != null && Boolean.parseBoolean(nativeFlag)) ||
> (nativeFlag == null && DatabaseDescriptor.startNativeTransport()))
> {
> startNativeTransport();
> StorageService.instance.setRpcReady(true);
> } {code}
> The startup code here only sets RpcReady if native transport is enabled. If
> you call
> {code:java}
> nodetool enablebinary{code}
> then this flag doesn't get set.
> But with the change from CASSANDRA-13043 it requires RpcReady set to true in
> order to get a leader for the counter update.
> Not sure what the correct fix is here, seems to only really use this flag for
> counters. So thinking perhaps the fix is to just move this outside the if
> condition.
>
--
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] (CASSANDRA-18935) Fix nodetool enable/disablebinary to correctly set rpc
[ https://issues.apache.org/jira/browse/CASSANDRA-18935 ]
Stefan Miklosovic deleted comment on CASSANDRA-18935:
---
was (Author: smiklosovic):
[~brandon.williams] would you please took a look and approved?
> Fix nodetool enable/disablebinary to correctly set rpc
> --
>
> Key: CASSANDRA-18935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18935
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Attachments: 18935-3.11.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
>
> {code:java}
> if ((nativeFlag != null && Boolean.parseBoolean(nativeFlag)) ||
> (nativeFlag == null && DatabaseDescriptor.startNativeTransport()))
> {
> startNativeTransport();
> StorageService.instance.setRpcReady(true);
> } {code}
> The startup code here only sets RpcReady if native transport is enabled. If
> you call
> {code:java}
> nodetool enablebinary{code}
> then this flag doesn't get set.
> But with the change from CASSANDRA-13043 it requires RpcReady set to true in
> order to get a leader for the counter update.
> Not sure what the correct fix is here, seems to only really use this flag for
> counters. So thinking perhaps the fix is to just move this outside the if
> condition.
>
--
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-18935) Fix nodetool enable/disablebinary to correctly set rpc
[
https://issues.apache.org/jira/browse/CASSANDRA-18935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1315#comment-1315
]
Stefan Miklosovic commented on CASSANDRA-18935:
---
[~brandon.williams] would you please took a look and approved?
> Fix nodetool enable/disablebinary to correctly set rpc
> --
>
> Key: CASSANDRA-18935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18935
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Attachments: 18935-3.11.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
>
> {code:java}
> if ((nativeFlag != null && Boolean.parseBoolean(nativeFlag)) ||
> (nativeFlag == null && DatabaseDescriptor.startNativeTransport()))
> {
> startNativeTransport();
> StorageService.instance.setRpcReady(true);
> } {code}
> The startup code here only sets RpcReady if native transport is enabled. If
> you call
> {code:java}
> nodetool enablebinary{code}
> then this flag doesn't get set.
> But with the change from CASSANDRA-13043 it requires RpcReady set to true in
> order to get a leader for the counter update.
> Not sure what the correct fix is here, seems to only really use this flag for
> counters. So thinking perhaps the fix is to just move this outside the if
> condition.
>
--
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-18935) Fix nodetool enable/disablebinary to correctly set rpc
[
https://issues.apache.org/jira/browse/CASSANDRA-18935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1316#comment-1316
]
Stefan Miklosovic commented on CASSANDRA-18935:
---
since it is the very same patch just applied to various branches, I would say
that we tested it all from Java 8 to 17 :)
> Fix nodetool enable/disablebinary to correctly set rpc
> --
>
> Key: CASSANDRA-18935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18935
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Attachments: 18935-3.11.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
>
> {code:java}
> if ((nativeFlag != null && Boolean.parseBoolean(nativeFlag)) ||
> (nativeFlag == null && DatabaseDescriptor.startNativeTransport()))
> {
> startNativeTransport();
> StorageService.instance.setRpcReady(true);
> } {code}
> The startup code here only sets RpcReady if native transport is enabled. If
> you call
> {code:java}
> nodetool enablebinary{code}
> then this flag doesn't get set.
> But with the change from CASSANDRA-13043 it requires RpcReady set to true in
> order to get a leader for the counter update.
> Not sure what the correct fix is here, seems to only really use this flag for
> counters. So thinking perhaps the fix is to just move this outside the if
> condition.
>
--
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-18943) http/2 vulnerability: CVE-2023-44487
[
https://issues.apache.org/jira/browse/CASSANDRA-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1318#comment-1318
]
Brandon Williams commented on CASSANDRA-18943:
--
This affects netty and the driver, with variance between branches. Here's what
dependency-check looks like:
{quote}
3.0: fail
Dependency-Check Failure:
One or more dependencies were identified with vulnerabilities that have a CVSS
score greater than or equal to '1.0':
netty-all-4.0.44.Final.jar: CVE-2023-44487
See the dependency-check report for more details.
Total time: 3 minutes 45 seconds
3.11: fail
Dependency-Check Failure:
One or more dependencies were identified with vulnerabilities that have a CVSS
score greater than or equal to '1.0':
netty-all-4.0.44.Final.jar: CVE-2023-44487
See the dependency-check report for more details.
Total time: 3 minutes 57 seconds
4.0: fail
Dependency-Check Failure:
One or more dependencies were identified with vulnerabilities that have a CVSS
score greater than or equal to '1.0':
netty-all-4.1.58.Final.jar: CVE-2023-4586, CVE-2023-44487
See the dependency-check report for more details.
Total time: 3 minutes 55 seconds
4.1: fail
Dependency-Check Failure:
One or more dependencies were identified with vulnerabilities that have a CVSS
score greater than or equal to '1.0':
netty-all-4.1.58.Final.jar: CVE-2023-4586, CVE-2023-44487
See the dependency-check report for more details.
Total time: 4 minutes 22 seconds
5.0: fail
cassandra-driver-core-3.11.5-shaded.jar/META-INF/maven/io.netty/netty-transport-classes-epoll/pom.xml:
CVE-2023-4586, CVE-2023-44487
cassandra-driver-core-3.11.5-shaded.jar/META-INF/maven/io.netty/netty-transport-native-unix-common/pom.xml:
CVE-2023-4586, CVE-2023-44487
netty-transport-4.1.96.Final.jar: CVE-2023-4586, CVE-2023-44487
See the dependency-check report for more details.
Total time: 3 minutes 39 seconds
trunk: fail
cassandra-driver-core-3.11.5-shaded.jar/META-INF/maven/io.netty/netty-transport-classes-epoll/pom.xml:
CVE-2023-4586, CVE-2023-44487
cassandra-driver-core-3.11.5-shaded.jar/META-INF/maven/io.netty/netty-transport-native-unix-common/pom.xml:
CVE-2023-4586, CVE-2023-44487
netty-transport-4.1.96.Final.jar: CVE-2023-4586, CVE-2023-44487
{quote}
> http/2 vulnerability: CVE-2023-44487
>
>
> Key: CASSANDRA-18943
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18943
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> https://nvd.nist.gov/vuln/detail/CVE-2023-44487
> Basically anything using http/2 is covered by this, but we don't use it.
--
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-18360) Test Failure: o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
[
https://issues.apache.org/jira/browse/CASSANDRA-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1328#comment-1328
]
Brandon Williams commented on CASSANDRA-18360:
--
Saw an instance of the cdc variant in the wild:
https://app.circleci.com/pipelines/github/instaclustr/cassandra/3368/workflows/8309cbb1-cd5b-4945-b590-329617e44c92/jobs/138919/tests
> Test Failure:
> o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
> ---
>
> Key: CASSANDRA-18360
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18360
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test
> {{org.apache.cassandra.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName}}
> is flaky at least on trunk. Flakiness seems lesser than 1%.
> While I haven't seen it on Jenkins yet, it can easily be reproduced on
> CircleCI with the multiplexer:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32235
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32234
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/739a95d3-8e42-4447-93dd-122fc16fdd7d/jobs/32233/tests
> Those runs show two types of errors:
> {code}
> junit.framework.AssertionFailedError: Invalid value for row 0 column 1
> (content of type text), expected but got
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1506)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> {code}
> and:
> {code}
> org.apache.cassandra.serializers.MarshalException: Invalid UTF-8 bytes
> 00e0279515437f00
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:46)
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:29)
> at
> org.apache.cassandra.serializers.TypeSerializer.deserialize(TypeSerializer.java:37)
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1494)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> 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}
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_UTESTS_COUNT=500 \
> -e REPEATED_UTESTS=org.apache.cassandra.cql3.validation.operations.AlterTest
> {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-18935) Fix nodetool enable/disablebinary to correctly set rpc
[
https://issues.apache.org/jira/browse/CASSANDRA-18935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1329#comment-1329
]
Brandon Williams commented on CASSANDRA-18935:
--
Fair enough, it's a simple patch. The failure in 5.0 is CASSANDRA-18360 and it
didn't repro on trunk so nothing to be concerned about there. +1
> Fix nodetool enable/disablebinary to correctly set rpc
> --
>
> Key: CASSANDRA-18935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18935
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Attachments: 18935-3.11.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
>
> {code:java}
> if ((nativeFlag != null && Boolean.parseBoolean(nativeFlag)) ||
> (nativeFlag == null && DatabaseDescriptor.startNativeTransport()))
> {
> startNativeTransport();
> StorageService.instance.setRpcReady(true);
> } {code}
> The startup code here only sets RpcReady if native transport is enabled. If
> you call
> {code:java}
> nodetool enablebinary{code}
> then this flag doesn't get set.
> But with the change from CASSANDRA-13043 it requires RpcReady set to true in
> order to get a leader for the counter update.
> Not sure what the correct fix is here, seems to only really use this flag for
> counters. So thinking perhaps the fix is to just move this outside the if
> condition.
>
--
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-18872) Remove deprecated crc_check_chance in compression params
[ https://issues.apache.org/jira/browse/CASSANDRA-18872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1333#comment-1333 ] Branimir Lambov commented on CASSANDRA-18872: - The patch looks good to me, the changes are not too invasive and can be easily replaced with format configuration in CASSANDRA-18534. Do we have a documentation ticket corresponding to this? AFAICS [the docs|https://cassandra.apache.org/doc/latest/cassandra/operating/compression.html] only mention the compression-level setting, even for 4.1. This documentation change also needs to explain that the chance only applies to compressed sstables. > Remove deprecated crc_check_chance in compression params > > > Key: CASSANDRA-18872 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18872 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression, Legacy/CQL >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > crc_check_chance was moved from compression parameters and it is a standalone > table parameter. This was done in times of 3.0 so it is now time to get rid > of that in 5.0. -- 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-18933) Correct comment for nc SSTable format
[
https://issues.apache.org/jira/browse/CASSANDRA-18933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1381#comment-1381
]
Francisco Guerrero commented on CASSANDRA-18933:
Yeah, I didn't feel like using resources for that change. I think it's good to
be merged now.
> Correct comment for nc SSTable format
> -
>
> Key: CASSANDRA-18933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18933
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In [CASSANDRA-18134 |https://issues.apache.org/jira/browse/CASSANDRA-18134],
> the {{nc}} SSTable format was introduced. The patch was merged into {{5.0+}},
> however the comment in source incorrectly mentions that the format was added
> to version {{4.1}}.
--
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-18836) Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-18836: Status: Review In Progress (was: Patch Available) > Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter > > > Key: CASSANDRA-18836 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18836 > Project: Cassandra > Issue Type: Improvement > Components: Feature/2i Index, Feature/SAI >Reporter: Caleb Rackliffe >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0-alpha2, 5.x > > Time Spent: 0.5h > Remaining Estimate: 0h > > It seems that now we're on Java 11 for 5.0, there isn't much reason not to > use CRC32C as a drop-in replacement for CRC32. SAI isn't even released, so > has no binary compatibility entanglements, and this should be pretty > straightforward. > See https://github.com/apache/bookkeeper/pull/3309 -- 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-18933) Correct comment for nc SSTable format
[
https://issues.apache.org/jira/browse/CASSANDRA-18933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18933:
-
Reviewers: Berenguer Blasi, Brandon Williams
Status: Review In Progress (was: Patch Available)
> Correct comment for nc SSTable format
> -
>
> Key: CASSANDRA-18933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18933
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In [CASSANDRA-18134 |https://issues.apache.org/jira/browse/CASSANDRA-18134],
> the {{nc}} SSTable format was introduced. The patch was merged into {{5.0+}},
> however the comment in source incorrectly mentions that the format was added
> to version {{4.1}}.
--
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-18933) Correct comment for nc SSTable format
[
https://issues.apache.org/jira/browse/CASSANDRA-18933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18933:
-
Status: Ready to Commit (was: Review In Progress)
> Correct comment for nc SSTable format
> -
>
> Key: CASSANDRA-18933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18933
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In [CASSANDRA-18134 |https://issues.apache.org/jira/browse/CASSANDRA-18134],
> the {{nc}} SSTable format was introduced. The patch was merged into {{5.0+}},
> however the comment in source incorrectly mentions that the format was added
> to version {{4.1}}.
--
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] branch cassandra-5.0 updated: Correct comment for nc SSTable format
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-5.0 by this push: new 8c89e2adb7 Correct comment for nc SSTable format 8c89e2adb7 is described below commit 8c89e2adb7680ecb4dd3cb2a562206fb8cb50d4a Author: Francisco Guerrero AuthorDate: Tue Oct 17 10:18:06 2023 -0700 Correct comment for nc SSTable format Patch by frankgh; reviewd by brandonwilliams and bereng for CASSANDRA-18933 --- src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java b/src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java index 4de58b4b6b..6977737bde 100644 --- a/src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java +++ b/src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java @@ -349,7 +349,7 @@ public class BigFormat extends AbstractSSTableFormat
[cassandra] branch trunk updated (088f3ea3e9 -> 06202c9ff3)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 088f3ea3e9 Merge branch 'cassandra-5.0' into trunk new 8c89e2adb7 Correct comment for nc SSTable format new 06202c9ff3 Merge branch 'cassandra-5.0' into trunk The 2 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/io/sstable/format/big/BigFormat.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 06202c9ff3991a67ecc50edf26ba67b4394fef1a Merge: 088f3ea3e9 8c89e2adb7 Author: Brandon Williams AuthorDate: Thu Oct 19 12:29:22 2023 -0500 Merge branch 'cassandra-5.0' into trunk src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18933) Correct comment for nc SSTable format
[
https://issues.apache.org/jira/browse/CASSANDRA-18933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18933:
-
Fix Version/s: 5.0-alpha2
5.1
Source Control Link:
https://github.com/apache/cassandra/commit/8c89e2adb7680ecb4dd3cb2a562206fb8cb50d4a
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
I committed this, thanks.
> Correct comment for nc SSTable format
> -
>
> Key: CASSANDRA-18933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18933
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 5.0-alpha2, 5.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In [CASSANDRA-18134 |https://issues.apache.org/jira/browse/CASSANDRA-18134],
> the {{nc}} SSTable format was introduced. The patch was merged into {{5.0+}},
> however the comment in source incorrectly mentions that the format was added
> to version {{4.1}}.
--
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-18836) Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
[
https://issues.apache.org/jira/browse/CASSANDRA-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1414#comment-1414
]
Caleb Rackliffe commented on CASSANDRA-18836:
-
I'm not having any trouble getting clean runs of \{{ClearSnapshotTest}} locally
either.
> Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
>
>
> Key: CASSANDRA-18836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18836
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/2i Index, Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Maxim Muzafarov
>Priority: Normal
> Fix For: 5.0-alpha2, 5.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It seems that now we're on Java 11 for 5.0, there isn't much reason not to
> use CRC32C as a drop-in replacement for CRC32. SAI isn't even released, so
> has no binary compatibility entanglements, and this should be pretty
> straightforward.
> See https://github.com/apache/bookkeeper/pull/3309
--
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-18872) Remove deprecated crc_check_chance in compression params
[ https://issues.apache.org/jira/browse/CASSANDRA-18872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1421#comment-1421 ] Stefan Miklosovic commented on CASSANDRA-18872: --- Thank you for the review. I will return to this the next week. > Remove deprecated crc_check_chance in compression params > > > Key: CASSANDRA-18872 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18872 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression, Legacy/CQL >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > crc_check_chance was moved from compression parameters and it is a standalone > table parameter. This was done in times of 3.0 so it is now time to get rid > of that in 5.0. -- 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-18836) Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
[
https://issues.apache.org/jira/browse/CASSANDRA-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1425#comment-1425
]
Caleb Rackliffe commented on CASSANDRA-18836:
-
Finished my first pass at review and left a few comments. Once we're happy w/
how we've dealt w/ those, I'll approve both patches. (\{{trunk}} patch looks
identical to 5.0)
> Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
>
>
> Key: CASSANDRA-18836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18836
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/2i Index, Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Maxim Muzafarov
>Priority: Normal
> Fix For: 5.0-alpha2, 5.x
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> It seems that now we're on Java 11 for 5.0, there isn't much reason not to
> use CRC32C as a drop-in replacement for CRC32. SAI isn't even released, so
> has no binary compatibility entanglements, and this should be pretty
> straightforward.
> See https://github.com/apache/bookkeeper/pull/3309
--
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-18941) Support max SSTable size in sorted CQLSSTableWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Guerrero updated CASSANDRA-18941: --- Reviewers: Francisco Guerrero, Maxwell Guo (was: Maxwell Guo) > Support max SSTable size in sorted CQLSSTableWriter > --- > > Key: CASSANDRA-18941 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18941 > Project: Cassandra > Issue Type: Improvement > Components: Tool/sstable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 5.x > > Time Spent: 1h > Remaining Estimate: 0h > > The CQLSSTableWriter can produce a series of SSTables with a bounded size in > the unsorted mode. The functionality is missing in the sorted > CQLSSTableWriter. > It will be great to bringing the parity to the sorted mode, so that it is > able to produce a series of size-bounded SSTable, instead of a single but > giant one. > Unlike the unsorted CQLSSTableWriter, the max SSTable size in the sorted > writer does not require buffering. -- 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] [Created] (CASSANDRASC-78) Fix token-ranges endpoint to o handle gossip-info responses without 'status'
Arjun Ashok created CASSANDRASC-78:
--
Summary: Fix token-ranges endpoint to o handle gossip-info
responses without 'status'
Key: CASSANDRASC-78
URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
Project: Sidecar for Apache Cassandra
Issue Type: Bug
Components: Rest API
Reporter: Arjun Ashok
Assignee: Arjun Ashok
This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
attributes in GossipInfo response to determine the ‘state’ of the node.
Currently, we only check for ‘status’ which can be missing from gossipInfo in
some cases, which will result in a replacement node status to be reported as
`Joining` instead of `Replacing`.
eg.
```
Found gossipInfoEntry=\{generation=1697736379,
schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb, tokens=,
dc=datacenter1, netVersion=12, statusWithPort=BOOT_REPLACE,127.0.0.5:7012}
```
--
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] (CASSANDRASC-78) Fix token-ranges endpoint to o handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Ashok updated CASSANDRASC-78:
---
Description:
This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
attributes in GossipInfo response to determine the ‘state’ of the node.
Currently, we only check for ‘status’ which can be missing from gossipInfo in
some cases, which will result in a replacement node status to be reported as
`Joining` instead of `Replacing`.
eg.
{code:java}
Found gossipInfoEntry={generation=1697736379,
schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb, tokens=,
dc=datacenter1, netVersion=12, statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{code}
was:
This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
attributes in GossipInfo response to determine the ‘state’ of the node.
Currently, we only check for ‘status’ which can be missing from gossipInfo in
some cases, which will result in a replacement node status to be reported as
`Joining` instead of `Replacing`.
eg.
```
Found gossipInfoEntry=\{generation=1697736379,
schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb, tokens=,
dc=datacenter1, netVersion=12, statusWithPort=BOOT_REPLACE,127.0.0.5:7012}
```
> Fix token-ranges endpoint to o handle gossip-info responses without 'status'
>
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{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-website] branch asf-staging updated (636e7070c -> a131155b7)
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 636e7070c generate docs for 1d0135e5 new a131155b7 generate docs for 1d0135e5 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 (636e7070c) \ N -- N -- N refs/heads/asf-staging (a131155b7) 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/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881412 -> 4881412 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18799) Remove org.caffinitas.ohc:ohc-core-j8 dependency
[ https://issues.apache.org/jira/browse/CASSANDRA-18799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1456#comment-1456 ] Ariel Weisberg commented on CASSANDRA-18799: The ASF has a policy against hostile forks so for us to modify OHC and release our own changes to OHC requires us to follow some guidelines that I don't know off the top of my head. I am still trying to get in touch with Robert. For JNA in particular I think we might be able to get away with excluding the dependency from OHC and then providing the newer version as a replacement. It doesn't look like there were breaking changes to JNA that impacted OHC https://github.com/snazy/ohc/commit/0b53560d7cc20aa8b3e2023d937c5495c89f766c https://github.com/snazy/ohc/commit/eafa289547895009f35c87bf908b1fbe5014c27d > Remove org.caffinitas.ohc:ohc-core-j8 dependency > > > Key: CASSANDRA-18799 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18799 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > It seems the `org.caffinitas.ohc:ohc-core-j8` is not required anymore and the > Cassandra project moved away from JDK8 support. The changes are here: > CASSANDRA-18255 > We can remove it. -- 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] (CASSANDRASC-78) Fix token-ranges endpoint to handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Ashok updated CASSANDRASC-78:
---
Summary: Fix token-ranges endpoint to handle gossip-info responses without
'status' (was: Fix token-ranges endpoint to o handle gossip-info responses
without 'status')
> Fix token-ranges endpoint to handle gossip-info responses without 'status'
> --
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{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] (CASSANDRASC-78) Fix token-ranges endpoint to handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Ashok updated CASSANDRASC-78:
---
Bug Category: Parent values: Correctness(12982)
Complexity: Normal
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> Fix token-ranges endpoint to handle gossip-info responses without 'status'
> --
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{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-18922) cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586
[ https://issues.apache.org/jira/browse/CASSANDRA-18922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1463#comment-1463 ] Jai Bheemsen Rao Dhanwada commented on CASSANDRA-18922: --- [~brandon.williams] Thanks for reporting the vulnerability. I see the Fix version is marked as 5.x, do we have any timelines to back port the hostname validation to the 3.x or 4.x branches? > cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586 > - > > Key: CASSANDRA-18922 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18922 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.0.x, 5.x > > > This is failing OWASP: https://nvd.nist.gov/vuln/detail/CVE-2023-4586 > but appears to be a false positive. -- 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] (CASSANDRASC-78) Fix token-ranges endpoint to handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-78:
--
Labels: pull-request-available (was: )
> Fix token-ranges endpoint to handle gossip-info responses without 'status'
> --
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
> Labels: pull-request-available
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{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-18922) cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586
[ https://issues.apache.org/jira/browse/CASSANDRA-18922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1464#comment-1464 ] Brandon Williams commented on CASSANDRA-18922: -- Only 5.0 and trunk are affected. > cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586 > - > > Key: CASSANDRA-18922 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18922 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.0.x, 5.x > > > This is failing OWASP: https://nvd.nist.gov/vuln/detail/CVE-2023-4586 > but appears to be a false positive. -- 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-18836) Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1470#comment-1470 ] Maxim Muzafarov commented on CASSANDRA-18836: - 5.0: https://github.com/apache/cassandra/pull/2782 https://app.circleci.com/pipelines/github/Mmuzaf/cassandra/448/workflows/633e5329-0964-465e-8dbf-60cfcbf70918 trunk: https://github.com/apache/cassandra/pull/2687 https://app.circleci.com/pipelines/github/Mmuzaf/cassandra/447/workflows/019f2769-2def-430e-90df-92985d60a332 > Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter > > > Key: CASSANDRA-18836 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18836 > Project: Cassandra > Issue Type: Improvement > Components: Feature/2i Index, Feature/SAI >Reporter: Caleb Rackliffe >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0-alpha2, 5.x > > Time Spent: 4h 40m > Remaining Estimate: 0h > > It seems that now we're on Java 11 for 5.0, there isn't much reason not to > use CRC32C as a drop-in replacement for CRC32. SAI isn't even released, so > has no binary compatibility entanglements, and this should be pretty > straightforward. > See https://github.com/apache/bookkeeper/pull/3309 -- 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-18836) Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1471#comment-1471 ] Maxim Muzafarov commented on CASSANDRA-18836: - [~maedhroz] I've fixed all your comments both for 5.0 and trunk branches and run the tests. > Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter > > > Key: CASSANDRA-18836 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18836 > Project: Cassandra > Issue Type: Improvement > Components: Feature/2i Index, Feature/SAI >Reporter: Caleb Rackliffe >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0-alpha2, 5.x > > Time Spent: 4h 40m > Remaining Estimate: 0h > > It seems that now we're on Java 11 for 5.0, there isn't much reason not to > use CRC32C as a drop-in replacement for CRC32. SAI isn't even released, so > has no binary compatibility entanglements, and this should be pretty > straightforward. > See https://github.com/apache/bookkeeper/pull/3309 -- 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-18943) http/2 vulnerability: CVE-2023-44487
[ https://issues.apache.org/jira/browse/CASSANDRA-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1476#comment-1476 ] Brandon Williams commented on CASSANDRA-18943: -- ||Branch||CI|| |[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18943-3.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1339/workflows/f88b91ff-e965-43ec-880a-2f544933376c]| |[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-18943-3.11]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1344/workflows/2c434466-0c43-4f45-a466-755bbec224f8]| |[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18943-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1343/workflows/5d2bb173-903c-4770-83d1-a28015595a75], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1343/workflows/cd279cdc-4005-4ffb-8046-bc176e04ff1e]| |[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-18943-4.1]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1340/workflows/1038a061-637f-4333-8278-6cb524d6a1eb], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1340/workflows/462d83a2-9700-4409-8233-645b197234a1]| |[5.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18943-5.0]|[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1342/workflows/9554c7b5-dd60-4f08-8db5-c954febc8ad6], [j17|https://app.circleci.com/pipelines/github/driftx/cassandra/1342/workflows/736405b6-a03d-4e01-be27-63e004019b43]| |[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-18943-trunk]|[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1341/workflows/6fc65390-c439-4a06-a1a5-7408974bde01], [j17|https://app.circleci.com/pipelines/github/driftx/cassandra/1341/workflows/17c70d76-20b2-49ae-a2d2-e4882bb51885]| > http/2 vulnerability: CVE-2023-44487 > > > Key: CASSANDRA-18943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18943 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > https://nvd.nist.gov/vuln/detail/CVE-2023-44487 > Basically anything using http/2 is covered by this, but we don't use it. -- 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-18896) ClientRequestSize metrics should not treat CONTAINS restrictions as being equality-based
[
https://issues.apache.org/jira/browse/CASSANDRA-18896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18896:
Test and Documentation Plan:
n/a
modifying the assumption of one existing test
Status: Patch Available (was: In Progress)
5.0 patch: [https://github.com/apache/cassandra/pull/2829]
> ClientRequestSize metrics should not treat CONTAINS restrictions as being
> equality-based
>
>
> Key: CASSANDRA-18896
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18896
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Metrics
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0.x, 5.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following behavior needs to be changed to consider the column restricted
> by {{CONTAINS}} or {{CONTAINS KEY}} as "read", rather than "provided by the
> client". We already do this for things like range restrictions, and the
> current behavior is inconsistent.
> {noformat}
> @Test
> public void shouldRecordReadMetricsForContainsQuery() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int, ck int, v set, PRIMARY KEY
> (pk, ck))");
> executeNet(CURRENT, "INSERT INTO %s (pk, ck, v) VALUES (1, 1, {1, 2, 3}
> )");
> executeNet(CURRENT, "INSERT INTO %s (pk, ck, v) VALUES (2, 2, {4, 5,
> 6})");
> executeNet(CURRENT, "SELECT * FROM %s WHERE v CONTAINS 1 ALLOW
> FILTERING");
> assertEquals(1, ClientRequestSizeMetrics.totalRowsRead.getCount());
> // The filtering term is provided by the client in the request, so we
> don't consider that column read.
> assertEquals(2, ClientRequestSizeMetrics.totalColumnsRead.getCount());
> }
> {noformat}
> The fix should be literally two lines, one in {{SingleRestriction}} and one
> in the test above.
--
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-18903) Incremental repair never cleans up completed sessions from CoordinatorSessions.sessions
[ https://issues.apache.org/jira/browse/CASSANDRA-18903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-18903: Reviewers: Caleb Rackliffe, Caleb Rackliffe Caleb Rackliffe, Caleb Rackliffe (was: Caleb Rackliffe) Status: Review In Progress (was: Patch Available) > Incremental repair never cleans up completed sessions from > CoordinatorSessions.sessions > --- > > Key: CASSANDRA-18903 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18903 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Repair >Reporter: Abe Ratnofsky >Assignee: Abe Ratnofsky >Priority: Normal > > Currently, there is nothing cleaning up repaired sessions from > org.apache.cassandra.repair.consistent.CoordinatorSessions#sessions. This > causes memory to leak for cluster members with long uptimes and lots of > incremental repair. -- 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 (a131155b7 -> 93c6cc030)
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 a131155b7 generate docs for 1d0135e5 new 93c6cc030 generate docs for 1d0135e5 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 (a131155b7) \ N -- N -- N refs/heads/asf-staging (93c6cc030) 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: site-ui/build/ui-bundle.zip | Bin 4881412 -> 4881412 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18922) cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586
[ https://issues.apache.org/jira/browse/CASSANDRA-18922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1490#comment-1490 ] Jai Bheemsen Rao Dhanwada commented on CASSANDRA-18922: --- thanks [~brandon.williams] can you provide some more details as to why only 5.0 is impacted? Reading through the comments it looks like we need to set the hostname verification by default. Is this derived from the `server_encryption_option`: `require_endpoint_verification` > cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586 > - > > Key: CASSANDRA-18922 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18922 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.0.x, 5.x > > > This is failing OWASP: https://nvd.nist.gov/vuln/detail/CVE-2023-4586 > but appears to be a false positive. -- 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-18922) cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586
[ https://issues.apache.org/jira/browse/CASSANDRA-18922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1494#comment-1494 ] Brandon Williams commented on CASSANDRA-18922: -- This ticket is for the CVE against the driver so that will need to be handled there, and then presumably we would upgrade to that fixed version here. Only 5.0 and trunk are showing this in 'ant dependency-check' which runs OWASP. > cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586 > - > > Key: CASSANDRA-18922 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18922 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.0.x, 5.x > > > This is failing OWASP: https://nvd.nist.gov/vuln/detail/CVE-2023-4586 > but appears to be a false positive. -- 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-18903) Incremental repair never cleans up completed sessions from CoordinatorSessions.sessions
[ https://issues.apache.org/jira/browse/CASSANDRA-18903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776370#comment-17776370 ] Abe Ratnofsky edited comment on CASSANDRA-18903 at 10/19/23 10:44 PM: -- PRs up: ||Release branch||PR|| |trunk|[https://github.com/apache/cassandra/pull/2810|https://github.com/apache/cassandra/pull/2810]| |5.0|[https://github.com/apache/cassandra/pull/2811| https://github.com/apache/cassandra/pull/2811 ]| |4.1|[https://github.com/apache/cassandra/pull/2812|https://github.com/apache/cassandra/pull/2812]| |4.0|[https://github.com/apache/cassandra/pull/2813|https://github.com/apache/cassandra/pull/2813]| was (Author: aratnofsky): PRs up: ||Release branch||PR|| |trunk|https://github.com/apache/cassandra/pull/2810| |5.0|https://github.com/apache/cassandra/pull/2811| |4.1|https://github.com/apache/cassandra/pull/2812| |4.0|https://github.com/apache/cassandra/pull/2813| > Incremental repair never cleans up completed sessions from > CoordinatorSessions.sessions > --- > > Key: CASSANDRA-18903 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18903 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Repair >Reporter: Abe Ratnofsky >Assignee: Abe Ratnofsky >Priority: Normal > > Currently, there is nothing cleaning up repaired sessions from > org.apache.cassandra.repair.consistent.CoordinatorSessions#sessions. This > causes memory to leak for cluster members with long uptimes and lots of > incremental repair. -- 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-18903) Incremental repair never cleans up completed sessions from CoordinatorSessions.sessions
[ https://issues.apache.org/jira/browse/CASSANDRA-18903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1499#comment-1499 ] Caleb Rackliffe commented on CASSANDRA-18903: - Approved all 4 PRs w/ a couple minor nits. > Incremental repair never cleans up completed sessions from > CoordinatorSessions.sessions > --- > > Key: CASSANDRA-18903 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18903 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Repair >Reporter: Abe Ratnofsky >Assignee: Abe Ratnofsky >Priority: Normal > > Currently, there is nothing cleaning up repaired sessions from > org.apache.cassandra.repair.consistent.CoordinatorSessions#sessions. This > causes memory to leak for cluster members with long uptimes and lots of > incremental repair. -- 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 (93c6cc030 -> 4747f3c3f)
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 93c6cc030 generate docs for 1d0135e5 new 4747f3c3f generate docs for 1d0135e5 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 (93c6cc030) \ N -- N -- N refs/heads/asf-staging (4747f3c3f) 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/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881412 -> 4881412 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-79) Sidecar should be able to load metadata even if the local instance is unavailable
Doug Rohrer created CASSANDRASC-79: -- Summary: Sidecar should be able to load metadata even if the local instance is unavailable Key: CASSANDRASC-79 URL: https://issues.apache.org/jira/browse/CASSANDRASC-79 Project: Sidecar for Apache Cassandra Issue Type: Improvement Components: Rest API Reporter: Doug Rohrer Assignee: Doug Rohrer Today, the sidecar’s CassandraAdapter/CqlSessionProvider uses a load balancing policy that only allows connections to a single instance configured for one of the managed instances of Cassandra. However, this is both unnecessary and potentially harmful, as requests to that instance’s hostname will fail to retrieve information like keyspace/cluster metadata when that instance is unavailable, and will not receive any updates to metadata either, which can cause stale metadata to be used. Instead, the CqlSessionProvider should take a list of contact points and use them to connect to the whole cluster (or a subset of nodes) without the single-instance load balancing policy. Where it is necessary to query an individual instance (system tables, attempts to check the health of a particular instance) we can, instead, use the driver’s ability to direct queries to a specific host on a per-statement basis. -- 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-18922) cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586
[ https://issues.apache.org/jira/browse/CASSANDRA-18922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1523#comment-1523 ] Jai Bheemsen Rao Dhanwada commented on CASSANDRA-18922: --- Thanks, I am trying to identify the impact of CVE-2023-4586 on the cassandra server and if that affects 3.x and 4.x versions of cassandra. From [CASSANDRA-18812|https://issues.apache.org/jira/browse/CASSANDRA-18812?focusedCommentId=17760806&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17760806] I see that the server is impacted but doesn't have more details on why only the trunk and 5.0 are impacted and not 3.x and 4.x. > cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586 > - > > Key: CASSANDRA-18922 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18922 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.0.x, 5.x > > > This is failing OWASP: https://nvd.nist.gov/vuln/detail/CVE-2023-4586 > but appears to be a false positive. -- 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-18941) Support max SSTable size in sorted CQLSSTableWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxwell Guo updated CASSANDRA-18941: Status: Needs Committer (was: Patch Available) > Support max SSTable size in sorted CQLSSTableWriter > --- > > Key: CASSANDRA-18941 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18941 > Project: Cassandra > Issue Type: Improvement > Components: Tool/sstable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 5.x > > Time Spent: 2.5h > Remaining Estimate: 0h > > The CQLSSTableWriter can produce a series of SSTables with a bounded size in > the unsorted mode. The functionality is missing in the sorted > CQLSSTableWriter. > It will be great to bringing the parity to the sorted mode, so that it is > able to produce a series of size-bounded SSTable, instead of a single but > giant one. > Unlike the unsorted CQLSSTableWriter, the max SSTable size in the sorted > writer does not require buffering. -- 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-18836) Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1563#comment-1563 ] Zhao Yang commented on CASSANDRA-18836: --- Thanks for the patch. LGTM > Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter > > > Key: CASSANDRA-18836 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18836 > Project: Cassandra > Issue Type: Improvement > Components: Feature/2i Index, Feature/SAI >Reporter: Caleb Rackliffe >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0-alpha2, 5.x > > Time Spent: 5h > Remaining Estimate: 0h > > It seems that now we're on Java 11 for 5.0, there isn't much reason not to > use CRC32C as a drop-in replacement for CRC32. SAI isn't even released, so > has no binary compatibility entanglements, and this should be pretty > straightforward. > See https://github.com/apache/bookkeeper/pull/3309 -- 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 (4747f3c3f -> 3ab78488e)
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 4747f3c3f generate docs for 1d0135e5 new 3ab78488e generate docs for 1d0135e5 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 (4747f3c3f) \ N -- N -- N refs/heads/asf-staging (3ab78488e) 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/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881412 -> 4881412 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
