[jira] [Commented] (CASSANDRA-18394) Add nodetool to show top n read/write table
[ https://issues.apache.org/jira/browse/CASSANDRA-18394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707119#comment-17707119 ] maxwellguo commented on CASSANDRA-18394: add tool support though we may can get from monitor web site. > Add nodetool to show top n read/write table > > > Key: CASSANDRA-18394 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18394 > Project: Cassandra > Issue Type: Improvement >Reporter: maxwellguo >Assignee: maxwellguo >Priority: Normal > > add nodetool to show the read/write top n table name -- 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-18394) Add nodetool to show top n read/write table
maxwellguo created CASSANDRA-18394: -- Summary: Add nodetool to show top n read/write table Key: CASSANDRA-18394 URL: https://issues.apache.org/jira/browse/CASSANDRA-18394 Project: Cassandra Issue Type: Improvement Reporter: maxwellguo Assignee: maxwellguo add nodetool to show the read/write top n table name -- 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-18124) Config parameter keystore_password should be nullable
[ https://issues.apache.org/jira/browse/CASSANDRA-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707072#comment-17707072 ] Maulin Vasavada commented on CASSANDRA-18124: - Hi [~rtib] Please confirm with the latest PR if the changes look good based on your testing. [~smiklosovic] I've resolved your comment on the PR, let me know if you want me to start the circleCI or you would kick it off. Thanks > Config parameter keystore_password should be nullable > - > > Key: CASSANDRA-18124 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18124 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Tibor Repasi >Assignee: Maulin Vasavada >Priority: Normal > Fix For: 4.1.x, 5.x > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Some SSL configuration may pass unencrypted private keys. PEMReader might > accept that by assuming keyPassword to be null in that case (e.g. > https://github.com/apache/cassandra/blob/f9e033f519c14596da4dc954875756a69aea4e78/src/java/org/apache/cassandra/security/PEMReader.java#L103). > Current configuration reader does not accept keystore_password parameter to > be set null or empty in the cassandra.yaml. -- 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-18378) CEP-15 (Accord) accord.messages.Defer rejects Recurrent retry of Commit
[
https://issues.apache.org/jira/browse/CASSANDRA-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-18378:
--
Resolution: Fixed
Status: Resolved (was: Open)
> CEP-15 (Accord) accord.messages.Defer rejects Recurrent retry of Commit
> ---
>
> Key: CASSANDRA-18378
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18378
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: David Capwell
>Priority: Normal
> Fix For: 5.x
>
>
> {code}
> java.lang.IllegalStateException: Recurrent retry of Commit{…}
> at accord.messages.Defer.add(Defer.java:63)
> at accord.messages.Commit.apply(Commit.java:167)
> at accord.messages.Commit.apply(Commit.java:42)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation$ForFunction.apply(AsyncOperation.java:321)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation$ForFunction.apply(AsyncOperation.java:308)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation.runInternal(AsyncOperation.java:226)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation.run(AsyncOperation.java:268)
> {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-18378) CEP-15 (Accord) accord.messages.Defer rejects Recurrent retry of Commit
[
https://issues.apache.org/jira/browse/CASSANDRA-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707070#comment-17707070
]
David Capwell commented on CASSANDRA-18378:
---
Hit this in BurnTest while debugging
https://issues.apache.org/jira/browse/CASSANDRA-18364 and think its a rather
simple fix, so will handle there
{code}
$ git diff
diff --git a/accord-core/src/main/java/accord/messages/Commit.java
b/accord-core/src/main/java/accord/messages/Commit.java
index ce010ae..fc756b3 100644
--- a/accord-core/src/main/java/accord/messages/Commit.java
+++ b/accord-core/src/main/java/accord/messages/Commit.java
@@ -162,7 +162,8 @@ public class Commit extends TxnRequest
case Insufficient:
SafeCommand safeCommand = safeStore.command(txnId);
Invariants.checkState(!safeCommand.current().known().isDefinitionKnown());
-if (defer == null)
+// When isDone this.process() is called and all CommandStores
run apply again; so safe to create a new one
+if (defer == null || defer.isDone)
defer = new Defer(DefinitionOnly, Committed.minKnown,
Commit.this);
defer.add(safeStore, safeCommand, safeStore.commandStore());
return ReadNack.NotCommitted;
{code}
> CEP-15 (Accord) accord.messages.Defer rejects Recurrent retry of Commit
> ---
>
> Key: CASSANDRA-18378
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18378
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: David Capwell
>Priority: Normal
> Fix For: 5.x
>
>
> {code}
> java.lang.IllegalStateException: Recurrent retry of Commit{…}
> at accord.messages.Defer.add(Defer.java:63)
> at accord.messages.Commit.apply(Commit.java:167)
> at accord.messages.Commit.apply(Commit.java:42)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation$ForFunction.apply(AsyncOperation.java:321)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation$ForFunction.apply(AsyncOperation.java:308)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation.runInternal(AsyncOperation.java:226)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation.run(AsyncOperation.java:268)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707057#comment-17707057 ] Brandon Williams edited comment on CASSANDRA-18391 at 3/30/23 11:38 PM: This test is being skipped, but the 'since' fixture, when it detects an upgrade, checks if any of the involved versions are excluded and then skips them, but doing this does the ccm setup for the old version first. If you don't already have this setup done, you can get a really long skip: bq. 1 skipped in 241.68 seconds We can skip out on these upgrades faster, like [this|https://github.com/driftx/cassandra-dtest/commit/4481f86e80f9625bcb1cfc36e1a97028d235b1d0]. [Upgrade tests on trunk|https://app.circleci.com/pipelines/github/driftx/cassandra/946/workflows/5afeccc6-753e-4a88-90eb-ecd0e56ac8cc]. [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/2405/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/2405/pipeline] was (Author: brandon.williams): This test is being skipped, but the 'since' fixture, when it detects an upgrade, checks if any of the involved versions are excluded and then skips them, but doing this does the ccm setup for the old version first. If you don't already have this setup done, you can get a really long skip: bq. 1 skipped in 241.68 seconds We can skip out on these upgrades faster, like [this|https://github.com/driftx/cassandra-dtest/commit/4481f86e80f9625bcb1cfc36e1a97028d235b1d0]. [Upgrade tests on trunk|https://app.circleci.com/pipelines/github/driftx/cassandra/946/workflows/5afeccc6-753e-4a88-90eb-ecd0e56ac8cc]. > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.x > > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707057#comment-17707057 ] Brandon Williams edited comment on CASSANDRA-18391 at 3/30/23 10:44 PM: This test is being skipped, but the 'since' fixture, when it detects an upgrade, checks if any of the involved versions are excluded and then skips them, but doing this does the ccm setup for the old version first. If you don't already have this setup done, you can get a really long skip: bq. 1 skipped in 241.68 seconds We can skip out on these upgrades faster, like [this|https://github.com/driftx/cassandra-dtest/commit/4481f86e80f9625bcb1cfc36e1a97028d235b1d0]. [Upgrade tests on trunk|https://app.circleci.com/pipelines/github/driftx/cassandra/946/workflows/5afeccc6-753e-4a88-90eb-ecd0e56ac8cc]. was (Author: brandon.williams): This test is being skipped, but the 'since' fixture, when it detects an upgrade, checks if any of the involved versions are excluded and then skips them, but doing this does the ccm setup for the old version first. If you don't already have this setup done, you can get a really long skip: bq. 1 skipped in 241.68 seconds We can skip out on these upgrades faster, like [this|https://github.com/driftx/cassandra-dtest/commit/4481f86e80f9625bcb1cfc36e1a97028d235b1d0]. [Upgrade tests on trunk|https://app.circleci.com/pipelines/github/driftx/cassandra/945/workflows/15f2c5b8-835b-4a58-9799-b3e69be77bb9]. > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.x > > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707057#comment-17707057 ] Brandon Williams edited comment on CASSANDRA-18391 at 3/30/23 10:29 PM: This test is being skipped, but the 'since' fixture, when it detects an upgrade, checks if any of the involved versions are excluded and then skips them, but doing this does the ccm setup for the old version first. If you don't already have this setup done, you can get a really long skip: bq. 1 skipped in 241.68 seconds We can skip out on these upgrades faster, like [this|https://github.com/driftx/cassandra-dtest/commit/4481f86e80f9625bcb1cfc36e1a97028d235b1d0]. [Upgrade tests on trunk|https://app.circleci.com/pipelines/github/driftx/cassandra/945/workflows/15f2c5b8-835b-4a58-9799-b3e69be77bb9]. was (Author: brandon.williams): This test is being skipped, but the 'since' fixture, when it detects and upgrade, checks if any of the involved versions are excluded and then skips them, but doing this does the ccm setup for the old version first. If you don't already have this setup done, you can get a really long skip: bq. 1 skipped in 241.68 seconds We can skip out on these upgrades faster, like [this|https://github.com/driftx/cassandra-dtest/commit/4481f86e80f9625bcb1cfc36e1a97028d235b1d0]. [Upgrade tests on trunk|https://app.circleci.com/pipelines/github/driftx/cassandra/945/workflows/15f2c5b8-835b-4a58-9799-b3e69be77bb9]. > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.x > > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18391: - Test and Documentation Plan: run CI Status: Patch Available (was: Open) > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.x > > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707057#comment-17707057 ] Brandon Williams commented on CASSANDRA-18391: -- This test is being skipped, but the 'since' fixture, when it detects and upgrade, checks if any of the involved versions are excluded and then skips them, but doing this does the ccm setup for the old version first. If you don't already have this setup done, you can get a really long skip: bq. 1 skipped in 241.68 seconds We can skip out on these upgrades faster, like [this|https://github.com/driftx/cassandra-dtest/commit/4481f86e80f9625bcb1cfc36e1a97028d235b1d0]. [Upgrade tests on trunk|https://app.circleci.com/pipelines/github/driftx/cassandra/945/workflows/15f2c5b8-835b-4a58-9799-b3e69be77bb9]. > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.x > > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-18391: Assignee: Brandon Williams > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Assignee: Brandon Williams >Priority: Normal > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18391: - Fix Version/s: 5.x > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.x > > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-18366: Assignee: Brandon Williams > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-18366: Assignee: (was: Brandon Williams) > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707052#comment-17707052 ] Brandon Williams edited comment on CASSANDRA-18391 at 3/30/23 9:58 PM: --- Near as I can tell, this shouldn't be running. It's decorated max_version='3.99' [here|https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/cql_tests.py#L1538], the doc says "Checks that 3.0 serializes RangeTombstoneLists correctly when communicating with 2.2 nodes", and is indeed skipped when I try to run it. One thing I noticed that the class name is no longer 'TestCQL' and is instead 'cls', I think from the transition to python 3.8, perhaps due to this inheriting UpgradeTester which inherits from both Tester and the builtin abstract base class. was (Author: brandon.williams): Near as I can tell, this shouldn't be running. It's decorated max_version='3.99' [here|https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/cql_tests.py#L1538], the doc says "Checks that 3.0 serializes RangeTombstoneLists correctly when communicating with 2.2 nodes", and is indeed skipped when I try to run it. > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Priority: Normal > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707052#comment-17707052 ] Brandon Williams commented on CASSANDRA-18391: -- Near as I can tell, this shouldn't be running. It's decorated max_version='3.99' [here|https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/cql_tests.py#L1538], the doc says "Checks that 3.0 serializes RangeTombstoneLists correctly when communicating with 2.2 nodes", and is indeed skipped when I try to run it. > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Priority: Normal > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18391: - Description: Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% link: https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ Error message: failed on setup with "Failed: Timeout >900.0s" was: Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% link: [https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-] upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ Error message: failed on setup with "Failed: Timeout >900.0s" > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Priority: Normal > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18370) BulkLoader tool initializes schema unnecessarily via streaming - 4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707051#comment-17707051
]
Jon Meredith commented on CASSANDRA-18370:
--
+1
> BulkLoader tool initializes schema unnecessarily via streaming - 4.0
>
>
> Key: CASSANDRA-18370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18370
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Yijun Mao
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Similar to CASSANDRA-17740, {{BulkLoader}} initializes the schema/system
> keyspace, which caused the issue in bulk loader tool. See more details in
> CASSANDRA-17740. Please help fix the issue in 4.0 branch as well. Thanks.
--
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-18370) BulkLoader tool initializes schema unnecessarily via streaming - 4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Meredith updated CASSANDRA-18370:
-
Status: Ready to Commit (was: Review In Progress)
> BulkLoader tool initializes schema unnecessarily via streaming - 4.0
>
>
> Key: CASSANDRA-18370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18370
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Yijun Mao
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Similar to CASSANDRA-17740, {{BulkLoader}} initializes the schema/system
> keyspace, which caused the issue in bulk loader tool. See more details in
> CASSANDRA-17740. Please help fix the issue in 4.0 branch as well. Thanks.
--
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-18370) BulkLoader tool initializes schema unnecessarily via streaming - 4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Meredith updated CASSANDRA-18370:
-
Reviewers: Jon Meredith, Jon Meredith
Status: Review In Progress (was: Patch Available)
> BulkLoader tool initializes schema unnecessarily via streaming - 4.0
>
>
> Key: CASSANDRA-18370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18370
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Yijun Mao
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Similar to CASSANDRA-17740, {{BulkLoader}} initializes the schema/system
> keyspace, which caused the issue in bulk loader tool. See more details in
> CASSANDRA-17740. Please help fix the issue in 4.0 branch as well. Thanks.
--
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-18392) flaky test org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect-compression.jdk1.8 on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18392:
-
Resolution: Duplicate
Status: Resolved (was: Open)
> flaky test
> org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect-compression.jdk1.8
> on trunk
> -
>
> Key: CASSANDRA-18392
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18392
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Priority: Normal
>
> Failed 3 times in the last 5 runs. Flakiness: 100%, Stability: 40%
> expected:<1> but was:<0>
> Stack:
> {code}
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
> at
> org.apache.cassandra.net.ConnectionTest.lambda$testMessageDeliveryOnReconnect$45(ConnectionTest.java:772)
> at
> org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:265)
> at
> org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:238)
> at
> org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect(ConnectionTest.java:751)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18370) BulkLoader tool initializes schema unnecessarily via streaming - 4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707006#comment-17707006
]
Caleb Rackliffe edited comment on CASSANDRA-18370 at 3/30/23 8:57 PM:
--
[4.0 patch|https://github.com/apache/cassandra/pull/2255]
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-18370]
Tests look clean. The timeout in {{FailingRepairTest}} reproduces on
{{cassandra-4.0}}, and I think may be a result of CASSANDRA-17116 not being on
4.0.
was (Author: maedhroz):
[4.0 patch|https://github.com/apache/cassandra/pull/2255]
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-18370]
Tests look clean. The timeout in {{FailingRepairTest}} reproduces on
{{cassandra-4.0}}.
> BulkLoader tool initializes schema unnecessarily via streaming - 4.0
>
>
> Key: CASSANDRA-18370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18370
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Yijun Mao
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Similar to CASSANDRA-17740, {{BulkLoader}} initializes the schema/system
> keyspace, which caused the issue in bulk loader tool. See more details in
> CASSANDRA-17740. Please help fix the issue in 4.0 branch as well. Thanks.
--
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-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707035#comment-17707035 ] Maxim Muzafarov commented on CASSANDRA-17797: - [~smiklosovic] You have done so much to move this PR forward, thank you! I have scheduled the build to check: https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2402/ > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 5.x > > Time Spent: 18h 50m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16895) Build with Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707024#comment-17707024 ] Josh McKenzie commented on CASSANDRA-16895: --- Strong +1 to making it easy to work with non-LTS versions; also get the benefit of some of this work happening incrementally instead of the lift being as big as this 11-17 one has been. I'd track that in a different ticket thought. :) > Build with Java 17 > -- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Epic > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.x > > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup > *NOTE:* GC tuning, performance testing were never agreed to be part of this > ticket. > Below is a snapshot of current CI failures with JDK17, it will be updated on > a regular basis with a date of update > *March 19th 2023* > || ||Failing Test Classes||Ticket Numbers|| > | |_Python DTests_| | > |1|test_sjk|CASSANDRA-18343| > | |_Java Ditributed Tests_| | > |1-6|org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest - all > tests, > org.apache.cassandra.distributed.test.PrepareBatchStatementsTest - all tests, > org.apache.cassandra.distributed.test.IPMembershipTest - both tests, > org.apache.cassandra.distributed.test.MixedModeFuzzTest, > org.apache.cassandra.distributed.test.ReprepareFuzzTest, > org.apache.cassandra.distributed.test.ReprepareNewBehaviourTest|CASSANDRA-16304| > |7,8|org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest > - all tests > org.apache.cassandra.distributed.test.InternodeEncryptionOptionsTest - all > tests|Could be related to CASSANDRA-18180, to be checked | > |9|org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest - > 2 tests|CASSANDRA-18180| > | |_Unit Tests_| | > |1|org.apache.cassandra.repair.RepairJobTest - 1 test|CASSANDRA-17884| > |2|org.apache.cassandra.security.SSLFactoryTest - all tests|CASSANDRA-17992| > |3,4|org.apache.cassandra.db.memtable.MemtableSizeOffheapBuffersTest, > org.apache.cassandra.utils.concurrent.RefCountedTest|CASSANDRA-18329| > |5,6|org.apache.cassandra.cql3.validation.entities.UFJavaTest, > org.apache.cassandra.cql3.validation.entities.UFSecurityTest|CASSANDRA-18190| > | | | | > | | | | > -- 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-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17797: -- Status: Needs Committer (was: Patch Available) > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 5.x > > Time Spent: 18h 50m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- 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-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17797: -- Status: Patch Available (was: In Progress) reviewed patch by myself here: https://github.com/apache/cassandra/pull/2046/ > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 5.x > > Time Spent: 18h 50m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- 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-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17797: -- Status: In Progress (was: Changes Suggested) > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 5.x > > Time Spent: 18h 50m > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- 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-18390) Run Sonar analyzer over the Cassandra project
[
https://issues.apache.org/jira/browse/CASSANDRA-18390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707020#comment-17707020
]
Josh McKenzie commented on CASSANDRA-18390:
---
Right. Hence the documentation angle; the sonarlint plugin should integrate
w/the sonarqube instance and pick up the rules there. Was a passing thought on
the "auto-magically do this as part of generating idea files", but likely
wouldn't work since it requires the plugin + likely auth.
> Run Sonar analyzer over the Cassandra project
> -
>
> Key: CASSANDRA-18390
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18390
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As we already have Cassandra's project configured for the sonarcloud.io
> INFRA-24196, I wonder if we will be able to release branches, trunk, and pull
> requests to get analyzed by the SonarAnalyzer tool.
> Sonar is a code quality and security tool that is free to open-source
> projects and recommended by the INFRA team:
> https://cwiki.apache.org/confluence/display/INFRA/SonarCloud+for+ASF+projects
> It can have the following benefits without introducing any drawbacks (except
> for a few lines of source code)
> - visualise the LFH problems to work on;
> - see the trends in the source code;
> - add an extra layer of static code analysis;
> Changes below I have tested it locally with my SonarQube deployed on
> http://localhost:9000 and run the `act` for the GA part of the PR. It seems
> to work and parse classes correctly, but there are a few steps that need to
> be done by Cassandra's Committer or PMC (I do not have sufficient privileges):
> - Get the {{sonar.projectKey}} from the INFRA team;
> - make sure that the {{SONARCLOUD_TOKEN}} is available for GA and enabled for
> the project;
--
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-18370) BulkLoader tool initializes schema unnecessarily via streaming - 4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707006#comment-17707006
]
Caleb Rackliffe edited comment on CASSANDRA-18370 at 3/30/23 7:56 PM:
--
[4.0 patch|https://github.com/apache/cassandra/pull/2255]
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-18370]
Tests look clean. The timeout in {{FailingRepairTest}} reproduces on
{{cassandra-4.0}}.
was (Author: maedhroz):
[4.0 patch|https://github.com/apache/cassandra/pull/2255]
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-18370]
Tests look clean, except for a timeout in {{FailingRepairTest}} that doesn't
reproduce locally.
> BulkLoader tool initializes schema unnecessarily via streaming - 4.0
>
>
> Key: CASSANDRA-18370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18370
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Yijun Mao
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Similar to CASSANDRA-17740, {{BulkLoader}} initializes the schema/system
> keyspace, which caused the issue in bulk loader tool. See more details in
> CASSANDRA-17740. Please help fix the issue in 4.0 branch as well. Thanks.
--
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-18393) Test failure: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1: clusterMinVersion=3.11]-compression.jdk1.8 on trun
Josh McKenzie created CASSANDRA-18393:
-
Summary: Test failure:
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1:
clusterMinVersion=3.11]-compression.jdk1.8 on trunk
Key: CASSANDRA-18393
URL: https://issues.apache.org/jira/browse/CASSANDRA-18393
Project: Cassandra
Issue Type: Bug
Components: Test/unit
Reporter: Josh McKenzie
Failed 1 times in the last 1 runs. Flakiness: 0%, Stability: 0%
{code}
Error Message
5.0.0-SNAPSHOT boolean:false
Stacktrace
junit.framework.AssertionFailedError: 5.0.0-SNAPSHOT boolean:false
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$1(InsertUpdateIfConditionTest.java:70)
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:95)
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:89)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18393) Test failure: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1: clusterMinVersion=3.11]-compression.jdk1.8 on trun
[
https://issues.apache.org/jira/browse/CASSANDRA-18393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-18393:
--
Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear
Impact(13164)
Complexity: Normal
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> Test failure:
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1:
> clusterMinVersion=3.11]-compression.jdk1.8 on trunk
> --
>
> Key: CASSANDRA-18393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18393
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Priority: Normal
>
> Failed 1 times in the last 1 runs. Flakiness: 0%, Stability: 0%
> {code}
> Error Message
> 5.0.0-SNAPSHOT boolean:false
> Stacktrace
> junit.framework.AssertionFailedError: 5.0.0-SNAPSHOT boolean:false
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$1(InsertUpdateIfConditionTest.java:70)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:95)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:89)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18392) flaky test org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect-compression.jdk1.8 on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-18392:
--
Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear
Impact(13164)
Complexity: Normal
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> flaky test
> org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect-compression.jdk1.8
> on trunk
> -
>
> Key: CASSANDRA-18392
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18392
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Priority: Normal
>
> Failed 3 times in the last 5 runs. Flakiness: 100%, Stability: 40%
> expected:<1> but was:<0>
> Stack:
> {code}
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
> at
> org.apache.cassandra.net.ConnectionTest.lambda$testMessageDeliveryOnReconnect$45(ConnectionTest.java:772)
> at
> org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:265)
> at
> org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:238)
> at
> org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect(ConnectionTest.java:751)
> {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] [Created] (CASSANDRA-18392) flaky test org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect-compression.jdk1.8 on trunk
Josh McKenzie created CASSANDRA-18392:
-
Summary: flaky test
org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect-compression.jdk1.8
on trunk
Key: CASSANDRA-18392
URL: https://issues.apache.org/jira/browse/CASSANDRA-18392
Project: Cassandra
Issue Type: Bug
Components: Test/unit
Reporter: Josh McKenzie
Failed 3 times in the last 5 runs. Flakiness: 100%, Stability: 40%
expected:<1> but was:<0>
Stack:
{code}
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at
org.apache.cassandra.net.ConnectionTest.lambda$testMessageDeliveryOnReconnect$45(ConnectionTest.java:772)
at
org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:265)
at
org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:238)
at
org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect(ConnectionTest.java:751)
{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] [Created] (CASSANDRA-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
Josh McKenzie created CASSANDRA-18391: - Summary: consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk Key: CASSANDRA-18391 URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 Project: Cassandra Issue Type: Bug Components: Test/dtest/python Reporter: Josh McKenzie Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% link: [https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-] upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18391) consistent timeout: dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-18391: -- Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear Impact(13164) Complexity: Normal Discovered By: DTest Severity: Normal Status: Open (was: Triage Needed) > consistent timeout: > dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones > on trunk > -- > > Key: CASSANDRA-18391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18391 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Priority: Normal > > Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0% > link: > [https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-] > upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/ > Error message: failed on setup with "Failed: Timeout >900.0s" -- 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-18370) BulkLoader tool initializes schema unnecessarily via streaming - 4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18370:
Status: Patch Available (was: In Progress)
[4.0 patch|https://github.com/apache/cassandra/pull/2255]
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-18370]
Tests look clean, except for a timeout in {{FailingRepairTest}} that doesn't
reproduce locally.
> BulkLoader tool initializes schema unnecessarily via streaming - 4.0
>
>
> Key: CASSANDRA-18370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18370
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Yijun Mao
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Similar to CASSANDRA-17740, {{BulkLoader}} initializes the schema/system
> keyspace, which caused the issue in bulk loader tool. See more details in
> CASSANDRA-17740. Please help fix the issue in 4.0 branch as well. Thanks.
--
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-18370) BulkLoader tool initializes schema unnecessarily via streaming - 4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18370:
Test and Documentation Plan: Avoid regressions in {{RepairErrorsTest}},
{{BulkLoaderTest}}, and {{SSTableLoaderEncryptionOptionsTest}} (which tests
{{BulkLoader}} streaming), and verify that not allowing early calls to
{{getPreferredIP()}} in {{NettyStreamingMessageSender}} _does_ break
{{RepairErrorsTest}}. (was: Avoid regressions in {{RepairErrorsTest}},
{{BulkLoaderTest}}, and {{SSTableLoaderEncryptionOptionsTest}}, and verify that
not allowing early calls to {{getPreferredIP()}} in
{{NettyStreamingMessageSender}} _does_ break {{RepairErrorsTest}}.)
> BulkLoader tool initializes schema unnecessarily via streaming - 4.0
>
>
> Key: CASSANDRA-18370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18370
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Yijun Mao
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x
>
>
> Similar to CASSANDRA-17740, {{BulkLoader}} initializes the schema/system
> keyspace, which caused the issue in bulk loader tool. See more details in
> CASSANDRA-17740. Please help fix the issue in 4.0 branch as well. Thanks.
--
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 (3be08899 -> 1ff53b41)
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 3be08899 generate docs for 8612e581 new 1ff53b41 generate docs for 8612e581 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 (3be08899) \ N -- N -- N refs/heads/asf-staging (1ff53b41) 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 4796442 -> 4796442 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] [Updated] (CASSANDRA-18370) BulkLoader tool initializes schema unnecessarily via streaming - 4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18370:
Test and Documentation Plan: Avoid regressions in {{RepairErrorsTest}},
{{BulkLoaderTest}}, and {{SSTableLoaderEncryptionOptionsTest}}, and verify that
not allowing early calls to {{getPreferredIP()}} in
{{NettyStreamingMessageSender}} _does_ break {{RepairErrorsTest}}.
> BulkLoader tool initializes schema unnecessarily via streaming - 4.0
>
>
> Key: CASSANDRA-18370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18370
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Yijun Mao
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x
>
>
> Similar to CASSANDRA-17740, {{BulkLoader}} initializes the schema/system
> keyspace, which caused the issue in bulk loader tool. See more details in
> CASSANDRA-17740. Please help fix the issue in 4.0 branch as well. Thanks.
--
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-18389) jackson-core-2.13.2.jar vulnerability: CVE-2022-45688
[ https://issues.apache.org/jira/browse/CASSANDRA-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706503#comment-17706503 ] Brandon Williams edited comment on CASSANDRA-18389 at 3/30/23 3:15 PM: --- https://nvd.nist.gov/vuln/detail/CVE-2022-45688 bq. A stack overflow in the XML.toJSONObject component of hutool-json v5.8.10 allows attackers to cause a Denial of Service (DoS) via crafted JSON or XML data. We aren't calling any 'toJSONObject' things, we can suppress: ||Branch||CI|| |[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-18389-3.11]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/942/workflows/82eb5bdb-e8a7-47f2-9fbf-e6d6eee523b5]| |[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18389-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/939/workflows/dfc592a1-22a7-4485-997e-09f85213a957], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/939/workflows/2c36af64-3f2e-4b76-bba6-9e486c6aa745]| |[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-18389-4.1]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/938/workflows/eddd2ec3-23ca-4b73-9e01-23c0179541ed], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/938/workflows/d91749d6-9b97-46a4-9934-532ac0c817f4]| |[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-18389-trunk]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/937/workflows/7b5ce52d-aa36-415c-97e8-edd1c743e39d], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/937/workflows/3d9a11ff-bfb1-4a31-a29b-2f08a5f34e11]| was (Author: brandon.williams): https://nvd.nist.gov/vuln/detail/CVE-2022-45688 bq. A stack overflow in the XML.toJSONObject component of hutool-json v5.8.10 allows attackers to cause a Denial of Service (DoS) via crafted JSON or XML data. We aren't calling any 'toJSONObject' things, we can suppress: ||Branch||CI|| |[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18389-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/939/workflows/dfc592a1-22a7-4485-997e-09f85213a957], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/939/workflows/2c36af64-3f2e-4b76-bba6-9e486c6aa745]| |[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-18389-4.1]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/938/workflows/eddd2ec3-23ca-4b73-9e01-23c0179541ed], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/938/workflows/d91749d6-9b97-46a4-9934-532ac0c817f4]| |[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-18389-trunk]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/937/workflows/7b5ce52d-aa36-415c-97e8-edd1c743e39d], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/937/workflows/3d9a11ff-bfb1-4a31-a29b-2f08a5f34e11]| > jackson-core-2.13.2.jar vulnerability: CVE-2022-45688 > - > > Key: CASSANDRA-18389 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18389 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x > > > This is currently failing in the OWASP scan. -- 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-18389) jackson-core-2.13.2.jar vulnerability: CVE-2022-45688
[ https://issues.apache.org/jira/browse/CASSANDRA-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18389: - Fix Version/s: 3.11.x > jackson-core-2.13.2.jar vulnerability: CVE-2022-45688 > - > > Key: CASSANDRA-18389 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18389 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x > > > This is currently failing in the OWASP scan. -- 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-16999) system.peers and system.peers_v2 do not contain the native_transport and/or native_transport_port_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-16999: - Fix Version/s: 4.1.x > system.peers and system.peers_v2 do not contain the native_transport and/or > native_transport_port_ssl > - > > Key: CASSANDRA-16999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16999 > Project: Cassandra > Issue Type: Bug > Components: Local/Other >Reporter: Steve Lacerda >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > > system.peers_v2 includes a “native_port” but has no notion of > native_transport_port vs. native_transport_port_ssl. Given this limited > information, there’s no clear way for the driver to know that different ports > are being used for SSL vs. non-SSL or which of those two ports is identified > by “native_port”. > > The issue we ran into is that the java driver, since it has no notion of the > transport port SSL, the driver was only using the contact points and was not > load balancing. > > The customer had both set: > native_transport_port: 9042 > native_transport_port_ssl: 9142 > > They were attempting to connect to 9142, but that was failing. They could > only use 9042, and so their applications load balancing was failing. We found > that any node that was a contact point was connecting, but the other nodes > were never acting as coordinators. > > There are still issues in the driver, for which I have created JAVA-2967, > which also refers to JAVA-2638, but the system.peers and system.peers_v2 > tables should both contain native_transport_port and > native_transport_port_ssl. > > -- 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-16999) system.peers and system.peers_v2 do not contain the native_transport and/or native_transport_port_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706907#comment-17706907 ] Brandon Williams edited comment on CASSANDRA-16999 at 3/30/23 2:12 PM: --- In the current state, via the system table we expose "native_address" and "native_port" to clients. In the yaml config we have "rpc_address" and "native_transport_port" and "native_transport_port_ssl". It would seem from the server perspective all we are really missing is exposing "native_port_ssl" to clients? As far as I can tell "native_transport_port" has always only been a yaml option and not exposed to drivers, and "native_transport_address" has never existed. If we want to rename "rpc_address" to "native_transport_address" that is probably worth its own ticket, but for this one the most consistent thing seems to be adding "native_port_ssl" to me. was (Author: brandon.williams): In the current state, via the system table we expose "native_address" and "native_port" to clients. In the yaml config we have "rpc_address" and "native_transport_port" and "native_transport_port_ssl". It would seem from the server perspective all we are really missing is exposing "native_port_ssl" to clients? As far as I can tell "native_transport_address" and "native_transport_port" have always only been yaml options and not exposed to drivers, and renaming these is problematic and I don't think buys us much. > system.peers and system.peers_v2 do not contain the native_transport and/or > native_transport_port_ssl > - > > Key: CASSANDRA-16999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16999 > Project: Cassandra > Issue Type: Bug > Components: Local/Other >Reporter: Steve Lacerda >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0.x, 5.x > > > system.peers_v2 includes a “native_port” but has no notion of > native_transport_port vs. native_transport_port_ssl. Given this limited > information, there’s no clear way for the driver to know that different ports > are being used for SSL vs. non-SSL or which of those two ports is identified > by “native_port”. > > The issue we ran into is that the java driver, since it has no notion of the > transport port SSL, the driver was only using the contact points and was not > load balancing. > > The customer had both set: > native_transport_port: 9042 > native_transport_port_ssl: 9142 > > They were attempting to connect to 9142, but that was failing. They could > only use 9042, and so their applications load balancing was failing. We found > that any node that was a contact point was connecting, but the other nodes > were never acting as coordinators. > > There are still issues in the driver, for which I have created JAVA-2967, > which also refers to JAVA-2638, but the system.peers and system.peers_v2 > tables should both contain native_transport_port and > native_transport_port_ssl. > > -- 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-16999) system.peers and system.peers_v2 do not contain the native_transport and/or native_transport_port_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706907#comment-17706907 ] Brandon Williams commented on CASSANDRA-16999: -- In the current state, via the system table we expose "native_address" and "native_port" to clients. In the yaml config we have "rpc_address" and "native_transport_port" and "native_transport_port_ssl". It would seem from the server perspective all we are really missing is exposing "native_port_ssl" to clients? As far as I can tell "native_transport_address" and "native_transport_port" have always only been yaml options and not exposed to drivers, and renaming these is problematic and I don't think buys us much. > system.peers and system.peers_v2 do not contain the native_transport and/or > native_transport_port_ssl > - > > Key: CASSANDRA-16999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16999 > Project: Cassandra > Issue Type: Bug > Components: Local/Other >Reporter: Steve Lacerda >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0.x, 5.x > > > system.peers_v2 includes a “native_port” but has no notion of > native_transport_port vs. native_transport_port_ssl. Given this limited > information, there’s no clear way for the driver to know that different ports > are being used for SSL vs. non-SSL or which of those two ports is identified > by “native_port”. > > The issue we ran into is that the java driver, since it has no notion of the > transport port SSL, the driver was only using the contact points and was not > load balancing. > > The customer had both set: > native_transport_port: 9042 > native_transport_port_ssl: 9142 > > They were attempting to connect to 9142, but that was failing. They could > only use 9042, and so their applications load balancing was failing. We found > that any node that was a contact point was connecting, but the other nodes > were never acting as coordinators. > > There are still issues in the driver, for which I have created JAVA-2967, > which also refers to JAVA-2638, but the system.peers and system.peers_v2 > tables should both contain native_transport_port and > native_transport_port_ssl. > > -- 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-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706828#comment-17706828 ] Stefan Miklosovic commented on CASSANDRA-17797: --- I did another round of review. Thanks! > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 5.x > > Time Spent: 17h > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- 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-17797) All system properties and environment variables should be accessed via the new CassandraRelevantProperties and CassandraRelevantEnv classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17797: -- Status: Changes Suggested (was: Review In Progress) > All system properties and environment variables should be accessed via the > new CassandraRelevantProperties and CassandraRelevantEnv classes > --- > > Key: CASSANDRA-17797 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17797 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Low > Fix For: 5.x > > Time Spent: 17h > Remaining Estimate: 0h > > Follow up ticket for CASSANDRA-15876 - > "Always access system properties and environment variables via the new > CassandraRelevantProperties and CassandraRelevantEnv classes" > As part of that ticket we moved to the two new classes only > properties/variables that were currently listed in System Properties Virtual > Table. > We have to move to those classes the rest of the properties around the code > and start using those classes to access all of them. > +Additional information for newcomers:+ > You might want to start by getting acquainted with > CassandraRelevantProperties and CassandraRelevantEnv classes. Also, you might > want to check what changes were done and how the first batch was transferred > to this new framework as part of > [CASSANDRA-15876|https://github.com/apache/cassandra/commit/7694c1d191531ac152db55e83bc0db6864a5441e] > We are interested into the properties accessed currently through > getProperties around the code. > As part of CASSANDRA-15876 relevant unit tests were added > (CassandraRelevantPropertiesTest). To verify the new patch we need to ensure > that all tests Cassandra pass and also to think about potential update of the > mentioned test class. -- 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-18262) Switch checkstyle running only with JDK8 to be run with JDK11
[ https://issues.apache.org/jira/browse/CASSANDRA-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18262: - Source Control Link: https://github.com/apache/cassandra/commit/e98258a132d6d27c8431e6971693a224953fdd89 (was: https://github.com/apache/cassandra/commit/4e3447ae1727a0d01c9d81792acbdeeef94d86d2) Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed, thanks! > Switch checkstyle running only with JDK8 to be run with JDK11 > - > > Key: CASSANDRA-18262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18262 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently we run checkstyle, eclipse warnings (and probably anything else?) > only with JDK8. > In preparation to remove JDK8 we need to switch those to run with JDK11. -- 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-18262) Switch checkstyle running only with JDK8 to be run with JDK11
[ https://issues.apache.org/jira/browse/CASSANDRA-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18262: - Status: Ready to Commit (was: Review In Progress) > Switch checkstyle running only with JDK8 to be run with JDK11 > - > > Key: CASSANDRA-18262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18262 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently we run checkstyle, eclipse warnings (and probably anything else?) > only with JDK8. > In preparation to remove JDK8 we need to switch those to run with JDK11. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18262) Switch checkstyle running only with JDK8 to be run with JDK11
[ https://issues.apache.org/jira/browse/CASSANDRA-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-18262: Assignee: Maxim Muzafarov (was: Brandon Williams) > Switch checkstyle running only with JDK8 to be run with JDK11 > - > > Key: CASSANDRA-18262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18262 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently we run checkstyle, eclipse warnings (and probably anything else?) > only with JDK8. > In preparation to remove JDK8 we need to switch those to run with JDK11. -- 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-18262) Switch checkstyle running only with JDK8 to be run with JDK11
[ https://issues.apache.org/jira/browse/CASSANDRA-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18262: - Reviewers: Brandon Williams, Stefan Miklosovic (was: Ekaterina Dimitrova) Status: Review In Progress (was: Patch Available) > Switch checkstyle running only with JDK8 to be run with JDK11 > - > > Key: CASSANDRA-18262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18262 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently we run checkstyle, eclipse warnings (and probably anything else?) > only with JDK8. > In preparation to remove JDK8 we need to switch those to run with JDK11. -- 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-18262) Switch checkstyle running only with JDK8 to be run with JDK11
[ https://issues.apache.org/jira/browse/CASSANDRA-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18262: - Status: Patch Available (was: Open) > Switch checkstyle running only with JDK8 to be run with JDK11 > - > > Key: CASSANDRA-18262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18262 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently we run checkstyle, eclipse warnings (and probably anything else?) > only with JDK8. > In preparation to remove JDK8 we need to switch those to run with JDK11. -- 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: Upgrade checkstyle to 10.8.1 for j11 and 8.45.1 for j8
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 The following commit(s) were added to refs/heads/trunk by this push: new e98258a132 Upgrade checkstyle to 10.8.1 for j11 and 8.45.1 for j8 e98258a132 is described below commit e98258a132d6d27c8431e6971693a224953fdd89 Author: Maxim Muzafarov AuthorDate: Wed Mar 29 13:30:53 2023 +0200 Upgrade checkstyle to 10.8.1 for j11 and 8.45.1 for j8 Patch by Maxim Muzafarov; reviewed by brandonwilliams and smiklosovic for CASSANDRA-18262 --- .build/build-resolver.xml| 6 ++ .build/cassandra-build-deps-template.xml | 4 .build/parent-pom-template.xml | 6 -- CHANGES.txt | 1 + build.xml| 13 +++-- 5 files changed, 14 insertions(+), 16 deletions(-) diff --git a/.build/build-resolver.xml b/.build/build-resolver.xml index 60122b854f..e78bbf05e6 100644 --- a/.build/build-resolver.xml +++ b/.build/build-resolver.xml @@ -126,6 +126,12 @@ + + + + + + diff --git a/.build/cassandra-build-deps-template.xml b/.build/cassandra-build-deps-template.xml index 93387996ef..cbf2f8c59d 100644 --- a/.build/cassandra-build-deps-template.xml +++ b/.build/cassandra-build-deps-template.xml @@ -62,10 +62,6 @@ com.google.jimfs jimfs - - com.puppycrawl.tools - checkstyle - org.quicktheories quicktheories diff --git a/.build/parent-pom-template.xml b/.build/parent-pom-template.xml index 70f85d033e..35ed4047fb 100644 --- a/.build/parent-pom-template.xml +++ b/.build/parent-pom-template.xml @@ -497,12 +497,6 @@ 0.0.13 test - -com.puppycrawl.tools -checkstyle -8.40 -test - net.java.dev.jna jna diff --git a/CHANGES.txt b/CHANGES.txt index a2102acc56..e541b5c7b1 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 5.0 + * Use jdk-dependent checkstyle version to check the source code (CASSANDRA-18262) * Provide summary of failed SessionInfo's in StreamResultFuture (CASSANDRA-17199) * CEP-20: Dynamic Data Masking (CASSANDRA-17940) * Add system_views.snapshots virtual table (CASSANDRA-18102) diff --git a/build.xml b/build.xml index 197f720472..f75314e044 100644 --- a/build.xml +++ b/build.xml @@ -311,6 +311,9 @@ + + + + classpathref="checkstyle.classpath"/> - + @@ -1964,7 +1965,7 @@ - + - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16895) Build with Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706802#comment-17706802 ] Benedict Elliott Smith commented on CASSANDRA-16895: FWIW, I don't think we have agreed on a prohibition for supporting other versions, and I wouldn't have supported such a decision. I agree that our main targets are LTS, but making it easy to work with non-LTS versions for development at least would be helpful so long as relatively costless. In particular, the latest versions support virtual threads, which would be extremely useful for simulator performance and dramatically improve testing velocity of features like Accord and TCM. So, I strongly support [~slachiewicz]'s efforts. Since we will need to address these compilation errors eventually, I don't see why we would not address them eagerly. > Build with Java 17 > -- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Epic > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.x > > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup > *NOTE:* GC tuning, performance testing were never agreed to be part of this > ticket. > Below is a snapshot of current CI failures with JDK17, it will be updated on > a regular basis with a date of update > *March 19th 2023* > || ||Failing Test Classes||Ticket Numbers|| > | |_Python DTests_| | > |1|test_sjk|CASSANDRA-18343| > | |_Java Ditributed Tests_| | > |1-6|org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest - all > tests, > org.apache.cassandra.distributed.test.PrepareBatchStatementsTest - all tests, > org.apache.cassandra.distributed.test.IPMembershipTest - both tests, > org.apache.cassandra.distributed.test.MixedModeFuzzTest, > org.apache.cassandra.distributed.test.ReprepareFuzzTest, > org.apache.cassandra.distributed.test.ReprepareNewBehaviourTest|CASSANDRA-16304| > |7,8|org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest > - all tests > org.apache.cassandra.distributed.test.InternodeEncryptionOptionsTest - all > tests|Could be related to CASSANDRA-18180, to be checked | > |9|org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest - > 2 tests|CASSANDRA-18180| > | |_Unit Tests_| | > |1|org.apache.cassandra.repair.RepairJobTest - 1 test|CASSANDRA-17884| > |2|org.apache.cassandra.security.SSLFactoryTest - all tests|CASSANDRA-17992| > |3,4|org.apache.cassandra.db.memtable.MemtableSizeOffheapBuffersTest, > org.apache.cassandra.utils.concurrent.RefCountedTest|CASSANDRA-18329| > |5,6|org.apache.cassandra.cql3.validation.entities.UFJavaTest, > org.apache.cassandra.cql3.validation.entities.UFSecurityTest|CASSANDRA-18190| > | | | | > | | | | > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16895) Build with Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706798#comment-17706798 ] Benjamin Lerer commented on CASSANDRA-16895: [~slachiewicz] Thanks for the information. The plan is to target only LTS versions. We do not have the capacity to target other versions. Simply looking at the build for one Java version is not enough. We need to upgrade all our CI environment, dependencies, ... It is a significant work which is why this epic is taking so long. :-) > Build with Java 17 > -- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Epic > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.x > > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup > *NOTE:* GC tuning, performance testing were never agreed to be part of this > ticket. > Below is a snapshot of current CI failures with JDK17, it will be updated on > a regular basis with a date of update > *March 19th 2023* > || ||Failing Test Classes||Ticket Numbers|| > | |_Python DTests_| | > |1|test_sjk|CASSANDRA-18343| > | |_Java Ditributed Tests_| | > |1-6|org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest - all > tests, > org.apache.cassandra.distributed.test.PrepareBatchStatementsTest - all tests, > org.apache.cassandra.distributed.test.IPMembershipTest - both tests, > org.apache.cassandra.distributed.test.MixedModeFuzzTest, > org.apache.cassandra.distributed.test.ReprepareFuzzTest, > org.apache.cassandra.distributed.test.ReprepareNewBehaviourTest|CASSANDRA-16304| > |7,8|org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest > - all tests > org.apache.cassandra.distributed.test.InternodeEncryptionOptionsTest - all > tests|Could be related to CASSANDRA-18180, to be checked | > |9|org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest - > 2 tests|CASSANDRA-18180| > | |_Unit Tests_| | > |1|org.apache.cassandra.repair.RepairJobTest - 1 test|CASSANDRA-17884| > |2|org.apache.cassandra.security.SSLFactoryTest - all tests|CASSANDRA-17992| > |3,4|org.apache.cassandra.db.memtable.MemtableSizeOffheapBuffersTest, > org.apache.cassandra.utils.concurrent.RefCountedTest|CASSANDRA-18329| > |5,6|org.apache.cassandra.cql3.validation.entities.UFJavaTest, > org.apache.cassandra.cql3.validation.entities.UFSecurityTest|CASSANDRA-18190| > | | | | > | | | | > -- 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-18049) Update Chronicle Queue
[
https://issues.apache.org/jira/browse/CASSANDRA-18049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706782#comment-17706782
]
Michael Semb Wever commented on CASSANDRA-18049:
We're pulling in lots of pom dependencies during the resolve step
unnecessarily, some of these are not accessible and if you're for example
proxying the maven repo then it will fail.
The workaround is
{code}
mvn dependency:tree -f build/apache-cassandra-5.0-SNAPSHOT.pom
{code}
see the discussion here:
https://the-asf.slack.com/archives/CK23JSY2K/p1679596952611919
It's still unclear to me how to prevent the ant maven resolver from pulling
these poms when maven doesn't…
> Update Chronicle Queue
> --
>
> Key: CASSANDRA-18049
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18049
> Project: Cassandra
> Issue Type: Task
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.0
>
>
> According to [this|https://chronicle.software/chronicle-support-java-17]
> article:
> {code:java}
> Starting from chronicle-bom-2.22ea26, all new releases can be run under Java
> 17 when run on the class path (but not yet under the module path).{code}
> This BOM is newer than what we currently have in both 4.1 and trunk. 4.1
> points in comments to
> [https://mvnrepository.com/artifact/net.openhft/chronicle-bom/1.16.23] which
> I believe was just forgotten to be updated/removed. The versions we see
> correspond to this BOM
> [https://mvnrepository.com/artifact/net.openhft/chronicle-bom/2.20.226]
> It is still older than chronicle-bom-2.22ea26 so we need to upgrade. I
> suggest we also add a comment again which BOM is considered, this makes
> things easier.
> Further to running CI, review of the CHANGE logs needs to happen to ensure we
> do not miss anything that can impact us and it is not caught by our tests.
> For testing with JDK17, please, contact [~e.dimitrova] for latest branch and
> CI config (at this point feature branch in the cassandra repo does not exist)
>
--
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
