[cassandra-website] branch asf-staging updated (32a80afc -> 18612450)
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 32a80afc generate docs for 07cc189e new 18612450 generate docs for 07cc189e 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 (32a80afc) \ N -- N -- N refs/heads/asf-staging (18612450) 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 4740078 -> 4740078 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17729) Raise test timeouts
[ https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563574#comment-17563574 ] Berenguer Blasi commented on CASSANDRA-17729: - Through all the reviews and tests fixes I have done all this time there are plenty that will only repro on circle or only on jenkins, yes. And I think that is shared pov if you ask at least in my team. It is common for me to be involved in tickets that only repro on jenkins. In fact the jenkins run in this ticket is showing a few that don't show on the matching circle run. How this would relate to a 'properly' provisioned cluster, which we would have to define, I can't tell. I see your point right, bc there are some snakes in the grass, but If they are only doing noise is sthg to discuss as in any dist environment you will have timeouts and resource contraints. But at the moment jenkins is our official CI so any bugs there need ironing iiuc. i.e CASSANDRA-17232 is sthg that comes up in jenkins a lot. On circle we only get it looping the test a1000 times and with difficulty. > Raise test timeouts > --- > > Key: CASSANDRA-17729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17729 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.1-beta > > > We have seen for some time now junits timeout frequently on jenkins. This is > probably down to it being a very loaded env. On circle we don't observe that > behavior probably bc it's not so loaded. > The question is whether it is time to raise timeouts as they might be hiding > legit failures. As en experiment I raised timeouts in a branch and ran > jenkins against it. What I see is that the last 4.1 run had 14 failures out > of which 12 were timeouts. Increasing timeouts reveals what looks to be 9 > legit failures where 2 are timeouts that probably need to be investigated. -- 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-17724) Remove commons-lang dependency during build runtime
[
https://issues.apache.org/jira/browse/CASSANDRA-17724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-17724:
--
Since Version: 4.1-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/a250126f0f277b43a18cb665ccd02a105271bc33
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed into 4.1 as
[a250126f|https://github.com/apache/cassandra/commit/a250126f0f277b43a18cb665ccd02a105271bc33]
and merged up into trunk.
> Remove commons-lang dependency during build runtime
> ---
>
> Key: CASSANDRA-17724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 4.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{commons-lang}} is not a runtime dependency and a
> {{java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils}}
> exception is encountered during startup when hitting the codepath in
> {{{}StartupClusterConnectivityChecker{}}}.
> This error is encountered very infrequently, but it has the potential of
> preventing the {{CassandraDaemon}} from starting up.
> Currently, the Cassandra project allows developers to import the
> {{org.apache.commons.lang.\*}} namespace. The Cassandra build process should
> fail when {{org.apache.commons.lang.\*}} namespace imports are added to the
> code. This will prevent anyone from adding a build runtime library that is
> not available during runtime.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (15bdf2e8e7 -> a250126f0f)
This is an automated email from the ASF dual-hosted git repository. ycai pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 15bdf2e8e7 Merge branch 'cassandra-4.0' into cassandra-4.1 add a250126f0f Remove commons-lang dependency during build runtime No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + build.xml| 1 + ide/nbproject/project.xml| 2 +- .../apache/cassandra/net/StartupClusterConnectivityChecker.java | 2 +- .../org/apache/cassandra/distributed/fuzz/InJvmSutBase.java | 9 + 5 files changed, 5 insertions(+), 10 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. ycai pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit ab0a9b5f5ca9b5189da2834698897961aac39e87 Merge: 5c7a47b384 a250126f0f Author: Yifan Cai AuthorDate: Wed Jul 6 17:41:16 2022 -0700 Merge branch 'cassandra-4.1' into trunk CHANGES.txt | 1 + build.xml| 1 + ide/nbproject/project.xml| 2 +- .../apache/cassandra/net/StartupClusterConnectivityChecker.java | 2 +- .../org/apache/cassandra/distributed/fuzz/InJvmSutBase.java | 9 + 5 files changed, 5 insertions(+), 10 deletions(-) diff --cc CHANGES.txt index f1030a90e6,37b32930ed..4e1d688467 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,20 -1,5 +1,21 @@@ -4.1-alpha2 +4.2 + * Allow sstableloader to specify table without relying on path (CASSANDRA-16584) + * Fix TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address (CASSANDRA-17700) + * Add ByteComparable API (CASSANDRA-6936) + * Add guardrail for maximum replication factor (CASSANDRA-17500) + * Increment CQLSH to version 6.2.0 for release 4.2 (CASSANDRA-17646) + * Adding support to perform certificate based internode authentication (CASSANDRA-17661) + * Option to disable CDC writes of repaired data (CASSANDRA-17666) + * When a node is bootstrapping it gets the whole gossip state but applies in random order causing some cases where StorageService will fail causing an instance to not show up in TokenMetadata (CASSANDRA-17676) + * Add CQLSH command SHOW REPLICAS (CASSANDRA-17577) + * Add guardrail to allow disabling of SimpleStrategy (CASSANDRA-17647) + * Change default directory permission to 750 in packaging (CASSANDRA-17470) + * Adding support for TLS client authentication for internode communication (CASSANDRA-17513) + * Add new CQL function maxWritetime (CASSANDRA-17425) + * Add guardrail for ALTER TABLE ADD / DROP / REMOVE column operations (CASSANDRA-17495) + * Rename DisableFlag class to EnableFlag on guardrails (CASSANDRA-17544) +Merged from 4.1: + * Remove commons-lang dependency during build runtime (CASSANDRA-17724) * Relax synchronization on StreamSession#onError() to avoid deadlock (CASSANDRA-17706) * Fix AbstractCell#toString throws MarshalException for cell in collection (CASSANDRA-17695) * Add new vtable output option to compactionstats (CASSANDRA-17683) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (5c7a47b384 -> ab0a9b5f5c)
This is an automated email from the ASF dual-hosted git repository. ycai pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 5c7a47b384 Merge branch 'cassandra-4.1' into trunk add a250126f0f Remove commons-lang dependency during build runtime new ab0a9b5f5c Merge branch 'cassandra-4.1' into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt | 1 + build.xml| 1 + ide/nbproject/project.xml| 2 +- .../apache/cassandra/net/StartupClusterConnectivityChecker.java | 2 +- .../org/apache/cassandra/distributed/fuzz/InJvmSutBase.java | 9 + 5 files changed, 5 insertions(+), 10 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17724) Remove commons-lang dependency during build runtime
[
https://issues.apache.org/jira/browse/CASSANDRA-17724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-17724:
--
Reviewers: Dinesh Joshi, Yifan Cai (was: Yifan Cai)
> Remove commons-lang dependency during build runtime
> ---
>
> Key: CASSANDRA-17724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 4.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{commons-lang}} is not a runtime dependency and a
> {{java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils}}
> exception is encountered during startup when hitting the codepath in
> {{{}StartupClusterConnectivityChecker{}}}.
> This error is encountered very infrequently, but it has the potential of
> preventing the {{CassandraDaemon}} from starting up.
> Currently, the Cassandra project allows developers to import the
> {{org.apache.commons.lang.\*}} namespace. The Cassandra build process should
> fail when {{org.apache.commons.lang.\*}} namespace imports are added to the
> code. This will prevent anyone from adding a build runtime library that is
> not available during runtime.
--
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-17724) Remove commons-lang dependency during build runtime
[
https://issues.apache.org/jira/browse/CASSANDRA-17724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Joshi updated CASSANDRA-17724:
-
Mentor: Yifan Cai
Status: Ready to Commit (was: Review In Progress)
> Remove commons-lang dependency during build runtime
> ---
>
> Key: CASSANDRA-17724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 4.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{commons-lang}} is not a runtime dependency and a
> {{java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils}}
> exception is encountered during startup when hitting the codepath in
> {{{}StartupClusterConnectivityChecker{}}}.
> This error is encountered very infrequently, but it has the potential of
> preventing the {{CassandraDaemon}} from starting up.
> Currently, the Cassandra project allows developers to import the
> {{org.apache.commons.lang.\*}} namespace. The Cassandra build process should
> fail when {{org.apache.commons.lang.\*}} namespace imports are added to the
> code. This will prevent anyone from adding a build runtime library that is
> not available during runtime.
--
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-17724) Remove commons-lang dependency during build runtime
[
https://issues.apache.org/jira/browse/CASSANDRA-17724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563425#comment-17563425
]
Dinesh Joshi commented on CASSANDRA-17724:
--
+1 LGTM. thank you for the patch.
> Remove commons-lang dependency during build runtime
> ---
>
> Key: CASSANDRA-17724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17724
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 4.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{commons-lang}} is not a runtime dependency and a
> {{java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils}}
> exception is encountered during startup when hitting the codepath in
> {{{}StartupClusterConnectivityChecker{}}}.
> This error is encountered very infrequently, but it has the potential of
> preventing the {{CassandraDaemon}} from starting up.
> Currently, the Cassandra project allows developers to import the
> {{org.apache.commons.lang.\*}} namespace. The Cassandra build process should
> fail when {{org.apache.commons.lang.\*}} namespace imports are added to the
> code. This will prevent anyone from adding a build runtime library that is
> not available during runtime.
--
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-17741) WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17741: - Status: Patch Available (was: Open) https://github.com/apache/cassandra-website/pull/151 > WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization" > -- > > Key: CASSANDRA-17741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17741 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.1.x > > > This ticket is to capture the work associated with publishing the June 2022 > blog "Apache Cassandra 4.1: Configuration Standardization" > If this blog cannot be published by the *July 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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-17741) WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-17741: --- Labels: pull-request-available (was: ) > WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization" > -- > > Key: CASSANDRA-17741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17741 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.1.x > > > This ticket is to capture the work associated with publishing the June 2022 > blog "Apache Cassandra 4.1: Configuration Standardization" > If this blog cannot be published by the *July 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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-17741) WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17741: - Status: Open (was: Triage Needed) > WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization" > -- > > Key: CASSANDRA-17741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17741 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Fix For: 4.1.x > > > This ticket is to capture the work associated with publishing the June 2022 > blog "Apache Cassandra 4.1: Configuration Standardization" > If this blog cannot be published by the *July 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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-17741) WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563411#comment-17563411 ] Diogenese Topper commented on CASSANDRA-17741: -- Text reviewed, translated to .adoc format - need someone for final check in staging and commit. > WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization" > -- > > Key: CASSANDRA-17741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17741 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Fix For: 4.1.x > > > This ticket is to capture the work associated with publishing the June 2022 > blog "Apache Cassandra 4.1: Configuration Standardization" > If this blog cannot be published by the *July 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] (CASSANDRA-17741) WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17741 ] Diogenese Topper deleted comment on CASSANDRA-17741: -- was (Author: diotopper): * Add blog post titled "Apache Cassandra 4.1: Configuration Standardization" * Modify blog index page * Add image for blog: "apache-cassandra-4.1-configuration-standardization-unsplash-cookie-the-pom.jpg" > WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization" > -- > > Key: CASSANDRA-17741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17741 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Fix For: 4.1.x > > > This ticket is to capture the work associated with publishing the June 2022 > blog "Apache Cassandra 4.1: Configuration Standardization" > If this blog cannot be published by the *July 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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-17741) WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17741: - Test and Documentation Plan: * Add blog post titled "Apache Cassandra 4.1: Configuration Standardization" * Modify blog index page * Add image for blog: "apache-cassandra-4.1-configuration-standardization-unsplash-cookie-the-pom.jpg" > WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization" > -- > > Key: CASSANDRA-17741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17741 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Fix For: 4.1.x > > > This ticket is to capture the work associated with publishing the June 2022 > blog "Apache Cassandra 4.1: Configuration Standardization" > If this blog cannot be published by the *July 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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-17741) WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17741: - Authors: Chris Thornett, Diogenese Topper, Ekaterina Dimitrova Change Category: Semantic Complexity: Normal Fix Version/s: 4.1.x * Add blog post titled "Apache Cassandra 4.1: Configuration Standardization" * Modify blog index page * Add image for blog: "apache-cassandra-4.1-configuration-standardization-unsplash-cookie-the-pom.jpg" > WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization" > -- > > Key: CASSANDRA-17741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17741 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Fix For: 4.1.x > > > This ticket is to capture the work associated with publishing the June 2022 > blog "Apache Cassandra 4.1: Configuration Standardization" > If this blog cannot be published by the *July 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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-17636) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeFrom3ReplicationTest.testSimpleStrategy
[ https://issues.apache.org/jira/browse/CASSANDRA-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563395#comment-17563395 ] Josh McKenzie edited comment on CASSANDRA-17636 at 7/6/22 6:51 PM: --- [ASF CI Results] Branch: 4.1, build number: 85 butler url: [https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1] jenkins url: [https://ci-cassandra.apache.org/job/Cassandra-4.1/85/] JIRA: CASSANDRA-17636 commit url: [https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=008bf8607c55926d0aadb4602a8a854d396c7657] affected paths: * test/distributed/org/apache/cassandra/distributed/action/GossipHelper.java * test/distributed/org/apache/cassandra/distributed/impl/AbstractCluster.java * test/distributed/org/apache/cassandra/distributed/impl/Instance.java Build Result: UNSTABLE Passing Tests: 47953 Failing Tests: 14 ||Test|Failures|JIRA| |dtest-novnode.transient_replication_test.TestTransientReplication.test_transient_write|1 of 82|CASSANDRA-16061?| |dtest-novnode.transient_replication_ring_test.TestTransientReplicationRing.test_bootstrap_and_cleanup|1 of 82|CASSANDRA-16061?| |org.apache.cassandra.cql3.validation.entities.TupleTypeTest.testNestedTuple|13 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |dtest-novnode.replica_side_filtering_test.TestAllowFiltering.test_range_deletion_on_wide_table|1 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation|22 of 82|CASSANDRA-17461?| |org.apache.cassandra.cql3.validation.operations.SelectTest.testAllowFilteringOnPartitionKey|3 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.audit.AuditLoggerTest.testCqlKeyspaceAuditing|1 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.tools.TopPartitionsTest.testServiceTopPartitionsSingleTable-compression|9 of 82|CASSANDRA-17649?| |dtest-novnode.repair_tests.repair_test.TestRepair.test_parent_repair_session_cleanup|1 of 82|[Multiple JIRAs found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22*TestRepair*%22]| |org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testCompletedFlag|6 of 82|CASSANDRA-17542?| |dtest-novnode.user_types_test.TestUserTypes.test_type_keyspace_permission_isolation|1 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |junit.framework.TestSuite.org.apache.cassandra.distributed.test.CASMultiDCTest|8 of 82|[Multiple JIRAs found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22*test*%22]| |org.apache.cassandra.cql3.ViewComplexTTLTest.testUpdateColumnInViewPKWithTTLWithFlush[3]|20 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testSelectOnMultiIndexOnCollectionsWithNull|12 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| was (Author: jmckenzie): [CI Results] Branch: 4.1, build number: 85 butler url: https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1 jenkins url: https://ci-cassandra.apache.org/job/Cassandra-4.1/85/ JIRA: CASSANDRA-17636 commit url: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=008bf8607c55926d0aadb4602a8a854d396c7657 affected paths: * test/distributed/org/apache/cassandra/distributed/action/GossipHelper.java * test/distributed/org/apache/cassandra/distributed/impl/AbstractCluster.java * test/distributed/org/apache/cassandra/distributed/impl/Instance.java Build Result: UNSTABLE Passing Tests: 47953 Failing Tests: 14 ||Test|Failures|JIRA|| |dtest-novnode.transient_replication_test.TestTransientReplication.test_transient_write|1 of 82|[CASSANDRA-16061?|https://issues.apache.org/jira/browse/CASSANDRA-16061]| |dtest-novnode.transient_replication_ring_test.TestTransientReplicationRing.test_bootstrap_and_cleanup|1 of 82|[CASSANDRA-16061?|https://issues.apache.org/jira/browse/CASSANDRA-16061]| |org.apache.cassandra.cql3.validation.entities.TupleTypeTest.testNestedTuple|13 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |dtest-novnode.replica_side_filtering_test.TestAllowFiltering.test_range_deletion_on_wide_table|1 of 82|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation|22 of
[jira] [Commented] (CASSANDRA-17636) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeFrom3ReplicationTest.testSimpleStrategy
[
https://issues.apache.org/jira/browse/CASSANDRA-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563395#comment-17563395
]
Josh McKenzie commented on CASSANDRA-17636:
---
[CI Results]
Branch: 4.1, build number: 85
butler url:
https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1
jenkins url: https://ci-cassandra.apache.org/job/Cassandra-4.1/85/
JIRA: CASSANDRA-17636
commit url:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=008bf8607c55926d0aadb4602a8a854d396c7657
affected paths:
* test/distributed/org/apache/cassandra/distributed/action/GossipHelper.java
* test/distributed/org/apache/cassandra/distributed/impl/AbstractCluster.java
* test/distributed/org/apache/cassandra/distributed/impl/Instance.java
Build Result: UNSTABLE
Passing Tests: 47953
Failing Tests: 14
||Test|Failures|JIRA||
|dtest-novnode.transient_replication_test.TestTransientReplication.test_transient_write|1
of 82|[CASSANDRA-16061?|https://issues.apache.org/jira/browse/CASSANDRA-16061]|
|dtest-novnode.transient_replication_ring_test.TestTransientReplicationRing.test_bootstrap_and_cleanup|1
of 82|[CASSANDRA-16061?|https://issues.apache.org/jira/browse/CASSANDRA-16061]|
|org.apache.cassandra.cql3.validation.entities.TupleTypeTest.testNestedTuple|13
of 82|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|dtest-novnode.replica_side_filtering_test.TestAllowFiltering.test_range_deletion_on_wide_table|1
of 82|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation|22
of 82|[CASSANDRA-17461?|https://issues.apache.org/jira/browse/CASSANDRA-17461]|
|org.apache.cassandra.cql3.validation.operations.SelectTest.testAllowFilteringOnPartitionKey|3
of 82|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.audit.AuditLoggerTest.testCqlKeyspaceAuditing|1 of 82|[No
JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.tools.TopPartitionsTest.testServiceTopPartitionsSingleTable-compression|9
of 82|[CASSANDRA-17649?|https://issues.apache.org/jira/browse/CASSANDRA-17649]|
|dtest-novnode.repair_tests.repair_test.TestRepair.test_parent_repair_session_cleanup|1
of 82|[Multiple JIRAs
found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20"*TestRepair*;]
|org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testCompletedFlag|6
of 82|[CASSANDRA-17542?|https://issues.apache.org/jira/browse/CASSANDRA-17542]|
|dtest-novnode.user_types_test.TestUserTypes.test_type_keyspace_permission_isolation|1
of 82|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|junit.framework.TestSuite.org.apache.cassandra.distributed.test.CASMultiDCTest|8
of 82|[Multiple JIRAs
found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20"*test*;]
|org.apache.cassandra.cql3.ViewComplexTTLTest.testUpdateColumnInViewPKWithTTLWithFlush[3]|20
of 82|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testSelectOnMultiIndexOnCollectionsWithNull|12
of 82|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeFrom3ReplicationTest.testSimpleStrategy
> ---
>
> Key: CASSANDRA-17636
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17636
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The upgrade in-JVM dtest
> {{org.apache.cassandra.distributed.upgrade.MixedModeFrom3ReplicationTest.testSimpleStrategy}}
> is flaky on 4.1 and trunk.
> Jenkins failure:
> https://ci-cassandra.apache.org/job/Cassandra-4.1/21/testReport/org.apache.cassandra.distributed.upgrade/MixedModeFrom3UnloggedBatchTest/testSimpleStrategy/
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1149/testReport/org.apache.cassandra.distributed.upgrade/MixedModeFrom3ReplicationTest/testSimpleStrategy_2/
> Circle failure:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1564/workflows/e8dbd50a-d574-4ef8-a741-795a93cd3e85/jobs/16725
> Error Message:
> {code}
> Uncaught exceptions were
[jira] [Commented] (CASSANDRA-17695) Fix AbstractCell#toString throws MarshalException for cell in collection
[ https://issues.apache.org/jira/browse/CASSANDRA-17695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563394#comment-17563394 ] Josh McKenzie commented on CASSANDRA-17695: --- [ASF CI Results] Branch: 4.1, build number: 84 butler url: [https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1] jenkins url: [https://ci-cassandra.apache.org/job/Cassandra-4.1/84/] JIRA: CASSANDRA-17695 commit url: [https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=a9725b681b948f2122f3d48b96a5c4e7403d2c39] affected paths: * src/java/org/apache/cassandra/db/rows/AbstractCell.java * CHANGES.txt * test/unit/org/apache/cassandra/db/CellTest.java Build Result: UNSTABLE Passing Tests: 48211 Failing Tests: 26 ||Test|Failures|JIRA| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testSelectOnMultiIndexOnCollectionsWithNull|11 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability|13 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |dtest-offheap.auth_test.TestAuth.test_system_auth_ks_is_alterable|3 of 81|[Multiple JIRAs found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22*TestAuth*%22]| |org.apache.cassandra.cql3.validation.operations.SelectTest.containsFilteringForClusteringKeys|2 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |dtest.repair_tests.incremental_repair_test.TestIncRepair.test_multiple_repair|4 of 81|CASSANDRA-11268?| |org.apache.cassandra.net.ProxyHandlerConnectionsTest.suddenDisconnect-compression|3 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestUpgrade_current_3_0_x_To_indev_4_1_x.test_bootstrap|1 of 81|[Multiple JIRAs found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22*TestUpgrade*%22]| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testIndexOnRegularColumnInsertExpiringColumnWithFlush|9 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.cql3.validation.entities.TupleTypeTest.testNestedTuple|12 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.distributed.test.SchemaTest.readRepair|21 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |dtest.rebuild_test.TestRebuild.test_resumable_rebuild|1 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testIndexesOnNonStaticColumnsWhereSchemaIncludesStaticColumns|2 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.net.ConnectionTest.testTimeout-cdc|1 of 81|CASSANDRA-16677?| |org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation|21 of 81|CASSANDRA-17461?| |org.apache.cassandra.distributed.upgrade.CompactStoragePagingTest.testPagingWithCompactStorage|7 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.distributed.test.RepairErrorsTest.testRemoteStreamFailure|3 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.cql3.ViewComplexTTLTest.testUpdateColumnInViewPKWithTTLWithFlush[3]|19 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.utils.concurrent.SemaphoreTest.testUnfair|1 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.net.ProxyHandlerConnectionsTest.testExpireSome-compression|7 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.distributed.test.SchemaTest.readRepairWithCompaction|23 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.cql3.ViewComplexLivenessTest.testUnselectedColumnWithExpiredLivenessInfoWithoutFlush[3]|1 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| |org.apache.cassandra.cql3.ViewComplexTTLTest.terminated successfully|5 of 81|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]| > Fix AbstractCell#toString throws MarshalException for cell in collection >
[jira] [Created] (CASSANDRA-17741) WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization"
Diogenese Topper created CASSANDRA-17741: Summary: WEBSITE - July 2022 blog "Apache Cassandra 4.1: Configuration Standardization" Key: CASSANDRA-17741 URL: https://issues.apache.org/jira/browse/CASSANDRA-17741 Project: Cassandra Issue Type: Task Components: Documentation/Blog Reporter: Diogenese Topper This ticket is to capture the work associated with publishing the June 2022 blog "Apache Cassandra 4.1: Configuration Standardization" If this blog cannot be published by the *July 7, 2022 publish date*, please contact me, suggest changes, or correct the date when possible in the pull request for the appropriate time that the blog will go live (on both the blog.adoc and the blog post's file). -- 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-17683) Address CASSANDRA-16844 and CASSANDRA-16976 breaking compatibility
[ https://issues.apache.org/jira/browse/CASSANDRA-17683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563393#comment-17563393 ] Josh McKenzie commented on CASSANDRA-17683: --- [CI Results] Branch: 4.1, build number: 83 butler url: https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1 jenkins url: https://ci-cassandra.apache.org/job/Cassandra-4.1/83/ JIRA: CASSANDRA-17683 commit url: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=b75d56fd387a3af2706f75c0536cf112fdf6b788 affected paths: * src/java/org/apache/cassandra/tools/nodetool/CompactionStats.java * NEWS.txt * CHANGES.txt * test/unit/org/apache/cassandra/tools/nodetool/CompactionStatsTest.java Build Result: UNSTABLE Passing Tests: 47696 Failing Tests: 13 ||Test|Failures|JIRA|| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testIndexOnNonFrozenCollectionOfFrozenUDT|4 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.ViewTest.terminated successfully|1 of 80|[Multiple JIRAs found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20"*ViewTest*;] |org.apache.cassandra.cql3.ViewFilteringClustering1Test.testClusteringKeySliceRestrictions[3]|13 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.net.ConnectionTest.testTimeout|2 of 80|[CASSANDRA-16677?|https://issues.apache.org/jira/browse/CASSANDRA-16677]| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testWriteOnlyIndex|7 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.distributed.test.SchemaTest.readRepair|20 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.hints.HintsServiceTest.testPageSeek|2 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.validation.entities.TupleTypeTest.testNestedTuple|11 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.ViewComplexTTLTest.testUpdateColumnInViewPKWithTTLWithFlush[3]|18 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testSelectOnMultiIndexOnCollectionsWithNull|10 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.droppingIndexInvalidatesPreparedStatements|4 of 80|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] > Address CASSANDRA-16844 and CASSANDRA-16976 breaking compatibility > -- > > Key: CASSANDRA-17683 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17683 > Project: Cassandra > Issue Type: Bug > Components: Tool/nodetool >Reporter: David Capwell >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.1-beta, 4.1 > > > Compactionstats changed the output format, which causes a breaking change in > a minor release; this goes against the projects guidelines for a minor > release and needs to be addressed before releasing 4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16899) Change select wording to be more inclusive
[ https://issues.apache.org/jira/browse/CASSANDRA-16899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16899: --- Status: In Progress (was: Patch Available) > Change select wording to be more inclusive > -- > > Key: CASSANDRA-16899 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16899 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Jeff Jirsa >Assignee: Jeff Jirsa >Priority: Normal > > The conscious language checker has flagged a few thousand places where we are > using words that may be insensitive or undesirable. > https://clc.diversity.apache.org/analysis.html?project=cassandra.git > This ticket will address the non-code comment text as a first pass. -- 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-17740) BulkLoader tool initializes schema unnecessarily via streaming
[
https://issues.apache.org/jira/browse/CASSANDRA-17740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-17740:
Reviewers: Caleb Rackliffe
> BulkLoader tool initializes schema unnecessarily via streaming
> --
>
> Key: CASSANDRA-17740
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17740
> Project: Cassandra
> Issue Type: Bug
>Reporter: Caleb Rackliffe
>Assignee: Jon Meredith
>Priority: Normal
>
> Changes to streaming setup code for CASSANDRA-17663 mean that {{BulkLoader}}
> initializes the schema/system keyspace, which is not what we want in a tool.
> Initialization is due to a call to {{SystemKeyspace.getPreferredIP}} from the
> {{BulkLoader}} when it starts to transmit the SSTables from the bulk loader
> to the Cassandra instance.
> {{noformat}}
> getPreferredIP:1063, SystemKeyspace (org.apache.cassandra.db)
> sendMessage:213, StreamingMultiplexedChannel
> (org.apache.cassandra.streaming.async)
> sendControlMessage:191, StreamingMultiplexedChannel
> (org.apache.cassandra.streaming.async)
> sendControlMessage:1033, StreamSession (org.apache.cassandra.streaming)
> startStreamingFiles:1257, StreamSession (org.apache.cassandra.streaming)
> prepareSynAck:802, StreamSession (org.apache.cassandra.streaming)
> messageReceived:622, StreamSession (org.apache.cassandra.streaming)
> run:76, StreamDeserializingTask (org.apache.cassandra.streaming)
> run:30, FastThreadLocalRunnable (io.netty.util.concurrent)
> run:748, Thread (java.lang)
> {{noformat}}
> The existing {{BulkLoaderTest}} fails to detect this as it doesn't actually
> connect to anything so does not initialize streaming.
> Affects 4.1 and trunk, and may affect 4.0, although the 4.0 patch for
> CASSANDRA-17663 is different than 4.1+, and may require different mitigation.
--
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-17740) BulkLoader tool initializes schema unnecessarily via streaming
Caleb Rackliffe created CASSANDRA-17740:
---
Summary: BulkLoader tool initializes schema unnecessarily via
streaming
Key: CASSANDRA-17740
URL: https://issues.apache.org/jira/browse/CASSANDRA-17740
Project: Cassandra
Issue Type: Bug
Reporter: Caleb Rackliffe
Assignee: Jon Meredith
Changes to streaming setup code for CASSANDRA-17663 mean that {{BulkLoader}}
initializes the schema/system keyspace, which is not what we want in a tool.
Initialization is due to a call to {{SystemKeyspace.getPreferredIP}} from the
{{BulkLoader}} when it starts to transmit the SSTables from the bulk loader to
the Cassandra instance.
{{noformat}}
getPreferredIP:1063, SystemKeyspace (org.apache.cassandra.db)
sendMessage:213, StreamingMultiplexedChannel
(org.apache.cassandra.streaming.async)
sendControlMessage:191, StreamingMultiplexedChannel
(org.apache.cassandra.streaming.async)
sendControlMessage:1033, StreamSession (org.apache.cassandra.streaming)
startStreamingFiles:1257, StreamSession (org.apache.cassandra.streaming)
prepareSynAck:802, StreamSession (org.apache.cassandra.streaming)
messageReceived:622, StreamSession (org.apache.cassandra.streaming)
run:76, StreamDeserializingTask (org.apache.cassandra.streaming)
run:30, FastThreadLocalRunnable (io.netty.util.concurrent)
run:748, Thread (java.lang)
{{noformat}}
The existing {{BulkLoaderTest}} fails to detect this as it doesn't actually
connect to anything so does not initialize streaming.
Affects 4.1 and trunk, and may affect 4.0, although the 4.0 patch for
CASSANDRA-17663 is different than 4.1+, and may require different mitigation.
--
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-17733) min_tracked_partition_size_bytes should not have the suffix prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova reassigned CASSANDRA-17733: --- Assignee: Ekaterina Dimitrova > min_tracked_partition_size_bytes should not have the suffix prefix > -- > > Key: CASSANDRA-17733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17733 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.x > > > min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have > not been added with the unit suffix anymore as confirmed on the commit. > It is also confusing now when users can add unit of their choice. > We have two options: > * keep it with annotation and add also version without the suffix > * rename it as we are still alpha and API changes can be done for bug > fixing. Not sure whether we need an approval on the ML for this one. > CC [~ycai] , [~marcuse] and [~dcapwell] -- 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-17587) Flaky compaction_test.py::TestCompaction:: test_user_defined_compaction
[
https://issues.apache.org/jira/browse/CASSANDRA-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563320#comment-17563320
]
Josh McKenzie commented on CASSANDRA-17587:
---
[ASF CI Results]
Branch: 4.1, build number: 82
butler url:
[https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1]
jenkins url: [https://ci-cassandra.apache.org/job/Cassandra-4.1/82/]
JIRA: CASSANDRA-17587
commit url:
[https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=60b54425edc0a328bc1baf00c2e5bf111d4b9da8]
affected paths:
* src/java/org/apache/cassandra/db/memtable/Flushing.java
* src/java/org/apache/cassandra/db/memtable/AbstractMemtable.java
* src/java/org/apache/cassandra/db/ColumnFamilyStore.java
* src/java/org/apache/cassandra/db/memtable/AbstractMemtableWithCommitlog.java
* src/java/org/apache/cassandra/db/memtable/Memtable.java
* test/unit/org/apache/cassandra/db/commitlog/CommitLogCQLTest.java
* CHANGES.txt
Build Result: UNSTABLE
Passing Tests: 47199
Failing Tests: 19
||Test|Failures|JIRA|
|org.apache.cassandra.cql3.validation.operations.SelectTest.filteringWithOrderClause|6
of 79|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]|
|org.apache.cassandra.distributed.test.SchemaTest.readRepair|19 of 79|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]|
|dtest-novnode.bootstrap_test.TestBootstrap.test_simultaneous_bootstrap|2 of
79|[Multiple JIRAs
found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22*TestBootstrap*%22]|
|org.apache.cassandra.distributed.test.CASTest.testSucccessfulWriteDuringRangeMovementFollowedByRead|12
of 79|CASSANDRA-17461?|
|dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_3_11_X.test_parallel_upgrade_with_internode_ssl|2
of 79|CASSANDRA-17610?|
|org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation|20
of 79|CASSANDRA-17461?|
|dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD.test_rolling_upgrade_with_internode_ssl|5
of 79|CASSANDRA-17610?|
|org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect-compression|7
of 79|CASSANDRA-16677?|
|org.apache.cassandra.distributed.upgrade.CompactStorageImplicitNullInClusteringTest.testImplicitNullInClusteringWithCompactStorage|7
of 79|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]|
|org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect|7 of
79|CASSANDRA-16677?|
|org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testSelectOnMultiIndexOnCollectionsWithNull|9
of 79|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]|
|dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV4Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_parallel_upgrade_with_internode_ssl|5
of 79|CASSANDRA-17296?|
|org.apache.cassandra.cql3.validation.entities.TupleTypeTest.testReversedTypeTuple|6
of 79|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]|
|org.apache.cassandra.utils.memory.LongBufferPoolTest.testPoolAllocateWithRecyclePartially|7
of 79|CASSANDRA-16681?|
|org.apache.cassandra.cql3.ViewComplexTTLTest.testUpdateColumnInViewPKWithTTLWithFlush[3]|17
of 79|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]|
|junit.framework.TestSuite.org.apache.cassandra.metrics.ClientRequestMetricsTest|1
of 79|[Multiple JIRAs
found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22*metrics*%22]|
> Flaky compaction_test.py::TestCompaction:: test_user_defined_compaction
> ---
>
> Key: CASSANDRA-17587
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17587
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Branimir Lambov
>Priority: Normal
> Fix For: 4.1-beta, 4.1, 4.2
>
>
> As proved this test is flaky on trunk compaction_test.py::TestCompaction::
> test_user_defined_compaction:
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1575/workflows/f9409df6-825f-4996-976a-0182549d87dc/jobs/10405/tests]
> I haven't tested other branches, probably good to be tested by whoever
> assigns this ticket.
> {code:java}
> test teardown failure Unexpected error found in node logs (see stdout for
> full details). Errors: [ERROR [Native-Transport-Requests-53] 2022-04-29
> 16:54:33,003 StorageProxy.java:1631 - Failed to
[jira] [Commented] (CASSANDRA-17650) Check startup and setter validations for batch_size_fail_threshold
[ https://issues.apache.org/jira/browse/CASSANDRA-17650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563319#comment-17563319 ] Josh McKenzie commented on CASSANDRA-17650: --- [CI Results] Branch: 4.1, build number: 81 butler url: https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1 jenkins url: https://ci-cassandra.apache.org/job/Cassandra-4.1/81/ JIRA: CASSANDRA-17650 commit url: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=07e5876c43998fe7384df115c65749d668183130 affected paths: * src/java/org/apache/cassandra/config/DataStorageSpec.java * src/java/org/apache/cassandra/config/DatabaseDescriptor.java * test/unit/org/apache/cassandra/config/DatabaseDescriptorTest.java * CHANGES.txt * test/unit/org/apache/cassandra/tools/nodetool/SetGetColumnIndexSizeTest.java Build Result: UNSTABLE Passing Tests: 47003 Failing Tests: 25 ||Test|Failures|JIRA|| |org.apache.cassandra.distributed.test.SchemaTest.readRepairWithCompaction|22 of 78|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testIndexOnClusteringKeyInsertExpiringColumn|8 of 78|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.distributed.upgrade.CompactStorageImplicitNullInClusteringTest.testImplicitNullInClusteringWithCompactStorage|6 of 78|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |junit.framework.TestSuite.org.apache.cassandra.distributed.test.guardrails.GuardrailDiskUsageTest|1 of 78|[Multiple JIRAs found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20"*guardrails*;] |dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV4Upgrade_AllVersions_RandomPartitioner_EndsAt_Trunk_HEAD.test_parallel_upgrade_with_internode_ssl|5 of 78|[CASSANDRA-17296?|https://issues.apache.org/jira/browse/CASSANDRA-17296]| |dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV4Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_parallel_upgrade_with_internode_ssl|4 of 78|[CASSANDRA-17296?|https://issues.apache.org/jira/browse/CASSANDRA-17296]| |junit.framework.TestSuite.org.apache.cassandra.distributed.test.CASMultiDCTest|7 of 78|[Multiple JIRAs found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20"*test*;] |org.apache.cassandra.distributed.upgrade.BatchUpgradeTest.batchTest|24 of 78|[CASSANDRA-17651?|https://issues.apache.org/jira/browse/CASSANDRA-17651]| |org.apache.cassandra.tools.TopPartitionsTest.testServiceTopPartitionsSingleTable|10 of 78|[CASSANDRA-17649?|https://issues.apache.org/jira/browse/CASSANDRA-17649]| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testSelectOnMultiIndexOnCollectionsWithNull|8 of 78|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.tools.TopPartitionsTest.testServiceTopPartitionsSingleTable-cdc|7 of 78|[CASSANDRA-17649?|https://issues.apache.org/jira/browse/CASSANDRA-17649]| |org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect-compression|6 of 78|[CASSANDRA-16677?|https://issues.apache.org/jira/browse/CASSANDRA-16677]| |dtest-upgrade.upgrade_tests.drop_compact_storage_upgrade_test.TestDropCompactStorage.test_drop_compact_storage_mixed_cluster|10 of 78|[CASSANDRA-17634?|https://issues.apache.org/jira/browse/CASSANDRA-17634]| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testIndexOnRegularColumnInsertExpiringColumnWithFlush|8 of 78|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.ViewComplexTTLTest.testUpdateColumnInViewPKWithTTLWithFlush[3]|16 of 78|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation|19 of 78|[CASSANDRA-17461?|https://issues.apache.org/jira/browse/CASSANDRA-17461]| |org.apache.cassandra.distributed.test.CASTest.testSucccessfulWriteDuringRangeMovementFollowedByRead|11 of 78|[CASSANDRA-17461?|https://issues.apache.org/jira/browse/CASSANDRA-17461]| |org.apache.cassandra.distributed.test.CASTest.testIncompleteWriteFollowedBySuccessfulWriteWithStaleRingDuringRangeMovementFollowedByRead|4 of 78|[CASSANDRA-17461?|https://issues.apache.org/jira/browse/CASSANDRA-17461]| |org.apache.cassandra.distributed.test.CASTest.testSuccessfulWriteBeforeRangeMovement|8 of 78|[CASSANDRA-17461?|https://issues.apache.org/jira/browse/CASSANDRA-17461]| |org.apache.cassandra.cql3.validation.entities.TupleTypeTest.testReversedTypeTuple|5 of 78|[No JIRA
[jira] [Commented] (CASSANDRA-17715) nodetool clientstats - client_options to be exposed by adding a new flag
[ https://issues.apache.org/jira/browse/CASSANDRA-17715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563314#comment-17563314 ] Josh McKenzie commented on CASSANDRA-17715: --- [CI Results] Branch: 4.1, build number: 79 butler url: https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1 jenkins url: https://ci-cassandra.apache.org/job/Cassandra-4.1/79/ JIRA: CASSANDRA-17715 commit url: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=dcb4768345e0fe96420c4f4597e2eb822040d15a affected paths: * src/java/org/apache/cassandra/tools/nodetool/ClientStats.java * test/unit/org/apache/cassandra/tools/nodetool/ClientStatsTest.java * CHANGES.txt * NEWS.txt Build Result: UNSTABLE Passing Tests: 47334 Failing Tests: 19 ||Test|Failures|JIRA|| |org.apache.cassandra.net.ProxyHandlerConnectionsTest.testExpireSome-compression|5 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.distributed.test.RepairErrorsTest.testRemoteStreamFailure|2 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testSegmentFlaggingWithNonblockingOnCreation|5 of 76|[CASSANDRA-17542?|https://issues.apache.org/jira/browse/CASSANDRA-17542]| |org.apache.cassandra.cql3.validation.operations.SelectTest.testTokenFctRejectsInvalidColumnType|4 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.distributed.test.CASTest.testSuccessfulWriteBeforeRangeMovement|7 of 76|[CASSANDRA-17461?|https://issues.apache.org/jira/browse/CASSANDRA-17461]| |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testIndexesOnComplexPrimaryKey|8 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testRangeQuery|5 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect|5 of 76|[CASSANDRA-16677?|https://issues.apache.org/jira/browse/CASSANDRA-16677]| |org.apache.cassandra.distributed.upgrade.CompactStorageImplicitNullInClusteringTest.testImplicitNullInClusteringWithCompactStorage|4 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.distributed.upgrade.DropCompactStorageTest.testDropCompactStorage|1 of 76|[CASSANDRA-17674?|https://issues.apache.org/jira/browse/CASSANDRA-17674]| |org.apache.cassandra.cql3.ViewComplexTTLTest.testUpdateColumnInViewPKWithTTLWithFlush[3]|15 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testIndexOnClusteringKeyInsertExpiringColumn|6 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestUpgrade_current_3_0_x_To_indev_4_1_x.test_bootstrap_multidc|3 of 76|[Multiple JIRAs found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20"*TestUpgrade*;] |org.apache.cassandra.distributed.upgrade.CompactStoragePagingTest.testPagingWithCompactStorage|6 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.tools.TopPartitionsTest.testServiceTopPartitionsSingleTable|8 of 76|[CASSANDRA-17649?|https://issues.apache.org/jira/browse/CASSANDRA-17649]| |org.apache.cassandra.distributed.test.CASTest.testSuccessfulWriteDuringRangeMovementFollowedByConflicting|8 of 76|[CASSANDRA-17461?|https://issues.apache.org/jira/browse/CASSANDRA-17461]| |org.apache.cassandra.cql3.ViewFilteringClustering1Test.terminated successfully|4 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] |org.apache.cassandra.distributed.upgrade.CompactStorageHiddenColumnTest.testHiddenColumnWithCompactStorage|5 of 76|[No JIRA found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252] > nodetool clientstats - client_options to be exposed by adding a new flag > > > Key: CASSANDRA-17715 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17715 > Project: Cassandra > Issue Type: Bug > Components: Tool/nodetool >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.2 > > > client_options column (CASSANDRA-16378) should appear when using a new flag > (to be introduced)
[jira] [Commented] (CASSANDRA-17628) CQL writetime and ttl functions should be forbidden for multicell columns
[
https://issues.apache.org/jira/browse/CASSANDRA-17628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563311#comment-17563311
]
Josh McKenzie commented on CASSANDRA-17628:
---
[CI Results]
Branch: 4.1, build number: 78
butler url:
https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-4.1/Cassandra-4.1
jenkins url: https://ci-cassandra.apache.org/job/Cassandra-4.1/78/
JIRA: CASSANDRA-17628
commit url:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=09692d5a58d96089c699f59e9b7daacd066e902d
affected paths:
* CHANGES.txt
* doc/cql3/CQL.textile
* src/java/org/apache/cassandra/cql3/selection/Selectable.java
*
test/unit/org/apache/cassandra/cql3/validation/entities/WritetimeOrTTLTest.java
Build Result: UNSTABLE
Passing Tests: 47482
Failing Tests: 10
||Test|Failures|JIRA||
|org.apache.cassandra.db.compaction.SingleSSTableLCSTaskTest.uplevelDisabledTest|3
of 75|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV4Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_parallel_upgrade|3
of 75|[CASSANDRA-17296?|https://issues.apache.org/jira/browse/CASSANDRA-17296]|
|org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testWriteOnlyIndex|6
of 75|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.cql3.ViewComplexTTLTest.testUpdateColumnInViewPKWithTTLWithFlush[3]|14
of 75|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.distributed.upgrade.MixedModeFrom3UnloggedBatchTest.testSimpleStrategy|5
of 75|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation|18
of 75|[CASSANDRA-17461?|https://issues.apache.org/jira/browse/CASSANDRA-17461]|
|dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestUpgrade_current_3_0_x_To_indev_4_1_x.test_bootstrap_multidc|2
of 75|[Multiple JIRAs
found|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20"*TestUpgrade*;]
|org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testIndexOnCountersInvalid|3
of 75|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.cql3.validation.operations.SelectTest.filteringWithOrderClause|5
of 75|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
|org.apache.cassandra.cql3.validation.entities.SecondaryIndexTest.testCanQuerySecondaryIndex|6
of 75|[No JIRA
found|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252]
> CQL writetime and ttl functions should be forbidden for multicell columns
> -
>
> Key: CASSANDRA-17628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 3.0.28, 3.11.14, 4.0.5, 4.1-alpha, 4.2
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> CQL {{writetime}} and {{ttl}} functions are currently forbidden for
> collections, frozen or not. Also, they are always allowed for UDTs, frozen or
> not:
> {code}
> CREATE TYPE udt (a int, b int);
> CREATE TABLE t (k int PRIMARY KEY, s set, fs frozen>, t udt, ft
> frozen);
> SELECT writetime(s) FROM t; -- fails
> SELECT writetime(st) FROM t; -- fails
> SELECT writetime(t) FROM t; -- allowed
> SELECT writetime(ft) FROM t; -- allowed
> {code}
> This is done by checking in
> [{{Selectable.WritetimeOrTTL#newSelectorFactory}}|https://github.com/apache/cassandra/blob/cassandra-4.0.4/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L250]
> whether the column is a collection or not. However, I think that what we
> should check is whether the column is multi-cell. That way the function would
> work with frozen collections and UDTs, and it would reject unfrozen
> collections and UDTs:
> {code}
> SELECT writetime(s) FROM t; -- fails
> SELECT writetime(st) FROM t; -- allowed
> SELECT writetime(t) FROM t; -- fails
> SELECT writetime(ft) FROM t; -- allowed
> {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-15254) Allow UPDATE on settings virtual table to change running configurations
[ https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563308#comment-17563308 ] Ekaterina Dimitrova edited comment on CASSANDRA-15254 at 7/6/22 3:51 PM: - FYI - I opened and linked to this ticket CASSANDRA-17734. to validate that Config properties actually are always updated internally so that we see and update properly in Settings Virtual Table when this patch lands. I found examples where JMX updates properly Cassandra and shows the right value assigned internally but this is not assigned to the original Config class property and we just see and operate with the yaml property. In this case update to that one from Settings Table would have had zero effect internally. Example - *index_summary_resize_interval* was (Author: e.dimitrova): FYI - I opened and linked to this ticket CASSANDRA-17734. to validate that Config properties actually are always updated internally so that we see and update properly in Settings Virtual Table when this patch lands. I found examples where JMX updates properly Cassandra and shows the right value assigned internally but this is not assigned to the original Config class property and we just see and operate with the yaml property. In this case update to that one from Settings Table would have had zero effect internally. > Allow UPDATE on settings virtual table to change running configurations > --- > > Key: CASSANDRA-15254 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15254 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Virtual Tables >Reporter: Chris Lohfink >Assignee: Benjamin Lerer >Priority: Normal > > Allow using UPDATE on the system_views.settings virtual table to update > configs at runtime for the equivalent of the dispersed JMX > attributes/operations. -- 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-15254) Allow UPDATE on settings virtual table to change running configurations
[ https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563308#comment-17563308 ] Ekaterina Dimitrova commented on CASSANDRA-15254: - FYI - I opened and linked to this ticket CASSANDRA-17734. to validate that Config properties actually are always updated internally so that we see and update properly in Settings Virtual Table when this patch lands. I found examples where JMX updates properly Cassandra and shows the right value assigned internally but this is not assigned to the original Config class property and we just see and operate with the yaml property. In this case update to that one from Settings Table would have had zero effect internally. > Allow UPDATE on settings virtual table to change running configurations > --- > > Key: CASSANDRA-15254 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15254 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Virtual Tables >Reporter: Chris Lohfink >Assignee: Benjamin Lerer >Priority: Normal > > Allow using UPDATE on the system_views.settings virtual table to update > configs at runtime for the equivalent of the dispersed JMX > attributes/operations. -- 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-17739) Validate that JMX updates any old pre-4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage)
[ https://issues.apache.org/jira/browse/CASSANDRA-17739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17739: Status: Open (was: Triage Needed) > Validate that JMX updates any old pre-4.1 properties (which are not moved to > the new Config classes; non-duration, non-data rate, non-data storage) > --- > > Key: CASSANDRA-17739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17739 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.1.x, 4.x > > > Check that any properties which are added pre-4.1 (non-Duration, non-Data > Storage, non-Data Rate) are always updated by JMX and there are no > inconsistent validations that might cover bugs. Validate proper update in > Settings Virtual Table -- 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-17739) Validate that JMX updates any old pre-4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage)
[ https://issues.apache.org/jira/browse/CASSANDRA-17739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17739: Description: Check that any properties which are added pre-4.1 (non-Duration, non-Data Storage, non-Data Rate) are always updated by JMX and there are no inconsistent validations that might cover bugs. Validate proper update in Settings Virtual Table (was: Check that any properties which are added in 4.1 (non-Duration, non-Data Storage, non-Data Rate) are always updated by JMX and there are no inconsistent validations that might cover bugs. Validate proper update in Settings Virtual Table) > Validate that JMX updates any old pre-4.1 properties (which are not moved to > the new Config classes; non-duration, non-data rate, non-data storage) > --- > > Key: CASSANDRA-17739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17739 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.1.x, 4.x > > > Check that any properties which are added pre-4.1 (non-Duration, non-Data > Storage, non-Data Rate) are always updated by JMX and there are no > inconsistent validations that might cover bugs. Validate proper update in > Settings Virtual Table -- 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-17739) CLONE - Validate that JMX updates any old pre-4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage)
Ekaterina Dimitrova created CASSANDRA-17739: --- Summary: CLONE - Validate that JMX updates any old pre-4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage) Key: CASSANDRA-17739 URL: https://issues.apache.org/jira/browse/CASSANDRA-17739 Project: Cassandra Issue Type: Task Components: Local/Config Reporter: Ekaterina Dimitrova Fix For: 4.1-beta, 4.1.x, 4.x Check that any properties which are added in 4.1 (non-Duration, non-Data Storage, non-Data Rate) are always updated by JMX and there are no inconsistent validations that might cover bugs. Validate proper update in Settings Virtual Table -- 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-17739) Validate that JMX updates any old pre-4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage)
[ https://issues.apache.org/jira/browse/CASSANDRA-17739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17739: Summary: Validate that JMX updates any old pre-4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage) (was: CLONE - Validate that JMX updates any old pre-4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage)) > Validate that JMX updates any old pre-4.1 properties (which are not moved to > the new Config classes; non-duration, non-data rate, non-data storage) > --- > > Key: CASSANDRA-17739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17739 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.1.x, 4.x > > > Check that any properties which are added in 4.1 (non-Duration, non-Data > Storage, non-Data Rate) are always updated by JMX and there are no > inconsistent validations that might cover bugs. Validate proper update in > Settings Virtual Table -- 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-17738) Validate that JMX updates any new 4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage)
[ https://issues.apache.org/jira/browse/CASSANDRA-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17738: Fix Version/s: 4.1-beta 4.1.x 4.x > Validate that JMX updates any new 4.1 properties (which are not moved to the > new Config classes; non-duration, non-data rate, non-data storage) > --- > > Key: CASSANDRA-17738 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17738 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.1.x, 4.x > > > Check that any properties which are added in 4.1 (non-Duration, non-Data > Storage, non-Data Rate) are always updated by JMX and there are no > inconsistent validations that might cover bugs. Validate proper update in > Settings Virtual Table -- 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-17738) Validate that JMX updates any new 4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage)
[ https://issues.apache.org/jira/browse/CASSANDRA-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17738: Change Category: Operability Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Validate that JMX updates any new 4.1 properties (which are not moved to the > new Config classes; non-duration, non-data rate, non-data storage) > --- > > Key: CASSANDRA-17738 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17738 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > > Check that any properties which are added in 4.1 (non-Duration, non-Data > Storage, non-Data Rate) are always updated by JMX and there are no > inconsistent validations that might cover bugs. Validate proper update in > Settings Virtual Table -- 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-17738) Validate that JMX updates any new 4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage)
Ekaterina Dimitrova created CASSANDRA-17738: --- Summary: Validate that JMX updates any new 4.1 properties (which are not moved to the new Config classes; non-duration, non-data rate, non-data storage) Key: CASSANDRA-17738 URL: https://issues.apache.org/jira/browse/CASSANDRA-17738 Project: Cassandra Issue Type: Task Components: Local/Config Reporter: Ekaterina Dimitrova Check that any properties which are added in 4.1 (non-Duration, non-Data Storage, non-Data Rate) are always updated by JMX and there are no inconsistent validations that might cover bugs. Validate proper update in Settings Virtual Table -- 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-17729) Raise test timeouts
[
https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563298#comment-17563298
]
Josh McKenzie commented on CASSANDRA-17729:
---
{quote}I can't stop finding legit bugs on jenkins runs
{quote}
You're seeing bugs showing up in Jenkins that don't show in circle that users
could expect to see in a reasonably provisioned C* cluster?
> Raise test timeouts
> ---
>
> Key: CASSANDRA-17729
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17729
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1-beta
>
>
> We have seen for some time now junits timeout frequently on jenkins. This is
> probably down to it being a very loaded env. On circle we don't observe that
> behavior probably bc it's not so loaded.
> The question is whether it is time to raise timeouts as they might be hiding
> legit failures. As en experiment I raised timeouts in a branch and ran
> jenkins against it. What I see is that the last 4.1 run had 14 failures out
> of which 12 were timeouts. Increasing timeouts reveals what looks to be 9
> legit failures where 2 are timeouts that probably need to be investigated.
--
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-17737) Validate that JMX updates properly any properties that were moved to the new Config classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17737: Fix Version/s: 4.1.x 4.x > Validate that JMX updates properly any properties that were moved to the new > Config classes > --- > > Key: CASSANDRA-17737 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17737 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.1.x, 4.x > > > Check that any properties moved to the new types in 4.1 (Duration, Data > Storage, Data Rate) are always updated by JMX and there are no inconsistent > validations that might cover bugs. Validate proper update in Settings Virtual > Table -- 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-17737) Validate that JMX updates properly any properties that were moved to the new Config classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17737: Fix Version/s: 4.1-beta > Validate that JMX updates properly any properties that were moved to the new > Config classes > --- > > Key: CASSANDRA-17737 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17737 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta > > > Check that any properties moved to the new types in 4.1 (Duration, Data > Storage, Data Rate) are always updated by JMX and there are no inconsistent > validations that might cover bugs. Validate proper update in Settings Virtual > Table -- 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-17737) Validate that JMX updates properly any properties that were moved to the new Config classes
[ https://issues.apache.org/jira/browse/CASSANDRA-17737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17737: Change Category: Operability Complexity: Low Hanging Fruit Component/s: Local/Config Assignee: Ekaterina Dimitrova Status: Open (was: Triage Needed) > Validate that JMX updates properly any properties that were moved to the new > Config classes > --- > > Key: CASSANDRA-17737 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17737 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > Check that any properties moved to the new types in 4.1 (Duration, Data > Storage, Data Rate) are always updated by JMX and there are no inconsistent > validations that might cover bugs. Validate proper update in Settings Virtual > Table -- 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-17737) Validate that JMX updates properly any properties that were moved to the new Config classes
Ekaterina Dimitrova created CASSANDRA-17737: --- Summary: Validate that JMX updates properly any properties that were moved to the new Config classes Key: CASSANDRA-17737 URL: https://issues.apache.org/jira/browse/CASSANDRA-17737 Project: Cassandra Issue Type: Task Reporter: Ekaterina Dimitrova Check that any properties moved to the new types in 4.1 (Duration, Data Storage, Data Rate) are always updated by JMX and there are no inconsistent validations that might cover bugs. Validate proper update in Settings Virtual Table -- 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-17734) Validate that JMX and the Settings Virtual Table are aligned
[ https://issues.apache.org/jira/browse/CASSANDRA-17734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17734: Description: I discovered JMX methods that are not updating the Config parameters but directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ as users will see wrong values in the Settings virtual table which rely on the Config parameters (if some value was changed after startup). It will be explicitly important to ensure there is no disconnect between those when we add update option for the Virtual Table. This ticket is meant to serve as an umbrella for subtasks to check the properties getters methods and for tickets to fix any discovered bugs. CC [~b.le...@gmail.com] and [~dcapwell] was: I discovered JMX methods that are not updating the Config parameters but directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ as users will see wrong values in the Settings virtual table which rely on the Config parameters (if some value was changed after startup). It will be explicitly important to ensure there is no disconnect between those when we add update option for the Virtual Table. This ticket is meant to serve as an umbrella for subtasks to check the properties getters methods and for bug tickets for fixes. CC [~b.le...@gmail.com] and [~dcapwell] > Validate that JMX and the Settings Virtual Table are aligned > > > Key: CASSANDRA-17734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17734 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > I discovered JMX methods that are not updating the Config parameters but > directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ > as users will see wrong values in the Settings virtual table which rely on > the Config parameters (if some value was changed after startup). It will be > explicitly important to ensure there is no disconnect between those when we > add update option for the Virtual Table. > This ticket is meant to serve as an umbrella for subtasks to check the > properties getters methods and for tickets to fix any discovered > bugs. > > CC [~b.le...@gmail.com] and [~dcapwell] -- 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-17736) Settings Virtual Table should display the values assigned to a property in the DatabaseDescriptor on startup and not null (as per the yaml)
[ https://issues.apache.org/jira/browse/CASSANDRA-17736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17736: Fix Version/s: 4.0.x 4.1-beta 4.1.x > Settings Virtual Table should display the values assigned to a property in > the DatabaseDescriptor on startup and not null (as per the yaml) > --- > > Key: CASSANDRA-17736 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17736 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.1-beta, 4.1.x > > > There are a few properties that after startup do not show their assigned > values as per the DatabaseDescriptor assignment but the cassandra.yaml value. > They will not be also updated in the virtual table down the road in case they > are updated through JMX, nodetool etc. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17736) Settings Virtual Table should display the values assigned to a property in the DatabaseDescriptor on startup and not null (as per the yaml)
[ https://issues.apache.org/jira/browse/CASSANDRA-17736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17736: Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Component/s: Local/Config Discovered By: User Report Severity: Low Status: Open (was: Triage Needed) > Settings Virtual Table should display the values assigned to a property in > the DatabaseDescriptor on startup and not null (as per the yaml) > --- > > Key: CASSANDRA-17736 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17736 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > > There are a few properties that after startup do not show their assigned > values as per the DatabaseDescriptor assignment but the cassandra.yaml value. > They will not be also updated in the virtual table down the road in case they > are updated through JMX, nodetool etc. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17736) Settings Virtual Table should display the values assigned to a property in the DatabaseDescriptor on startup and not null (as per the yaml)
Ekaterina Dimitrova created CASSANDRA-17736: --- Summary: Settings Virtual Table should display the values assigned to a property in the DatabaseDescriptor on startup and not null (as per the yaml) Key: CASSANDRA-17736 URL: https://issues.apache.org/jira/browse/CASSANDRA-17736 Project: Cassandra Issue Type: Bug Reporter: Ekaterina Dimitrova There are a few properties that after startup do not show their assigned values as per the DatabaseDescriptor assignment but the cassandra.yaml value. They will not be also updated in the virtual table down the road in case they are updated through JMX, nodetool etc. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17734) Validate that JMX and the Settings Virtual Table are aligned
[ https://issues.apache.org/jira/browse/CASSANDRA-17734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17734: Fix Version/s: 4.0.x 4.1.x 4.x > Validate that JMX and the Settings Virtual Table are aligned > > > Key: CASSANDRA-17734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17734 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > I discovered JMX methods that are not updating the Config parameters but > directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ > as users will see wrong values in the Settings virtual table which rely on > the Config parameters (if some value was changed after startup). It will be > explicitly important to ensure there is no disconnect between those when we > add update option for the Virtual Table. > This ticket is meant to serve as an umbrella for subtasks to check the > properties getters methods and for bug tickets for fixes. > > CC [~b.le...@gmail.com] and [~dcapwell] -- 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-17735) Fix issues with index_summary_resize_interval and index_summary_capacity
[ https://issues.apache.org/jira/browse/CASSANDRA-17735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17735: Fix Version/s: 4.0.x 4.1-beta 4.x > Fix issues with index_summary_resize_interval and index_summary_capacity > > > Key: CASSANDRA-17735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17735 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > Fix For: 4.0.x, 4.1-beta, 4.x > > > There are a few problems: > 4.0+: > * the virtual table displays only the cassandra.yaml values for both > properties, all changes after that are not updated > 4.1+: > Breaking compatibility - -1 was considered disabled, this should be > considered as null now for the new config. The converter should be updated. > There is a test for the -1, disable but it didn't caught the issue because of > the previous one mentioned (the disconnect between jmx and the actual > property in Config 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-17735) Fix issues with index_summary_resize_interval and index_summary_capacity
[ https://issues.apache.org/jira/browse/CASSANDRA-17735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17735: Description: There are a few problems: 4.0+: * the virtual table displays only the cassandra.yaml values for both properties, all changes after that are not updated 4.1+: * Breaking compatibility - -1 was considered disabled, this should be considered as null now for the new config. The converter should be updated. There is a test for the -1, disable but it didn't caught the issue because of the previous one mentioned (the disconnect between jmx and the actual property in Config class) was: There are a few problems: 4.0+: * the virtual table displays only the cassandra.yaml values for both properties, all changes after that are not updated 4.1+: Breaking compatibility - -1 was considered disabled, this should be considered as null now for the new config. The converter should be updated. There is a test for the -1, disable but it didn't caught the issue because of the previous one mentioned (the disconnect between jmx and the actual property in Config class) > Fix issues with index_summary_resize_interval and index_summary_capacity > > > Key: CASSANDRA-17735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17735 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > Fix For: 4.0.x, 4.1-beta, 4.x > > > There are a few problems: > 4.0+: > * the virtual table displays only the cassandra.yaml values for both > properties, all changes after that are not updated > 4.1+: > * Breaking compatibility - -1 was considered disabled, this should be > considered as null now for the new config. The converter should be updated. > There is a test for the -1, disable but it didn't caught the issue because of > the previous one mentioned (the disconnect between jmx and the actual > property in Config 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-17734) Validate that JMX and the Settings Virtual Table are aligned
[ https://issues.apache.org/jira/browse/CASSANDRA-17734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17734: Description: I discovered JMX methods that are not updating the Config parameters but directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ as users will see wrong values in the Settings virtual table which rely on the Config parameters (if some value was changed after startup). It will be explicitly important to ensure there is no disconnect between those when we add update option for the Virtual Table. This ticket is meant to serve as an umbrella for subtasks to check the properties getters methods and for bug tickets for fixes. CC [~b.le...@gmail.com] and [~dcapwell] was: I discovered JMX methods that are not updating the Config parameters but directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ as users will see wrong values in the Settings virtual table which rely on the Config parameters (if some value was changed after startup). It will be explicitly important to ensure there is no disconnect between those when we add update option for the Virtual Table. This ticket is meant to serve as an umbrella for subtasks to check the properties getters methods and for bug tickets for fixes. > Validate that JMX and the Settings Virtual Table are aligned > > > Key: CASSANDRA-17734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17734 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > > I discovered JMX methods that are not updating the Config parameters but > directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ > as users will see wrong values in the Settings virtual table which rely on > the Config parameters (if some value was changed after startup). It will be > explicitly important to ensure there is no disconnect between those when we > add update option for the Virtual Table. > This ticket is meant to serve as an umbrella for subtasks to check the > properties getters methods and for bug tickets for fixes. > > CC [~b.le...@gmail.com] and [~dcapwell] -- 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-17735) Fix issues with index_summary_resize_interval and index_summary_capacity
[ https://issues.apache.org/jira/browse/CASSANDRA-17735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova reassigned CASSANDRA-17735: --- Bug Category: Parent values: Degradation(12984) Complexity: Low Hanging Fruit Discovered By: User Report Severity: Low Since Version: 4.1-alpha1 Assignee: Ekaterina Dimitrova > Fix issues with index_summary_resize_interval and index_summary_capacity > > > Key: CASSANDRA-17735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17735 > Project: Cassandra > Issue Type: Bug >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > There are a few problems: > 4.0+: > * the virtual table displays only the cassandra.yaml values for both > properties, all changes after that are not updated > 4.1+: > Breaking compatibility - -1 was considered disabled, this should be > considered as null now for the new config. The converter should be updated. > There is a test for the -1, disable but it didn't caught the issue because of > the previous one mentioned (the disconnect between jmx and the actual > property in Config 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-17735) Fix issues with index_summary_resize_interval and index_summary_capacity
[ https://issues.apache.org/jira/browse/CASSANDRA-17735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17735: Component/s: Local/Config Status: Open (was: Triage Needed) > Fix issues with index_summary_resize_interval and index_summary_capacity > > > Key: CASSANDRA-17735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17735 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > There are a few problems: > 4.0+: > * the virtual table displays only the cassandra.yaml values for both > properties, all changes after that are not updated > 4.1+: > Breaking compatibility - -1 was considered disabled, this should be > considered as null now for the new config. The converter should be updated. > There is a test for the -1, disable but it didn't caught the issue because of > the previous one mentioned (the disconnect between jmx and the actual > property in Config 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] [Created] (CASSANDRA-17735) Fix issues with index_summary_resize_interval and index_summary_capacity
Ekaterina Dimitrova created CASSANDRA-17735: --- Summary: Fix issues with index_summary_resize_interval and index_summary_capacity Key: CASSANDRA-17735 URL: https://issues.apache.org/jira/browse/CASSANDRA-17735 Project: Cassandra Issue Type: Bug Reporter: Ekaterina Dimitrova There are a few problems: 4.0+: * the virtual table displays only the cassandra.yaml values for both properties, all changes after that are not updated 4.1+: Breaking compatibility - -1 was considered disabled, this should be considered as null now for the new config. The converter should be updated. There is a test for the -1, disable but it didn't caught the issue because of the previous one mentioned (the disconnect between jmx and the actual property in Config 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-17734) Validate that JMX and the Settings Virtual Table are aligned
[ https://issues.apache.org/jira/browse/CASSANDRA-17734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17734: Description: I discovered JMX methods that are not updating the Config parameters but directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ as users will see wrong values in the Settings virtual table which rely on the Config parameters (if some value was changed after startup). It will be explicitly important to ensure there is no disconnect between those when we add update option for the Virtual Table. This ticket is meant to serve as an umbrella for subtasks to check the properties getters methods and for bug tickets for fixes. was: I discovered JMX methods that are not updating the Config parameters but directly the usage. This is a bug in 4.0+ as users will see wrong values in the Settings virtual table which rely on the Config parameters if some value was changed after startup. It will be explicitly important to ensure there is no disconnect between those when we add update option for the Virtual Table This ticket is meant to serve as an umbrella for subtasks to check different properties and bug tickets for fixes. > Validate that JMX and the Settings Virtual Table are aligned > > > Key: CASSANDRA-17734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17734 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > > I discovered JMX methods that are not updating the Config parameters but > directly the usage. (see index_summary_resize_interval) This is a bug in 4.0+ > as users will see wrong values in the Settings virtual table which rely on > the Config parameters (if some value was changed after startup). It will be > explicitly important to ensure there is no disconnect between those when we > add update option for the Virtual Table. > This ticket is meant to serve as an umbrella for subtasks to check the > properties getters methods and for bug tickets for fixes. -- 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-17734) Validate that JMX and the Settings Virtual Table are aligned
[ https://issues.apache.org/jira/browse/CASSANDRA-17734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17734: Change Category: Operability Complexity: Low Hanging Fruit Component/s: Local/Config Status: Open (was: Triage Needed) > Validate that JMX and the Settings Virtual Table are aligned > > > Key: CASSANDRA-17734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17734 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > > I discovered JMX methods that are not updating the Config parameters but > directly the usage. This is a bug in 4.0+ as users will see wrong values in > the Settings virtual table which rely on the Config parameters if some value > was changed after startup. It will be explicitly important to ensure there is > no disconnect between those when we add update option for the Virtual Table > This ticket is meant to serve as an umbrella for subtasks to check different > properties and bug tickets for fixes. -- 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-17734) Validate that JMX and the Settings Virtual Table are aligned
Ekaterina Dimitrova created CASSANDRA-17734: --- Summary: Validate that JMX and the Settings Virtual Table are aligned Key: CASSANDRA-17734 URL: https://issues.apache.org/jira/browse/CASSANDRA-17734 Project: Cassandra Issue Type: Task Reporter: Ekaterina Dimitrova I discovered JMX methods that are not updating the Config parameters but directly the usage. This is a bug in 4.0+ as users will see wrong values in the Settings virtual table which rely on the Config parameters if some value was changed after startup. It will be explicitly important to ensure there is no disconnect between those when we add update option for the Virtual Table This ticket is meant to serve as an umbrella for subtasks to check different properties and bug tickets for fixes. -- 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-17733) min_tracked_partition_size_bytes should not have the suffix prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563251#comment-17563251 ] Marcus Eriksson commented on CASSANDRA-17733: - +1 on just renaming it, thanks for catching this > min_tracked_partition_size_bytes should not have the suffix prefix > -- > > Key: CASSANDRA-17733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17733 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.x > > > min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have > not been added with the unit suffix anymore as confirmed on the commit. > It is also confusing now when users can add unit of their choice. > We have two options: > * keep it with annotation and add also version without the suffix > * rename it as we are still alpha and API changes can be done for bug > fixing. Not sure whether we need an approval on the ML for this one. > CC [~ycai] , [~marcuse] and [~dcapwell] -- 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-17733) min_tracked_partition_size_bytes should not have the suffix prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17733: Description: min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have not been added with the unit suffix anymore as confirmed on the commit. It is also confusing now when users can add unit of their choice. We have two options: * keep it with annotation and add also version without the suffix * rename it as we are still alpha and API changes can be done for bug fixing. Not sure whether we need an approval on the ML for this one. CC [~ycai] , [~marcuse] and [~dcapwell] was: min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have not been added with the suffix anymore as confirmed on the commit. It is also confusing now when users can add unit of their choice. We have two options: * keep it with annotation and add also version without the suffix * rename it as we are still alpha and API changes can be done for bug fixing. Not sure whether we need an approval on the ML for this one. CC [~ycai] , [~marcuse] and [~dcapwell] > min_tracked_partition_size_bytes should not have the suffix prefix > -- > > Key: CASSANDRA-17733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17733 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.x > > > min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have > not been added with the unit suffix anymore as confirmed on the commit. > It is also confusing now when users can add unit of their choice. > We have two options: > * keep it with annotation and add also version without the suffix > * rename it as we are still alpha and API changes can be done for bug > fixing. Not sure whether we need an approval on the ML for this one. > CC [~ycai] , [~marcuse] and [~dcapwell] -- 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-17733) min_tracked_partition_size_bytes should not have the suffix prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17733: Fix Version/s: 4.1-beta > min_tracked_partition_size_bytes should not have the suffix prefix > -- > > Key: CASSANDRA-17733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17733 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta > > > min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have > not been added with the suffix anymore as confirmed on the commit. > It is also confusing now when users can add unit of their choice. > We have two options: > * keep it with annotation and add also version without the suffix > * rename it as we are still alpha and API changes can be done for bug > fixing. Not sure whether we need an approval on the ML for this one. > CC [~ycai] , [~marcuse] and [~dcapwell] -- 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-17733) min_tracked_partition_size_bytes should not have the suffix prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17733: Fix Version/s: 4.x > min_tracked_partition_size_bytes should not have the suffix prefix > -- > > Key: CASSANDRA-17733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17733 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1-beta, 4.x > > > min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have > not been added with the suffix anymore as confirmed on the commit. > It is also confusing now when users can add unit of their choice. > We have two options: > * keep it with annotation and add also version without the suffix > * rename it as we are still alpha and API changes can be done for bug > fixing. Not sure whether we need an approval on the ML for this one. > CC [~ycai] , [~marcuse] and [~dcapwell] -- 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-17733) min_tracked_partition_size_bytes should not have the suffix prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17733: Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Component/s: Local/Config Discovered By: User Report Severity: Low Status: Open (was: Triage Needed) > min_tracked_partition_size_bytes should not have the suffix prefix > -- > > Key: CASSANDRA-17733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17733 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > > min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have > not been added with the suffix anymore as confirmed on the commit. > It is also confusing now when users can add unit of their choice. > We have two options: > * keep it with annotation and add also version without the suffix > * rename it as we are still alpha and API changes can be done for bug > fixing. Not sure whether we need an approval on the ML for this one. > CC [~ycai] , [~marcuse] and [~dcapwell] -- 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-17733) min_tracked_partition_size_bytes should not have the suffix prefix
Ekaterina Dimitrova created CASSANDRA-17733: --- Summary: min_tracked_partition_size_bytes should not have the suffix prefix Key: CASSANDRA-17733 URL: https://issues.apache.org/jira/browse/CASSANDRA-17733 Project: Cassandra Issue Type: Bug Reporter: Ekaterina Dimitrova min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have not been added with the suffix anymore as confirmed on the commit. It is also confusing now when users can add unit of their choice. We have two options: * keep it with annotation and add also version without the suffix * rename it as we are still alpha and API changes can be done for bug fixing. Not sure whether we need an approval on the ML for this one. CC [~ycai] , [~marcuse] and [~dcapwell] -- 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-15511) Utilising BTree Improvements
[
https://issues.apache.org/jira/browse/CASSANDRA-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563223#comment-17563223
]
Benjamin Lerer commented on CASSANDRA-15511:
|| Branch || CI ||
|[4.0|https://github.com/apache/cassandra/pull/1646]|[j8|https://app.circleci.com/pipelines/github/blerer/cassandra/310/workflows/fdbdfe80-38d4-44da-82a4-87f1c0e2afc2]|
|[4.1|https://github.com/apache/cassandra/pull/1719]|[j8|https://app.circleci.com/pipelines/github/blerer/cassandra/311/workflows/8782993a-282f-48ae-94da-b97b32413956]|
|[trunk|https://github.com/apache/cassandra/pull/1720]|[j8|https://app.circleci.com/pipelines/github/blerer/cassandra/312/workflows/013a764a-c121-438c-9894-170d9c951510]|
> Utilising BTree Improvements
>
>
> Key: CASSANDRA-15511
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15511
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Other
>Reporter: Benedict Elliott Smith
>Assignee: Benedict Elliott Smith
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
> Attachments: atomicbtreepartition.ods, atomicbtreepartition.xlsx.zip,
> perfsh.tar.gz
>
>
> This patch utilises CASSANDRA-15510 to improve throughput and reduce garbage
> produced by a number of common operations, by employing
> {{transformAndFilter}}, {{transform}} and {{FastBuilder}}
> * {{Row}}, {{Cell}} and {{ComplexColumnData}} cloning are implemented with
> {{BTree.transform}}, so no special builders are necessary;
> ** {{Rows.copy}} removed
> * {{Rows.merge}} implemented using {{BTree.update}} and a {{ColumnData}}
> reconciler
> ** Zero-allocations if result of merge is same as {{existing}}
> ** Fewer comparisons
> * {{ColumnData}} reconciler implemented in same manner
> ** {{Cells.reconcileComplex}} is retired
> ** {{ComplexColumnData}} reconciliation now
> *** Garbage-free if the merge has no effect
> *** Always fewer allocations
> *** Fewer comparisons
> * {{FastBuilder}} employed widely:
> ** {{ClusteringIndexNamesFilter}} deserialization
> ** {{Columns}} deserialization
> ** {{PartitionUpdate}} deserialization
> ** {{AbstractBTreePartition}} construction
> ** Misc others
> The upshot of this work when combined with the proposed patch for
> CASSANDRA-15367 has a dramatic impact on operations over collection types -
> under contention, as much as 100x improved throughput, and hundreds of
> megabytes of reduced allocations. For all operations, allocations under
> contention and no contention are significantly reduced and throughput
> improved.
--
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-17489) Test Failures: org.apache.cassandra.metrics and a few others failing (utests_system_keyspace_directory on circleci)
[
https://issues.apache.org/jira/browse/CASSANDRA-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-17489:
---
Status: Ready to Commit (was: Review In Progress)
> Test Failures: org.apache.cassandra.metrics and a few others failing
> (utests_system_keyspace_directory on circleci)
> ---
>
> Key: CASSANDRA-17489
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17489
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Blake Eggleston
>Priority: Urgent
> Fix For: 4.1-beta
>
>
> There are 10 tests failing in CircleCI - utests_system_keyspace_directory
> This test target is not presented in Jenkins.
>
> The tests fail for the same reason:
> {code:java}
> java.lang.RuntimeException: java.nio.file.NoSuchFileException:
> build/test/cassandra/data/system/_paxos_repair_state/ballot.meta.tmp at
> org.apache.cassandra.io.util.SequentialWriter.openChannel(SequentialWriter.java:128)
> at
> org.apache.cassandra.io.util.SequentialWriter.(SequentialWriter.java:161)
> at
> org.apache.cassandra.io.util.SequentialWriter.(SequentialWriter.java:150)
> at
> org.apache.cassandra.service.paxos.uncommitted.PaxosBallotTracker.flush(PaxosBallotTracker.java:130)
> at
> org.apache.cassandra.service.paxos.uncommitted.PaxosStateTracker.maybeRebuild(PaxosStateTracker.java:309)
> at
> org.apache.cassandra.service.paxos.PaxosState.maybeRebuildUncommittedState(PaxosState.java:122)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:368)
> at
> org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:655)
> at
> org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
> at org.apache.cassandra.metrics.CQLMetricsTest.setup(CQLMetricsTest.java:53)
> Caused by: java.nio.file.NoSuchFileException:
> build/test/cassandra/data/system/_paxos_repair_state/ballot.meta.tmp at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at
> sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:177)
> at java.nio.channels.FileChannel.open(FileChannel.java:287) at
> java.nio.channels.FileChannel.open(FileChannel.java:335) at
> org.apache.cassandra.io.util.SequentialWriter.openChannel(SequentialWriter.java:113){code}
> The tests started failing every time after CEP 14 was committed.
> For reference:
> * build before -
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1484/workflows/88cac38a-ee0c-46e2-a6a7-5c364ff04f3e/jobs/9680
> * build after -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1485/workflows/c3f56ec1-2ef0-4e61-b689-c7764934827d/jobs/9682]
> I think the only unrelated is
> {code:java}
> testTokenGenerator_single_rack_or_single_rf{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-17489) Test Failures: org.apache.cassandra.metrics and a few others failing (utests_system_keyspace_directory on circleci)
[
https://issues.apache.org/jira/browse/CASSANDRA-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563212#comment-17563212
]
Benjamin Lerer commented on CASSANDRA-17489:
The patch look good to me. Thanks [~bdeggleston]
> Test Failures: org.apache.cassandra.metrics and a few others failing
> (utests_system_keyspace_directory on circleci)
> ---
>
> Key: CASSANDRA-17489
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17489
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Blake Eggleston
>Priority: Urgent
> Fix For: 4.1-beta
>
>
> There are 10 tests failing in CircleCI - utests_system_keyspace_directory
> This test target is not presented in Jenkins.
>
> The tests fail for the same reason:
> {code:java}
> java.lang.RuntimeException: java.nio.file.NoSuchFileException:
> build/test/cassandra/data/system/_paxos_repair_state/ballot.meta.tmp at
> org.apache.cassandra.io.util.SequentialWriter.openChannel(SequentialWriter.java:128)
> at
> org.apache.cassandra.io.util.SequentialWriter.(SequentialWriter.java:161)
> at
> org.apache.cassandra.io.util.SequentialWriter.(SequentialWriter.java:150)
> at
> org.apache.cassandra.service.paxos.uncommitted.PaxosBallotTracker.flush(PaxosBallotTracker.java:130)
> at
> org.apache.cassandra.service.paxos.uncommitted.PaxosStateTracker.maybeRebuild(PaxosStateTracker.java:309)
> at
> org.apache.cassandra.service.paxos.PaxosState.maybeRebuildUncommittedState(PaxosState.java:122)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:368)
> at
> org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:655)
> at
> org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
> at org.apache.cassandra.metrics.CQLMetricsTest.setup(CQLMetricsTest.java:53)
> Caused by: java.nio.file.NoSuchFileException:
> build/test/cassandra/data/system/_paxos_repair_state/ballot.meta.tmp at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at
> sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:177)
> at java.nio.channels.FileChannel.open(FileChannel.java:287) at
> java.nio.channels.FileChannel.open(FileChannel.java:335) at
> org.apache.cassandra.io.util.SequentialWriter.openChannel(SequentialWriter.java:113){code}
> The tests started failing every time after CEP 14 was committed.
> For reference:
> * build before -
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1484/workflows/88cac38a-ee0c-46e2-a6a7-5c364ff04f3e/jobs/9680
> * build after -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1485/workflows/c3f56ec1-2ef0-4e61-b689-c7764934827d/jobs/9682]
> I think the only unrelated is
> {code:java}
> testTokenGenerator_single_rack_or_single_rf{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-17489) Test Failures: org.apache.cassandra.metrics and a few others failing (utests_system_keyspace_directory on circleci)
[
https://issues.apache.org/jira/browse/CASSANDRA-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-17489:
---
Reviewers: Benjamin Lerer, Berenguer Blasi, Benjamin Lerer (was: Berenguer
Blasi)
Benjamin Lerer, Berenguer Blasi, Benjamin Lerer (was: Benjamin
Lerer, Berenguer Blasi)
Status: Review In Progress (was: Patch Available)
> Test Failures: org.apache.cassandra.metrics and a few others failing
> (utests_system_keyspace_directory on circleci)
> ---
>
> Key: CASSANDRA-17489
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17489
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Blake Eggleston
>Priority: Urgent
> Fix For: 4.1-beta
>
>
> There are 10 tests failing in CircleCI - utests_system_keyspace_directory
> This test target is not presented in Jenkins.
>
> The tests fail for the same reason:
> {code:java}
> java.lang.RuntimeException: java.nio.file.NoSuchFileException:
> build/test/cassandra/data/system/_paxos_repair_state/ballot.meta.tmp at
> org.apache.cassandra.io.util.SequentialWriter.openChannel(SequentialWriter.java:128)
> at
> org.apache.cassandra.io.util.SequentialWriter.(SequentialWriter.java:161)
> at
> org.apache.cassandra.io.util.SequentialWriter.(SequentialWriter.java:150)
> at
> org.apache.cassandra.service.paxos.uncommitted.PaxosBallotTracker.flush(PaxosBallotTracker.java:130)
> at
> org.apache.cassandra.service.paxos.uncommitted.PaxosStateTracker.maybeRebuild(PaxosStateTracker.java:309)
> at
> org.apache.cassandra.service.paxos.PaxosState.maybeRebuildUncommittedState(PaxosState.java:122)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:368)
> at
> org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:655)
> at
> org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
> at org.apache.cassandra.metrics.CQLMetricsTest.setup(CQLMetricsTest.java:53)
> Caused by: java.nio.file.NoSuchFileException:
> build/test/cassandra/data/system/_paxos_repair_state/ballot.meta.tmp at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at
> sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:177)
> at java.nio.channels.FileChannel.open(FileChannel.java:287) at
> java.nio.channels.FileChannel.open(FileChannel.java:335) at
> org.apache.cassandra.io.util.SequentialWriter.openChannel(SequentialWriter.java:113){code}
> The tests started failing every time after CEP 14 was committed.
> For reference:
> * build before -
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1484/workflows/88cac38a-ee0c-46e2-a6a7-5c364ff04f3e/jobs/9680
> * build after -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1485/workflows/c3f56ec1-2ef0-4e61-b689-c7764934827d/jobs/9682]
> I think the only unrelated is
> {code:java}
> testTokenGenerator_single_rack_or_single_rf{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-17570) Update the CQL version for the 4.1 release
[
https://issues.apache.org/jira/browse/CASSANDRA-17570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563195#comment-17563195
]
Benjamin Lerer commented on CASSANDRA-17570:
+1
> Update the CQL version for the 4.1 release
> --
>
> Key: CASSANDRA-17570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17570
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Berenguer Blasi
>Priority: Urgent
> Fix For: 4.1-rc
>
>
> We made several changes to CQL during that version. We need to document those
> changes in the {{CQL.textile}} file and update the version.
--
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-17729) Raise test timeouts
[ https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563145#comment-17563145 ] Michael Semb Wever commented on CASSANDRA-17729: Agree with the notion that Jenkins (lower resources/more contention) is better at exposing flakies, but that there's a trade-off between encouraging flakies and creating difficult-to-deal-with noise. While I'm for raising the discussion about what is the base hardware requirement (once HDD issues are resolved and all agents are active again), I don't see this as an argument not to continuously improve tests to be more robust. So +1 to the patch. > Raise test timeouts > --- > > Key: CASSANDRA-17729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17729 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.1-beta > > > We have seen for some time now junits timeout frequently on jenkins. This is > probably down to it being a very loaded env. On circle we don't observe that > behavior probably bc it's not so loaded. > The question is whether it is time to raise timeouts as they might be hiding > legit failures. As en experiment I raised timeouts in a branch and ran > jenkins against it. What I see is that the last 4.1 run had 14 failures out > of which 12 were timeouts. Increasing timeouts reveals what looks to be 9 > legit failures where 2 are timeouts that probably need to be investigated. -- 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-17232) org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563077#comment-17563077
]
Berenguer Blasi edited comment on CASSANDRA-17232 at 7/6/22 9:47 AM:
-
So we were swallowing interrupts
[here|https://github.com/apache/cassandra/pull/1651/files#diff-536585042adf6b16fdd0a2d894080cb7c3a7f0ab7f67e2d9dd8dbf09110b74daR159],
which has a wait at the end, hence blocking and timing out when waiting on the
executor to finish.
I got past that but now I hit again file inconsistencies and the original
error. So some progress made but this is still quite convoluted.
was (Author: bereng):
So we were swallowing interrupts
[here|https://github.com/apache/cassandra/pull/1651/files#diff-536585042adf6b16fdd0a2d894080cb7c3a7f0ab7f67e2d9dd8dbf09110b74daR159]
hence, which has a wait at the end, blocking and timing out when waiting on
the executor to finish.
I got past that but now I hit again file inconsistencies. So some progress made
but this is still quite convoluted.
> org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
> ---
>
> Key: CASSANDRA-17232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> I saw
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
> and
> [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
> the same assertion failure:
>
> {code:java}
> org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
> Error Message
> expected:<204> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<204> but was:<0> at
> org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
> {code}
>
> Then I find that there are many other tests from GroupCommitLogTest failing
> with No such file found.
> Example:
> https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/
--
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-17127) Remove use of deprecated java.util.concurrent in tests
[
https://issues.apache.org/jira/browse/CASSANDRA-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563078#comment-17563078
]
Claude Warren commented on CASSANDRA-17127:
---
A 3rd option is to use the suppression filter and build it from the standard
suppression filter to create a test suppression filter that excludes the
illegal import messages for the specific classes.
> Remove use of deprecated java.util.concurrent in tests
> --
>
> Key: CASSANDRA-17127
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17127
> Project: Cassandra
> Issue Type: Sub-task
> Components: Test/unit
>Reporter: Brandon Williams
>Assignee: Claude Warren
>Priority: Normal
>
> {noformat}
> 1 Illegal import - java.util.concurrent.ArrayBlockingQueue.
> [IllegalImport]
> 11 Illegal import - java.util.concurrent.CompletableFuture.
> [IllegalImport]
> 39 Illegal import - java.util.concurrent.CountDownLatch. [IllegalImport]
> 48 Illegal import - java.util.concurrent.Executors. [IllegalImport]
> 3 Illegal import - java.util.concurrent.LinkedBlockingQueue.
> [IllegalImport]
> 5 Illegal import - java.util.concurrent.Semaphore. [IllegalImport]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17232) org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563077#comment-17563077
]
Berenguer Blasi commented on CASSANDRA-17232:
-
So we were swallowing interrupts
[here|https://github.com/apache/cassandra/pull/1651/files#diff-536585042adf6b16fdd0a2d894080cb7c3a7f0ab7f67e2d9dd8dbf09110b74daR159]
hence, which has a wait at the end, blocking and timing out when waiting on
the executor to finish.
I got past that but now I hit again file inconsistencies. So some progress made
but this is still quite convoluted.
> org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
> ---
>
> Key: CASSANDRA-17232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> I saw
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
> and
> [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
> the same assertion failure:
>
> {code:java}
> org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
> Error Message
> expected:<204> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<204> but was:<0> at
> org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
> {code}
>
> Then I find that there are many other tests from GroupCommitLogTest failing
> with No such file found.
> Example:
> https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/
--
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 (29f46ee8 -> 32a80afc)
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 29f46ee8 generate docs for 07cc189e new 32a80afc generate docs for 07cc189e 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 (29f46ee8) \ N -- N -- N refs/heads/asf-staging (32a80afc) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (db1d62b9 -> 29f46ee8)
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 db1d62b9 generate docs for 07cc189e new 29f46ee8 generate docs for 07cc189e 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 (db1d62b9) \ N -- N -- N refs/heads/asf-staging (29f46ee8) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17127) Remove use of deprecated java.util.concurrent in tests
[
https://issues.apache.org/jira/browse/CASSANDRA-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Warren reassigned CASSANDRA-17127:
-
Assignee: Claude Warren
> Remove use of deprecated java.util.concurrent in tests
> --
>
> Key: CASSANDRA-17127
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17127
> Project: Cassandra
> Issue Type: Sub-task
> Components: Test/unit
>Reporter: Brandon Williams
>Assignee: Claude Warren
>Priority: Normal
>
> {noformat}
> 1 Illegal import - java.util.concurrent.ArrayBlockingQueue.
> [IllegalImport]
> 11 Illegal import - java.util.concurrent.CompletableFuture.
> [IllegalImport]
> 39 Illegal import - java.util.concurrent.CountDownLatch. [IllegalImport]
> 48 Illegal import - java.util.concurrent.Executors. [IllegalImport]
> 3 Illegal import - java.util.concurrent.LinkedBlockingQueue.
> [IllegalImport]
> 5 Illegal import - java.util.concurrent.Semaphore. [IllegalImport]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
