[cassandra-website] branch asf-staging updated (6f24e3f23 -> d1a35ace1)
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 6f24e3f23 generate docs for c99e80d5 new d1a35ace1 generate docs for c99e80d5 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 (6f24e3f23) \ N -- N -- N refs/heads/asf-staging (d1a35ace1) 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 4852435 -> 4852435 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
[cassandra-website] branch asf-staging updated (3e0e9c59a -> 6f24e3f23)
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 3e0e9c59a generate docs for c99e80d5 new 6f24e3f23 generate docs for c99e80d5 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 (3e0e9c59a) \ N -- N -- N refs/heads/asf-staging (6f24e3f23) 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 4852435 -> 4852435 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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753368#comment-17753368 ] Abe Ratnofsky commented on CASSANDRA-18743: --- Looks like there's consensus on the ML thread: https://lists.apache.org/thread/lppjlxrd91qn0r0dkz80r5y843jwl1qo Patches look good to me, but my understanding was that the deprecation had to last one major. So if 5.1 is going to be cut from trunk in the future, then trunk is not the right place to apply the removal patch just yet. [~brandon.williams] could you confirm? > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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
[GitHub] [cassandra-analytics] yifan-c commented on a diff in pull request #11: CASSANDRA-18683: Add PartitionSizeTableProvider for reading the compressed and uncompr…
yifan-c commented on code in PR #11:
URL:
https://github.com/apache/cassandra-analytics/pull/11#discussion_r1291816343
##
cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/sparksql/SparkCellIterator.java:
##
@@ -339,21 +337,28 @@ private void maybeRebuildPartition()
}
// Or new partition, so deserialize partition keys and update 'values'
array
-ByteBuffer partitionKey = rid.getPartitionKey();
-if (numPartitionKeys == 1)
+readPartitionKey(rid.getPartitionKey(), cqlTable, this.values, stats);
+}
+
+public static void readPartitionKey(final ByteBuffer partitionKey,
+final CqlTable table,
+final Object[] values,
+final Stats stats)
+{
+if (table.numPartitionKeys() == 1)
{
// Not a composite partition key
-CqlField field = cqlTable.partitionKeys().get(0);
-values[field.position()] = deserialize(field, partitionKey);
+final CqlField field = table.partitionKeys().get(0);
Review Comment:
nit: avoid using the unnecessary `final`. The project use the same code
style as in https://cassandra.apache.org/_/development/code_style.html
##
cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/sparksql/PartitionSizeIterator.java:
##
@@ -0,0 +1,89 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+package org.apache.cassandra.spark.sparksql;
+
+import java.io.IOException;
+
+import org.apache.cassandra.spark.data.CqlTable;
+import org.apache.cassandra.spark.data.DataLayer;
+import org.apache.cassandra.spark.reader.IndexEntry;
+import org.apache.cassandra.spark.reader.StreamScanner;
+import org.apache.cassandra.spark.stats.Stats;
+import org.apache.spark.sql.catalyst.InternalRow;
+import org.apache.spark.sql.catalyst.expressions.GenericInternalRow;
+import org.apache.spark.sql.connector.read.PartitionReader;
+import org.jetbrains.annotations.NotNull;
+
+/**
+ * Wrapper iterator around IndexIterator to read all Index.db files and return
SparkSQL
+ * rows containing all partition keys and the associated on-disk uncompressed
and compressed sizes.
+ */
+public class PartitionSizeIterator implements PartitionReader
+{
+private final StreamScanner it;
+private final CqlTable cqlTable;
+private final int numPartitionKeys;
+private final Stats stats;
+private final long startTimeNanos;
+private GenericInternalRow curr = null;
+
+public PartitionSizeIterator(final int partitionId, @NotNull final
DataLayer dataLayer)
+{
+this.cqlTable = dataLayer.cqlTable();
+this.numPartitionKeys = cqlTable.numPartitionKeys();
+this.stats = dataLayer.stats();
+this.startTimeNanos = System.nanoTime();
+this.it = dataLayer.openPartitionSizeIterator(partitionId);
+stats.openedPartitionSizeIterator(System.nanoTime() - startTimeNanos);
+}
+
+public boolean next() throws IOException
+{
+if (it.hasNext())
+{
+it.advanceToNextColumn();
+
+final IndexEntry entry = it.rid();
+final Object[] values = new Object[numPartitionKeys + 2];
+
+SparkCellIterator.readPartitionKey(entry.getPartitionKey(),
cqlTable, values, stats);
+values[numPartitionKeys] = entry.getUncompressed();
+values[numPartitionKeys + 1] = entry.getCompressed();
Review Comment:
nit: add a comment to associate the data population with the schema defined
at `partitionSizeStructType` in `DataLayer`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRASC-68: - Epic Link: (was: CASSANDRASC-13) > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-68: Authors: Saranya Krishnakumar Test and Documentation Plan: Added a small interface, so far no tests added Status: Patch Available (was: Open) > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-68: Change Category: Operability Complexity: Low Hanging Fruit Reviewers: Yifan Cai Priority: High (was: Normal) Status: Open (was: Triage Needed) > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saranya Krishnakumar updated CASSANDRASC-68: Description: We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. PR: [https://github.com/apache/cassandra-sidecar/pull/64] was:We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
Saranya Krishnakumar created CASSANDRASC-68: --- Summary: Add Metrics publisher interface to Sidecar to expose metrics for capture Key: CASSANDRASC-68 URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 Project: Sidecar for Apache Cassandra Issue Type: New Feature Components: Rest API Reporter: Saranya Krishnakumar Assignee: Saranya Krishnakumar We need metrics publisher interface in Sidecar to capture some of the metrics like bytes written/streamed. -- 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-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18708:
Since Version: (was: 5.x)
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0, 5.1
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
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-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18708:
Fix Version/s: 5.0
5.1
(was: 5.x)
Since Version: 5.x
Source Control Link:
https://github.com/apache/cassandra/commit/000533cb633cc900f277c1612862480944b9f6ea.
https://github.com/apache/cassandra/commit/8f3c8e721e991d1e2219ac32edacde9d5c19ce82
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0, 5.1
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
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-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753336#comment-17753336
]
Ekaterina Dimitrova commented on CASSANDRA-18708:
-
Commiited
f8d4e2a3c8..000533cb63 cassandra-5.0 -> cassandra-5.0
5ade7a6cd8..8f3c8e721e trunk -> trunk
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-5.0 updated (f8d4e2a3c8 -> 000533cb63)
This is an automated email from the ASF dual-hosted git repository.
edimitrova pushed a change to branch cassandra-5.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
from f8d4e2a3c8 Disable heap dump creation by default on crash for tests
that use test/conf/cassandra.yaml
add 000533cb63 Prevent InaccessibleObjectException when the Leak Detector
is traversing objects
No new revisions were added by this update.
Summary of changes:
CHANGES.txt| 1 +
.../UnaccessibleFieldException.java} | 10 +--
.../org/apache/cassandra/utils/concurrent/Ref.java | 78 +++---
3 files changed, 74 insertions(+), 15 deletions(-)
copy src/java/org/apache/cassandra/{serializers/MarshalException.java =>
exceptions/UnaccessibleFieldException.java} (74%)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 8f3c8e721e991d1e2219ac32edacde9d5c19ce82 Merge: 5ade7a6cd8 000533cb63 Author: Ekaterina Dimitrova AuthorDate: Fri Aug 11 15:44:36 2023 -0400 Merge branch 'cassandra-5.0' into trunk CHANGES.txt| 1 + .../exceptions/UnaccessibleFieldException.java | 34 ++ .../org/apache/cassandra/utils/concurrent/Ref.java | 78 +++--- 3 files changed, 102 insertions(+), 11 deletions(-) diff --cc CHANGES.txt index 969b959e01,984b9ef99d..6761949457 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,5 -1,5 +1,6 @@@ -5.0 +5.1 +Merged from 5.0: + * Prevent InaccessibleObjectException when the Leak Detector is traversing objects (CASSANDRA-18708) * Remove legacy command line options from cassandra-stress (CASSANDRA-18529) * Remove commitlog_sync_batch_window_in_ms (CASSANDRA-17161) * Upgrade JMH from 1.21 to 1.36 (CASSANDRA-18696) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (5ade7a6cd8 -> 8f3c8e721e)
This is an automated email from the ASF dual-hosted git repository.
edimitrova pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
from 5ade7a6cd8 Merge branch 'cassandra-5.0' into trunk
add 000533cb63 Prevent InaccessibleObjectException when the Leak Detector
is traversing objects
new 8f3c8e721e Merge branch 'cassandra-5.0' into trunk
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
CHANGES.txt| 1 +
.../UnaccessibleFieldException.java} | 10 +--
.../org/apache/cassandra/utils/concurrent/Ref.java | 78 +++---
3 files changed, 74 insertions(+), 15 deletions(-)
copy src/java/org/apache/cassandra/{serializers/MarshalException.java =>
exceptions/UnaccessibleFieldException.java} (74%)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18725) IsolatedJMX should not release all TCPEndpoints on instance shutdown
[ https://issues.apache.org/jira/browse/CASSANDRA-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer updated CASSANDRA-18725: Test and Documentation Plan: Tests are updated in the dtest JMXFeatureTest and JMXGetterCheckTest for each branch. Status: Patch Available (was: Open) See attached Github PRs for patches for each branch - will attach CircleCI runs once they are completed. > IsolatedJMX should not release all TCPEndpoints on instance shutdown > > > Key: CASSANDRA-18725 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18725 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Fix For: 3.11.x, 4.0, 4.1.x, 5.0, 5.1 > > Time Spent: 50m > Remaining Estimate: 0h > > In the original implementation of the JMX feature, we fixed some memory leaks > by clearing some internal state in Java’s TCPEndpoint. However, that > implementation was overly aggressive and cleared the whole map, vs. just > removing the endpoints created by the individual instances. This causes > issues when you remove a node from the cluster (as all of the endpoints are > cleared, not just the ones in use by that instance). > > In stead, we should check if the endpoint was created by the instance in > question and only remove it if it was. -- 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-18725) IsolatedJMX should not release all TCPEndpoints on instance shutdown
[ https://issues.apache.org/jira/browse/CASSANDRA-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer updated CASSANDRA-18725: Change Category: Operability Complexity: Challenging Component/s: Test/dtest/java Status: Open (was: Triage Needed) > IsolatedJMX should not release all TCPEndpoints on instance shutdown > > > Key: CASSANDRA-18725 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18725 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Fix For: 3.11.x, 4.1.x, 5.0, 5.1, 4.0 > > Time Spent: 50m > Remaining Estimate: 0h > > In the original implementation of the JMX feature, we fixed some memory leaks > by clearing some internal state in Java’s TCPEndpoint. However, that > implementation was overly aggressive and cleared the whole map, vs. just > removing the endpoints created by the individual instances. This causes > issues when you remove a node from the cluster (as all of the endpoints are > cleared, not just the ones in use by that instance). > > In stead, we should check if the endpoint was created by the instance in > question and only remove it if it was. -- 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-18725) IsolatedJMX should not release all TCPEndpoints on instance shutdown
[ https://issues.apache.org/jira/browse/CASSANDRA-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer reassigned CASSANDRA-18725: --- Assignee: Doug Rohrer > IsolatedJMX should not release all TCPEndpoints on instance shutdown > > > Key: CASSANDRA-18725 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18725 > Project: Cassandra > Issue Type: Improvement >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Fix For: 3.11.x, 4.0, 4.1.x, 5.0, 5.1 > > Time Spent: 50m > Remaining Estimate: 0h > > In the original implementation of the JMX feature, we fixed some memory leaks > by clearing some internal state in Java’s TCPEndpoint. However, that > implementation was overly aggressive and cleared the whole map, vs. just > removing the endpoints created by the individual instances. This causes > issues when you remove a node from the cluster (as all of the endpoints are > cleared, not just the ones in use by that instance). > > In stead, we should check if the endpoint was created by the instance in > question and only remove it if it was. -- 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-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753324#comment-17753324
]
Ekaterina Dimitrova commented on CASSANDRA-18708:
-
CASSANDRA-18747 was opened for the assertions failures
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18747) Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.cassandra.db.Keysp
[
https://issues.apache.org/jira/browse/CASSANDRA-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18747:
Workflow: Copy of Cassandra Bug Workflow (was: Copy of Cassandra Default
Workflow)
Issue Type: Bug (was: Task)
> Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
> -
>
> Key: CASSANDRA-18747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x, 5.1.x
>
>
> I've been seeing this assertion error in different tests lately.
> Full error message:
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
> 16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
> node logs (see stdout for full details). Errors: [[node2] 'ERROR
> [PendingRangeCalculator:1] 2023-08-11 16:35:14,445
> JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']{code}
> Example failures:
> test_failed_snitch_update_property_file_snitch -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2475/workflows/2086619e-0f21-464b-a866-84aca516b5e5/jobs/36716/tests]
> test_gcgs_validation -
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1666/testReport/junit/dtest.materialized_views_test/TestMaterializedViews/test_gcgs_validation/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18747) Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.cassandra.db.Keysp
[
https://issues.apache.org/jira/browse/CASSANDRA-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18747:
Fix Version/s: 5.x
5.1.x
> Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
> -
>
> Key: CASSANDRA-18747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
> Project: Cassandra
> Issue Type: Task
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x, 5.1.x
>
>
> I've been seeing this assertion error in different tests lately.
> Full error message:
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
> 16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
> node logs (see stdout for full details). Errors: [[node2] 'ERROR
> [PendingRangeCalculator:1] 2023-08-11 16:35:14,445
> JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']{code}
> Example failures:
> test_failed_snitch_update_property_file_snitch -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2475/workflows/2086619e-0f21-464b-a866-84aca516b5e5/jobs/36716/tests]
> test_gcgs_validation -
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1666/testReport/junit/dtest.materialized_views_test/TestMaterializedViews/test_gcgs_validation/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18747) Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.cassandra.db.Keysp
[
https://issues.apache.org/jira/browse/CASSANDRA-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18747:
Change Category: Quality Assurance
Complexity: Normal
Component/s: Test/dtest/python
Status: Open (was: Triage Needed)
> Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
> -
>
> Key: CASSANDRA-18747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x, 5.1.x
>
>
> I've been seeing this assertion error in different tests lately.
> Full error message:
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
> 16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
> node logs (see stdout for full details). Errors: [[node2] 'ERROR
> [PendingRangeCalculator:1] 2023-08-11 16:35:14,445
> JVMStabilityInspector.java:70 - Exception in thread
> Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
> Unknown keyspace system_auth\n\tat
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
>
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
> org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
>
> org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
>
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)']{code}
> Example failures:
> test_failed_snitch_update_property_file_snitch -
> [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2475/workflows/2086619e-0f21-464b-a866-84aca516b5e5/jobs/36716/tests]
> test_gcgs_validation -
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1666/testReport/junit/dtest.materialized_views_test/TestMaterializedViews/test_gcgs_validation/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18747) Fix assertion error AssertionError: Unknown keyspace system_auth\n\tat org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat org.apache.cassandra.db.Keysp
Ekaterina Dimitrova created CASSANDRA-18747:
---
Summary: Fix assertion error AssertionError: Unknown keyspace
system_auth\n\tat
org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)
Key: CASSANDRA-18747
URL: https://issues.apache.org/jira/browse/CASSANDRA-18747
Project: Cassandra
Issue Type: Task
Reporter: Ekaterina Dimitrova
I've been seeing this assertion error in different tests lately.
Full error message:
{code:java}
failed on teardown with "Unexpected error found in node logs (see stdout for
full details). Errors: [[node2] 'ERROR [PendingRangeCalculator:1] 2023-08-11
16:35:14,445 JVMStabilityInspector.java:70 - Exception in thread
Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
Unknown keyspace system_auth\n\tat
org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
java.base/java.lang.Thread.run(Thread.java:829)']" Unexpected error found in
node logs (see stdout for full details). Errors: [[node2] 'ERROR
[PendingRangeCalculator:1] 2023-08-11 16:35:14,445
JVMStabilityInspector.java:70 - Exception in thread
Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
Unknown keyspace system_auth\n\tat
org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
java.base/java.lang.Thread.run(Thread.java:829)']{code}
Example failures:
test_failed_snitch_update_property_file_snitch -
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2475/workflows/2086619e-0f21-464b-a866-84aca516b5e5/jobs/36716/tests]
test_gcgs_validation -
[https://ci-cassandra.apache.org/job/Cassandra-trunk/1666/testReport/junit/dtest.materialized_views_test/TestMaterializedViews/test_gcgs_validation/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753319#comment-17753319
]
Ekaterina Dimitrova edited comment on CASSANDRA-18708 at 8/11/23 7:14 PM:
--
One timeout on trunk and there is a failure on 5.0, assertion error that I see
in different tests lately:
{code:java}
Error Message
failed on teardown with "Failed: Unexpected error found in node logs (see
stdout for full details). Errors: [[node3] 'ERROR [PendingRangeCalculator:1]
2023-08-10 18:39:33,000 JVMStabilityInspector.java:70 - Exception in thread
Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
Unknown keyspace system_auth\n\tat
org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
java.base/java.lang.Thread.run(Thread.java:829)']"
{code}
I will open a ticket for that one.
Starting commit soon.
was (Author: e.dimitrova):
One timeout on trunk and there is a failure on 5.0, assertion error that I see
in different tests lately:
h3.
{code:java}
Error Message
failed on teardown with "Failed: Unexpected error found in node logs (see
stdout for full details). Errors: [[node3] 'ERROR [PendingRangeCalculator:1]
2023-08-10 18:39:33,000 JVMStabilityInspector.java:70 - Exception in thread
Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
Unknown keyspace system_auth\n\tat
org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
java.base/java.lang.Thread.run(Thread.java:829)']"
{code}
I will open a ticket for that one.
Starting commit soon.
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at
[jira] [Commented] (CASSANDRA-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753319#comment-17753319
]
Ekaterina Dimitrova commented on CASSANDRA-18708:
-
One timeout on trunk and there is a failure on 5.0, assertion error that I see
in different tests lately:
h3.
{code:java}
Error Message
failed on teardown with "Failed: Unexpected error found in node logs (see
stdout for full details). Errors: [[node3] 'ERROR [PendingRangeCalculator:1]
2023-08-10 18:39:33,000 JVMStabilityInspector.java:70 - Exception in thread
Thread[PendingRangeCalculator:1,5,PendingRangeCalculator]\njava.lang.AssertionError:
Unknown keyspace system_auth\n\tat
org.apache.cassandra.db.Keyspace.(Keyspace.java:324)\n\tat
org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162)\n\tat
org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat
org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:162)\n\tat
org.apache.cassandra.db.Keyspace.open(Keyspace.java:151)\n\tat
org.apache.cassandra.service.PendingRangeCalculatorService.lambda$new$1(PendingRangeCalculatorService.java:58)\n\tat
org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce.run(SingleThreadExecutorPlus.java:60)\n\tat
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
java.base/java.lang.Thread.run(Thread.java:829)']"
{code}
I will open a ticket for that one.
Starting commit soon.
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
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-18746) CircleCI: Add jobs for Java distributed tests running on Java 11, J8 builds for cassandra-4.0
[ https://issues.apache.org/jira/browse/CASSANDRA-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18746: Summary: CircleCI: Add jobs for Java distributed tests running on Java 11, J8 builds for cassandra-4.0 (was: Add jobs for Java distributed tests running on Java 11, J8 builds for cassandra-4.0) > CircleCI: Add jobs for Java distributed tests running on Java 11, J8 builds > for cassandra-4.0 > - > > Key: CASSANDRA-18746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18746 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Low > Fix For: 4.0.x > > -- 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-18503) CircleCI java distributed tests to run in Medium containers
[ https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753312#comment-17753312 ] Ekaterina Dimitrova commented on CASSANDRA-18503: - Thank you I just opened CASSANDRA-18746 I will commit on the weekend when there is less chance of collisions on commit... to many branches > CircleCI java distributed tests to run in Medium containers > --- > > Key: CASSANDRA-18503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18503 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x > > > With the paid configuration we have in-tree it is enough to run the java > distributed regular and upgrade tests in Medium containers, instead of Large > containers -- 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-18746) Add jobs for Java distributed tests running on Java 11, J8 builds for cassandra-4.0
[ https://issues.apache.org/jira/browse/CASSANDRA-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18746: Change Category: Quality Assurance Complexity: Low Hanging Fruit Component/s: CI Priority: Low (was: Normal) Status: Open (was: Triage Needed) > Add jobs for Java distributed tests running on Java 11, J8 builds for > cassandra-4.0 > --- > > Key: CASSANDRA-18746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18746 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Low > Fix For: 4.0.x > > -- 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-18746) Add jobs for Java distributed tests running on Java 11, J8 builds for cassandra-4.0
[ https://issues.apache.org/jira/browse/CASSANDRA-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18746: Fix Version/s: 4.0.x > Add jobs for Java distributed tests running on Java 11, J8 builds for > cassandra-4.0 > --- > > Key: CASSANDRA-18746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18746 > Project: Cassandra > Issue Type: Task >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x > > -- 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-18746) Add jobs for Java distributed tests running on Java 11, J8 builds for cassandra-4.0
Ekaterina Dimitrova created CASSANDRA-18746: --- Summary: Add jobs for Java distributed tests running on Java 11, J8 builds for cassandra-4.0 Key: CASSANDRA-18746 URL: https://issues.apache.org/jira/browse/CASSANDRA-18746 Project: Cassandra Issue Type: Task Reporter: Ekaterina Dimitrova -- 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 (070140327 -> 3e0e9c59a)
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 070140327 generate docs for f02aa10d add c99e80d57 Update How to commit page post CASSANDRA-18618 and 5.0 branch creation new 3e0e9c59a generate docs for c99e80d5 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 (070140327) \ N -- N -- N refs/heads/asf-staging (3e0e9c59a) 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/_/development/how_to_commit.html | 94 + content/_/development/index.html | 94 + content/search-index.js| 2 +- .../ROOT/pages/development/how_to_commit.adoc | 54 site-ui/build/ui-bundle.zip| Bin 4852435 -> 4852435 bytes 5 files changed, 195 insertions(+), 49 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18738) Update the How to Commit page after CASSANDRA-18618
[ https://issues.apache.org/jira/browse/CASSANDRA-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753307#comment-17753307 ] Ekaterina Dimitrova commented on CASSANDRA-18738: - Patch committed to trunk: [https://github.com/apache/cassandra-website/commit/c99e80d57465640b438b0a8c4d8338224c90c454] Jenkins triggered here: [https://ci-cassandra.apache.org/job/cassandra-website/1386/] > Update the How to Commit page after CASSANDRA-18618 > --- > > Key: CASSANDRA-18738 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18738 > Project: Cassandra > Issue Type: Task > Components: Legacy/Documentation and Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > In CASSANDRA-18618, checks like rat and checkstyle were moved to a separate > ant task - "check". > We need to update our How to commit page that on branches Cassandra-5.0 + we > need to run now ant realclean && ant jar build-test check pre-commit. While > on that, we already have the cassandra-5.0 branch, so that we can add that > too. -- 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 trunk updated: Update How to commit page post CASSANDRA-18618 and 5.0 branch creation
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/trunk by this push: new c99e80d57 Update How to commit page post CASSANDRA-18618 and 5.0 branch creation c99e80d57 is described below commit c99e80d57465640b438b0a8c4d8338224c90c454 Author: Ekaterina Dimitrova AuthorDate: Wed Aug 9 15:23:49 2023 -0400 Update How to commit page post CASSANDRA-18618 and 5.0 branch creation patch by Ekaterina Dimitrova; reviewed by Michael Semb Wever for CASSANDRA-18738 --- .../ROOT/pages/development/how_to_commit.adoc | 54 +++--- 1 file changed, 38 insertions(+), 16 deletions(-) diff --git a/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc b/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc index ceb8ac243..383fcf605 100644 --- a/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc +++ b/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc @@ -14,12 +14,12 @@ Hypothetical CASSANDRA-12345 ticket is a cassandra-4.0 based bug fix that requires different code for cassandra-4.0, cassandra-4.1, and trunk. Contributor Jackie supplied a patch for the root branch (12345-4.0.patch), and patches for the remaining branches -(12345-4.1.patch, 12345-trunk.patch). +(12345-4.1.patch, 12345-5.0.patch, 12345-trunk.patch). On cassandra-4.0::: . `+git am -3 12345-4.0.patch+` (any problem b/c of CHANGES.txt not merging anymore, fix it in place) - . `+ant realclean && ant jar build-test+` (rebuild to make sure code + . `+ant realclean && ant jar+` (rebuild to make sure code compiles) . `+git commit --amend+` (Notice this will squash the 4.0 applied patch into the forward merge commit) @@ -27,22 +27,30 @@ On cassandra-4.1::: . `+git merge cassandra-4.0 -s ours --log+` . `+git apply -3 12345-4.1.patch+` (any issue with CHANGES.txt : fix and [.title-ref]#git add CHANGES.txt#) - . `+ant realclean && ant jar build-test+` (rebuild to make sure code + . `+ant realclean && ant jar+` (rebuild to make sure code compiles) . `+git commit --amend+` (Notice this will squash the 4.1 applied patch into the forward merge commit) +On cassandra-5.0::: +. `+git merge cassandra-4.1 -s ours --log+` +. `+git apply -3 12345-5.0.patch+` (any issue with CHANGES.txt : fix +and [.title-ref]#git add CHANGES.txt#) +. `+ant realclean && ant jar check+` (rebuild to make sure code +compiles) +. `+git commit --amend+` (Notice this will squash the 4.1 applied +patch into the forward merge commit) On trunk::: - . `+git merge cassandra-4.1 -s ours --log+` + . `+git merge cassandra-5.0 -s ours --log+` . `+git apply -3 12345-trunk.patch+` (any issue with CHANGES.txt : fix and [.title-ref]#git add CHANGES.txt#) - . `+ant realclean && ant jar build-test+` (rebuild to make sure code + . `+ant realclean && ant jar check+` (rebuild to make sure code compiles) . `+git commit --amend+` (Notice this will squash the trunk applied patch into the forward merge commit) On any branch::: - . `+git push origin cassandra-4.0 cassandra-4.1 trunk --atomic -n+` + . `+git push origin cassandra-4.0 cassandra-4.1 cassandra-5.0 trunk --atomic -n+` (dryrun check) - . `+git push origin cassandra-4.0 cassandra-4.1 trunk --atomic+` + . `+git push origin cassandra-4.0 cassandra-4.1 cassandra-5.0 trunk --atomic+` == Git branch based Contribution @@ -51,7 +59,7 @@ Same scenario, but a branch-based contribution: On cassandra-4.0::: . `+git cherry-pick +` (any problem b/c of CHANGES.txt not merging anymore, fix it in place) - . `+ant realclean && ant jar build-test+` (rebuild to make sure code + . `+ant realclean && ant jar+` (rebuild to make sure code compiles) On cassandra-4.1::: . `+git merge cassandra-4.0 -s ours --log+` @@ -59,24 +67,34 @@ On cassandra-4.1::: format-patch and apply is [.title-ref]#cherry-pick -n#) . `+git apply -3 .patch+` (any issue with CHANGES.txt : fix and [.title-ref]#git add CHANGES.txt#) - . `+ant realclean && ant jar build-test+` (rebuild to make sure code + . `+ant realclean && ant jar+` (rebuild to make sure code compiles) . `+git commit --amend+` (Notice this will squash the 4.1 applied patch into the forward merge commit) +On cassandra-5.0::: +. `+git merge cassandra-4.1 -s ours --log+` +. `+git format-patch -1 +` (alternative to +format-patch and apply is [.title-ref]#cherry-pick -n#) +. `+git apply -3 .patch+` (any issue with +CHANGES.txt : fix and [.title-ref]#git add CHANGES.txt#) +. `+ant realclean && ant jar check+` (rebuild to make sure code +compiles) +. `+git commit --amend+` (Notice this will squash the 5.0 applied +patch into the forward merge commit) On trunk::: - . `+git merge cassandra-4.1 -s ours --log+` + . `+git merge cassandra-5.0 -s ours --log+`
[jira] [Comment Edited] (CASSANDRA-18738) Update the How to Commit page after CASSANDRA-18618
[ https://issues.apache.org/jira/browse/CASSANDRA-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752912#comment-17752912 ] Ekaterina Dimitrova edited comment on CASSANDRA-18738 at 8/11/23 6:18 PM: -- Applied the fixes. Wanna take another look, [~mck] ? Also, to confirm the website process as I haven't committed anything there for a while. We commit to trunk. This triggers Jenkins; on completion - we can see the staged website and if there is nothing wrong - merge asf-staging to asf-site. Is this still the correct process? was (Author: e.dimitrova): Applied tehe fixes. Wanna take another look, [~mck] ? Also, just to confirm the website process as I haven't committed there anything for a while. We commit to trunk. This triggers Jenkins, on completion - we can see the staged website andd if there is nothing wrong - merge asf-staging to asf-site. Is this still the correct process? > Update the How to Commit page after CASSANDRA-18618 > --- > > Key: CASSANDRA-18738 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18738 > Project: Cassandra > Issue Type: Task > Components: Legacy/Documentation and Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > In CASSANDRA-18618, checks like rat and checkstyle were moved to a separate > ant task - "check". > We need to update our How to commit page that on branches Cassandra-5.0 + we > need to run now ant realclean && ant jar build-test check pre-commit. While > on that, we already have the cassandra-5.0 branch, so that we can add that > too. -- 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-18738) Update the How to Commit page after CASSANDRA-18618
[ https://issues.apache.org/jira/browse/CASSANDRA-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753301#comment-17753301 ] Ekaterina Dimitrova commented on CASSANDRA-18738: - Great, I did not know about raw.githack.com. Thank you for explaining this to me. I will commit to cassandra-website trunk in a bit > Update the How to Commit page after CASSANDRA-18618 > --- > > Key: CASSANDRA-18738 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18738 > Project: Cassandra > Issue Type: Task > Components: Legacy/Documentation and Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > In CASSANDRA-18618, checks like rat and checkstyle were moved to a separate > ant task - "check". > We need to update our How to commit page that on branches Cassandra-5.0 + we > need to run now ant realclean && ant jar build-test check pre-commit. While > on that, we already have the cassandra-5.0 branch, so that we can add that > too. -- 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-18503) CircleCI java distributed tests to run in Medium containers
[ https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753290#comment-17753290 ] Andres de la Peña commented on CASSANDRA-18503: --- Good catch on the readme example. LGTM, +1. > CircleCI java distributed tests to run in Medium containers > --- > > Key: CASSANDRA-18503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18503 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x > > > With the paid configuration we have in-tree it is enough to run the java > distributed regular and upgrade tests in Medium containers, instead of Large > containers -- 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-18503) CircleCI java distributed tests to run in Medium containers
[ https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-18503: -- Status: Ready to Commit (was: Review In Progress) > CircleCI java distributed tests to run in Medium containers > --- > > Key: CASSANDRA-18503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18503 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x > > > With the paid configuration we have in-tree it is enough to run the java > distributed regular and upgrade tests in Medium containers, instead of Large > containers -- 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-18503) CircleCI java distributed tests to run in Medium containers
[
https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753283#comment-17753283
]
Ekaterina Dimitrova commented on CASSANDRA-18503:
-
The PRs were updated, and CI successfully completed the repeated jobs with the
expected resources.
3.11:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2477/workflows/211f06ca-7745-4658-8be8-e088b35f7ad5]
4.0:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2469/workflows/4f3c4f17-dc6f-49de-9ac2-0b14f108dc86]
4.1:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2470/workflows/e724bf10-f00a-4ff6-b5d2-0092ab3ff6df]
5.0:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2473/workflows/b9d2998d-ef3b-4283-9c35-cd02c895fe7e]
trunk:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2472/workflows/bdae68e9-5cd5-4408-8160-a96df0f62260]
I also fixed a test name in the readme of cassandra-3.11. The example was on a
non-existent test.
Also:
{quote}[One of the
containers|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2464/workflows/f94292ac-74c9-443f-a4c4-d20c177935ac/jobs/35666/tests]
for the job java11_separate_tests.j11_jvm_dtests in 4.0 seems to have timed
out, we should probably run it again:
[https://app.circleci.com/pipelines/github/adelapena/cassandra/3102/workflows/c06f68a7-f3ac-4518-9802-44c6da9c286a]
{quote}
Thank you for re-running. It is completed as expected now. The test failure is
known from - CASSANDRA-18366
> CircleCI java distributed tests to run in Medium containers
> ---
>
> Key: CASSANDRA-18503
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18503
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x
>
>
> With the paid configuration we have in-tree it is enough to run the java
> distributed regular and upgrade tests in Medium containers, instead of Large
> containers
--
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-18021) Flaky org.apache.cassandra.distributed.test.ReprepareTestOldBehaviour#testReprepareMixedVersionWithoutReset
[
https://issues.apache.org/jira/browse/CASSANDRA-18021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753282#comment-17753282
]
Doug Rohrer commented on CASSANDRA-18021:
-
Just hit this again, this time in 3.11
[https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/166/workflows/a95dcfe8-bc62-473d-a8fc-edb5e5ae0296/jobs/6459/tests]
> Flaky
> org.apache.cassandra.distributed.test.ReprepareTestOldBehaviour#testReprepareMixedVersionWithoutReset
> ---
>
> Key: CASSANDRA-18021
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18021
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.11.x
>
>
> {code:java}
> testReprepareMixedVersionWithoutReset
> com.datastax.driver.core.exceptions.InvalidQueryException: MD5 hash
> collision: query with the same MD5 hash was already prepared.
> Existing: ''
> at
> com.datastax.driver.core.exceptions.InvalidQueryException.copy(InvalidQueryException.java:50)
> at
> com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
> at
> com.datastax.driver.core.AbstractSession.prepare(AbstractSession.java:98)
> at
> org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest.testReprepareMixedVersionWithoutReset(ReprepareOldBehaviourTest.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
> at
> com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
> at
> com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:235)
> at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:54)
> Caused by: com.datastax.driver.core.exceptions.InvalidQueryException: MD5
> hash collision: query with the same MD5 hash was already prepared.
> Existing: ''
> at
> com.datastax.driver.core.Responses$Error.asException(Responses.java:136)
> at
> com.datastax.driver.core.SessionManager$4.apply(SessionManager.java:220)
> at
> com.datastax.driver.core.SessionManager$4.apply(SessionManager.java:196)
> at
> com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:906)
> at com.google.common.util.concurrent.Futures$1$1.run(Futures.java:635)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> this throws:
> {code}
> lbp.setPrimary(firstContact);
> final PreparedStatement select = session.prepare(withKeyspace("SELECT * FROM
> %s.tbl")); /// THIS
> session.execute(select.bind());
> {code}
> I observed this in 3.11.
>
[jira] [Updated] (CASSANDRA-18738) Update the How to Commit page after CASSANDRA-18618
[ https://issues.apache.org/jira/browse/CASSANDRA-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18738: Status: Ready to Commit (was: Review In Progress) > Update the How to Commit page after CASSANDRA-18618 > --- > > Key: CASSANDRA-18738 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18738 > Project: Cassandra > Issue Type: Task > Components: Legacy/Documentation and Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > In CASSANDRA-18618, checks like rat and checkstyle were moved to a separate > ant task - "check". > We need to update our How to commit page that on branches Cassandra-5.0 + we > need to run now ant realclean && ant jar build-test check pre-commit. While > on that, we already have the cassandra-5.0 branch, so that we can add that > too. -- 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-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753275#comment-17753275
]
Ekaterina Dimitrova commented on CASSANDRA-18708:
-
Patch approved on GH, and approval to commit confirmed in Slack.
Rebased 5.0 and trunk and running final CI:
5.0 -
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18708-5.0]
run #2475
trunk -
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18708-trunk]
run #2476
Pending commit on clean CI runs.
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
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-18738) Update the How to Commit page after CASSANDRA-18618
[ https://issues.apache.org/jira/browse/CASSANDRA-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753270#comment-17753270 ] Michael Semb Wever commented on CASSANDRA-18738: +1 on new changes > Update the How to Commit page after CASSANDRA-18618 > --- > > Key: CASSANDRA-18738 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18738 > Project: Cassandra > Issue Type: Task > Components: Legacy/Documentation and Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > In CASSANDRA-18618, checks like rat and checkstyle were moved to a separate > ant task - "check". > We need to update our How to commit page that on branches Cassandra-5.0 + we > need to run now ant realclean && ant jar build-test check pre-commit. While > on that, we already have the cassandra-5.0 branch, so that we can add that > too. -- 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-18738) Update the How to Commit page after CASSANDRA-18618
[ https://issues.apache.org/jira/browse/CASSANDRA-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753267#comment-17753267 ] Michael Semb Wever commented on CASSANDRA-18738: bq. We commit to trunk. This triggers Jenkins, on completion - we can see the staged website andd if there is nothing wrong - merge asf-staging to asf-site. Is this still the correct process? That's correct. But this patch is on cassandra-website repo. Commits to that repo trigger CI too. We also have pre-commit CI in github for cassandra-website commits, for example in your fork your commits will have checks, like this: https://github.com/ekaterinadimitrova2/cassandra-website/actions/runs/5825288289/job/15796474462 And it generates a (just top-level) website in the _generated branch, e.g. https://github.com/ekaterinadimitrova2/cassandra-website/blob/18738-trunk_generated/content/_/development/how_to_commit.html You can take the raw url of that and put it into raw.githack.com , e.g. https://raw.githack.com/ekaterinadimitrova2/cassandra-website/18738-trunk_generated/content/_/development/how_to_commit.html to preview the generated output. > Update the How to Commit page after CASSANDRA-18618 > --- > > Key: CASSANDRA-18738 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18738 > Project: Cassandra > Issue Type: Task > Components: Legacy/Documentation and Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > In CASSANDRA-18618, checks like rat and checkstyle were moved to a separate > ant task - "check". > We need to update our How to commit page that on branches Cassandra-5.0 + we > need to run now ant realclean && ant jar build-test check pre-commit. While > on that, we already have the cassandra-5.0 branch, so that we can add that > too. -- 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-18741) Some unit tests create a heap dump each time
[ https://issues.apache.org/jira/browse/CASSANDRA-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18741: - Fix Version/s: (was: 5.x) > Some unit tests create a heap dump each time > > > Key: CASSANDRA-18741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18741 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Brandon Williams >Assignee: Caleb Rackliffe >Priority: Normal > Fix For: 5.0 > > > I noticed this by running out of space while working on CASSANDRA-18706. > Something must be calling HeaupUtils.maybeCreateHeapDump because the > build/test directory is littered with pid-epoch.hprof files > despite the tests not crashing. I checked a couple other random tests, > RandomSchemaTest also generates a dump but KeywordSplitTest does not. > This behavior does not occur on 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-18741) Some unit tests create a heap dump each time
[ https://issues.apache.org/jira/browse/CASSANDRA-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-18741: Fix Version/s: 5.0 Since Version: 5.0 Source Control Link: https://github.com/apache/cassandra/commit/f8d4e2a3c80d5d2be1e270e7ac601f4bc0a17fe7 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed in https://github.com/apache/cassandra/commit/f8d4e2a3c80d5d2be1e270e7ac601f4bc0a17fe7 > Some unit tests create a heap dump each time > > > Key: CASSANDRA-18741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18741 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Brandon Williams >Assignee: Caleb Rackliffe >Priority: Normal > Fix For: 5.0, 5.x > > > I noticed this by running out of space while working on CASSANDRA-18706. > Something must be calling HeaupUtils.maybeCreateHeapDump because the > build/test directory is littered with pid-epoch.hprof files > despite the tests not crashing. I checked a couple other random tests, > RandomSchemaTest also generates a dump but KeywordSplitTest does not. > This behavior does not occur on 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-18741) Some unit tests create a heap dump each time
[ https://issues.apache.org/jira/browse/CASSANDRA-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18741: - Fix Version/s: 5.1.x > Some unit tests create a heap dump each time > > > Key: CASSANDRA-18741 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18741 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Brandon Williams >Assignee: Caleb Rackliffe >Priority: Normal > Fix For: 5.0, 5.1.x > > > I noticed this by running out of space while working on CASSANDRA-18706. > Something must be calling HeaupUtils.maybeCreateHeapDump because the > build/test directory is littered with pid-epoch.hprof files > despite the tests not crashing. I checked a couple other random tests, > RandomSchemaTest also generates a dump but KeywordSplitTest does not. > This behavior does not occur on 4.1. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (7022d1a5e6 -> 5ade7a6cd8)
This is an automated email from the ASF dual-hosted git repository. maedhroz pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 7022d1a5e6 Merge branch 'cassandra-5.0' into trunk new f8d4e2a3c8 Disable heap dump creation by default on crash for tests that use test/conf/cassandra.yaml new 5ade7a6cd8 Merge branch 'cassandra-5.0' into trunk The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: test/conf/cassandra.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository. maedhroz pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 5ade7a6cd8f5e0ca1a633032e935f7148f853be6 Merge: 7022d1a5e6 f8d4e2a3c8 Author: Caleb Rackliffe AuthorDate: Fri Aug 11 10:37:37 2023 -0500 Merge branch 'cassandra-5.0' into trunk * cassandra-5.0: Disable heap dump creation by default on crash for tests that use test/conf/cassandra.yaml test/conf/cassandra.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-5.0 updated: Disable heap dump creation by default on crash for tests that use test/conf/cassandra.yaml
This is an automated email from the ASF dual-hosted git repository. maedhroz pushed a commit to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-5.0 by this push: new f8d4e2a3c8 Disable heap dump creation by default on crash for tests that use test/conf/cassandra.yaml f8d4e2a3c8 is described below commit f8d4e2a3c80d5d2be1e270e7ac601f4bc0a17fe7 Author: Caleb Rackliffe AuthorDate: Thu Aug 10 10:56:30 2023 -0500 Disable heap dump creation by default on crash for tests that use test/conf/cassandra.yaml patch by Caleb Rackliffe; reviewed by Brandon Williams and Ekaterina Dimitrova for CASSANDRA-18741 --- test/conf/cassandra.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/conf/cassandra.yaml b/test/conf/cassandra.yaml index 379792a662..0e0da455a9 100644 --- a/test/conf/cassandra.yaml +++ b/test/conf/cassandra.yaml @@ -56,7 +56,7 @@ full_query_logging_options: auto_hints_cleanup_enabled: true heap_dump_path: build/test -dump_heap_on_uncaught_exception: true +dump_heap_on_uncaught_exception: false read_thresholds_enabled: true coordinator_read_size_warn_threshold: 1024KiB - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18708:
Reviewers: Benjamin Lerer (was: Benjamin Lerer, Ekaterina Dimitrova)
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
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-in-jvm-dtest-api] branch trunk updated: CASSANDRA-18727 - JMXUtil.getJmxConnector should retry connection attempts (#37)
This is an automated email from the ASF dual-hosted git repository.
ifesdjeen pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git
The following commit(s) were added to refs/heads/trunk by this push:
new f3a3b98 CASSANDRA-18727 - JMXUtil.getJmxConnector should retry
connection attempts (#37)
f3a3b98 is described below
commit f3a3b982227602ec0752a5d0d4d780dc62ac3f6d
Author: Doug Rohrer <682821+jeetkund...@users.noreply.github.com>
AuthorDate: Fri Aug 11 10:46:44 2023 -0400
CASSANDRA-18727 - JMXUtil.getJmxConnector should retry connection attempts
(#37)
JMXUtil.getJmxConnector should retry connection attempts
Patch by Doug Roher for CASSANDRA-18727. Reviewed by Jon Meredith and
Francisco Guerrero.
---
.../cassandra/distributed/api/LogAction.java | 30 +---
.../cassandra/distributed/shared/JMXUtil.java | 90 --
.../distributed/shared/Uninterruptibles.java | 48
3 files changed, 134 insertions(+), 34 deletions(-)
diff --git a/src/main/java/org/apache/cassandra/distributed/api/LogAction.java
b/src/main/java/org/apache/cassandra/distributed/api/LogAction.java
index 8f9e693..7b90ffc 100644
--- a/src/main/java/org/apache/cassandra/distributed/api/LogAction.java
+++ b/src/main/java/org/apache/cassandra/distributed/api/LogAction.java
@@ -30,6 +30,8 @@ import java.util.function.Predicate;
import java.util.regex.Matcher;
import java.util.regex.Pattern;
+import org.apache.cassandra.distributed.shared.Uninterruptibles;
+
public interface LogAction
{
/**
@@ -56,7 +58,7 @@ public interface LogAction
if (previousPosition == mark())
{
// still matching... wait a bit
-Internal.sleepUninterruptibly(1, TimeUnit.SECONDS);
+Uninterruptibles.sleepUninterruptibly(1, TimeUnit.SECONDS);
continue;
}
// position not matching, try to read
@@ -340,7 +342,7 @@ public interface LogAction
'}';
}
}
-
+
class Internal
{
private static final int DEFAULT_START_POSITION = -1;
@@ -388,29 +390,5 @@ public interface LogAction
{
return regexPredicate(Pattern.compile(pattern));
}
-
-private static void sleepUninterruptibly(long sleepFor, TimeUnit unit)
{
-// copied from guava since dtest can't depend on guava
-boolean interrupted = false;
-
-try {
-long remainingNanos = unit.toNanos(sleepFor);
-long end = System.nanoTime() + remainingNanos;
-
-while(true) {
-try {
-TimeUnit.NANOSECONDS.sleep(remainingNanos);
-return;
-} catch (InterruptedException var12) {
-interrupted = true;
-remainingNanos = end - System.nanoTime();
-}
-}
-} finally {
-if (interrupted) {
-Thread.currentThread().interrupt();
-}
-}
-}
}
}
diff --git a/src/main/java/org/apache/cassandra/distributed/shared/JMXUtil.java
b/src/main/java/org/apache/cassandra/distributed/shared/JMXUtil.java
index 183397e..c505201 100644
--- a/src/main/java/org/apache/cassandra/distributed/shared/JMXUtil.java
+++ b/src/main/java/org/apache/cassandra/distributed/shared/JMXUtil.java
@@ -18,11 +18,16 @@
package org.apache.cassandra.distributed.shared;
-import java.io.IOException;
+import java.net.MalformedURLException;
+import java.util.Map;
+import java.util.concurrent.TimeUnit;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.remote.JMXServiceURL;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
import org.apache.cassandra.distributed.api.IInstanceConfig;
public final class JMXUtil
@@ -31,23 +36,92 @@ public final class JMXUtil
{
}
+private final static Logger LOGGER =
LoggerFactory.getLogger(JMXUtil.class);
+
public static final String JMX_SERVICE_URL_FMT =
"service:jmx:rmi:///jndi/rmi://%s:%d/jmxrmi";
+/**
+ * Create an instance of a {@link JMXConnector} to an in-jvm instance
based on the input configuration.
+ * This overload uses 5 as the default number of retries which has been
shown to be adequate in testing,
+ * and passes a null environment map to the connect call.
+ * @param config The instance configuration to use to get the necessary
parameters to connect
+ * @return A JMXConnector instance which can communicate with the
specified instance via JMX
+ */
public static JMXConnector getJmxConnector(IInstanceConfig config) {
+return getJmxConnector(config, 5, null);
+}
+
+/**
+ * Create an instance of a {@link
[jira] [Updated] (CASSANDRA-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18708:
Reviewers: Benjamin Lerer, Ekaterina Dimitrova (was: Benjamin Lerer)
Status: Review In Progress (was: Patch Available)
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
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-18708) Test failure: org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18708:
Status: Ready to Commit (was: Review In Progress)
> Test failure:
> org.apache.cassandra.tools.StandaloneSplitterWithCQLTesterTest.testNoSnapshotOption-.jdk17
>
>
> Key: CASSANDRA-18708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18708
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit/org.apache.cassandra.tools/StandaloneSplitterWithCQLTesterTest/testNoSnapshotOption__jdk17/]
> h3.
> {code:java}
> Error Message
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final sun.nio.fs.UnixFileSystem sun.nio.fs.UnixPath.fs accessible: module
> java.base does not "opens sun.nio.fs" to unnamed module @1f28c152 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
> org.apache.cassandra.utils.concurrent.Ref.getFields(Ref.java:656) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.traverse(Ref.java:613) at
> org.apache.cassandra.utils.concurrent.Ref$Visitor.run(Ref.java:568) at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
--
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-18666) [Doc] Add to virtual table documentation that a minimum cq;lsh version is needed
[ https://issues.apache.org/jira/browse/CASSANDRA-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753247#comment-17753247 ] Brandon Williams commented on CASSANDRA-18666: -- I created CASSANDRA-18745 to emit a warning on version mismatch. > [Doc] Add to virtual table documentation that a minimum cq;lsh version is > needed > > > Key: CASSANDRA-18666 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18666 > Project: Cassandra > Issue Type: New Feature >Reporter: German Eichberger >Priority: Normal > > See [https://the-asf.slack.com/archives/CJZLTM05A/p1686771286554899] for > details. > > Add some warning on top of > [https://cassandra.apache.org/doc/4.1/cassandra/new/virtualtables.html] that > protocol version v5 is needed > > -- 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-18745) cqlsh should warn on server version mismatch
[ https://issues.apache.org/jira/browse/CASSANDRA-18745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753245#comment-17753245 ] Brandon Williams commented on CASSANDRA-18745: -- The way I currently imagine this working is having Ant write "version = $version" to something like pylib/cqlshlib/serverversion.py, which cqlsh can then import and compare against the server version it has connected to. > cqlsh should warn on server version mismatch > > > Key: CASSANDRA-18745 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18745 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x > > > When cqlsh is used against a different version of the server than the one > that it shipped with, it should emit a warning so that users aren't confused > when some things don't work correctly. -- 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-18745) cqlsh should warn on server version mismatch
[ https://issues.apache.org/jira/browse/CASSANDRA-18745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18745: - Change Category: Operability Complexity: Normal Component/s: CQL/Interpreter Fix Version/s: 3.0.x 3.11.x 4.0.x 4.1.x 5.x Status: Open (was: Triage Needed) > cqlsh should warn on server version mismatch > > > Key: CASSANDRA-18745 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18745 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x > > > When cqlsh is used against a different version of the server than the one > that it shipped with, it should emit a warning so that users aren't confused > when some things don't work correctly. -- 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-18745) cqlsh should warn on server version mismatch
Brandon Williams created CASSANDRA-18745: Summary: cqlsh should warn on server version mismatch Key: CASSANDRA-18745 URL: https://issues.apache.org/jira/browse/CASSANDRA-18745 Project: Cassandra Issue Type: Improvement Reporter: Brandon Williams When cqlsh is used against a different version of the server than the one that it shipped with, it should emit a warning so that users aren't confused when some things don't work correctly. -- 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-18725) IsolatedJMX should not release all TCPEndpoints on instance shutdown
[ https://issues.apache.org/jira/browse/CASSANDRA-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer updated CASSANDRA-18725: Fix Version/s: 3.11.x 5.1 > IsolatedJMX should not release all TCPEndpoints on instance shutdown > > > Key: CASSANDRA-18725 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18725 > Project: Cassandra > Issue Type: Improvement >Reporter: Doug Rohrer >Priority: Normal > Fix For: 3.11.x, 4.0, 4.1.x, 5.0, 5.1 > > Time Spent: 50m > Remaining Estimate: 0h > > In the original implementation of the JMX feature, we fixed some memory leaks > by clearing some internal state in Java’s TCPEndpoint. However, that > implementation was overly aggressive and cleared the whole map, vs. just > removing the endpoints created by the individual instances. This causes > issues when you remove a node from the cluster (as all of the endpoints are > cleared, not just the ones in use by that instance). > > In stead, we should check if the endpoint was created by the instance in > question and only remove it if it was. -- 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-18725) IsolatedJMX should not release all TCPEndpoints on instance shutdown
[ https://issues.apache.org/jira/browse/CASSANDRA-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753244#comment-17753244 ] Doug Rohrer commented on CASSANDRA-18725: - These PRs are waiting on the in-jvm dtest framework 0.0.16 snapshot release ([https://github.com/apache/cassandra-in-jvm-dtest-api/pull/37]) which [~djoshi] is working on or will be in the next day or so. Once that's done, we'll start the vote for the dtest-api release and these PRs can run on the snapshot in CircleCI. Before merging, we need to get the official 0.0.16 release done and change the references to 0.0.16-SNAPSHOT in all of the ant files, and then make sure not to commit the use of the SNAPSHOT repository. > IsolatedJMX should not release all TCPEndpoints on instance shutdown > > > Key: CASSANDRA-18725 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18725 > Project: Cassandra > Issue Type: Improvement >Reporter: Doug Rohrer >Priority: Normal > Fix For: 4.0, 4.1.x, 5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > In the original implementation of the JMX feature, we fixed some memory leaks > by clearing some internal state in Java’s TCPEndpoint. However, that > implementation was overly aggressive and cleared the whole map, vs. just > removing the endpoints created by the individual instances. This causes > issues when you remove a node from the cluster (as all of the endpoints are > cleared, not just the ones in use by that instance). > > In stead, we should check if the endpoint was created by the instance in > question and only remove it if it was. -- 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-18503) CircleCI java distributed tests to run in Medium containers
[ https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18503: Description: With the paid configuration we have in-tree it is enough to run the java distributed regular and upgrade tests in Medium containers, instead of Large containers (was: With the paid configuration we have in-tree it is enough to run the java distributed upgrade tests in Medium containers, instead of Large containers) > CircleCI java distributed tests to run in Medium containers > --- > > Key: CASSANDRA-18503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18503 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x > > > With the paid configuration we have in-tree it is enough to run the java > distributed regular and upgrade tests in Medium containers, instead of Large > containers -- 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-18503) CircleCI java distributed tests to run in Medium containers
[
https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753228#comment-17753228
]
Ekaterina Dimitrova commented on CASSANDRA-18503:
-
{quote}I think the executor for repeated JVM upgrade dtests should also use
{{medium}} containers, instead of the current {{large}} containers.
{quote}
Good point, I will do it, thanks
> CircleCI java distributed tests to run in Medium containers
> ---
>
> Key: CASSANDRA-18503
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18503
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x
>
>
> With the paid configuration we have in-tree it is enough to run the java
> distributed upgrade tests in Medium containers, instead of Large containers
--
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-18739) UDF functions fail to load on rolling restart
[
https://issues.apache.org/jira/browse/CASSANDRA-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753229#comment-17753229
]
Claude Warren commented on CASSANDRA-18739:
---
Fixes and test code for v4.0 in
[https://github.com/claudenw/cassandra/tree/CASSANDRA-18739_v4.0]
Fixes and test code for v4.1 in
[https://github.com/claudenw/cassandra/tree/CASSANDRA-18739_v4.1]
I will open pull requests next week.
> UDF functions fail to load on rolling restart
> -
>
> Key: CASSANDRA-18739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18739
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/UDF
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Normal
> Attachments: udf_error.cql, udf_error_data.cql
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> UDFs fail to reload properly after a rolling restart.
> h3. *Symptom:*
> NPE thrown when used after restart.
> h3. *Steps to recreate:*
> # Create a cluster as per cql file
> # Populate the cluster with data.cql.
> # Execute SELECT city_measurements(city, measurement, 16.5) AS m FROM current
> # expect min and max values for cities.
> # Performing a rolling restart on one server.
> # When the server is back up
> # Execute SELECT city_measurements(city, measurement, 16.5) AS m FROM current
> # expect: error result with NPE message.
> {*}Analysis{*}:
> During system restart the SchemaKeyspace.fetchNonSystemKeyspaces() is called,
> when a keyspace with a UDF is loaded the SchemaKeyspace method
> createUDFFromRow() is called, this in turn calls UDFunction.create() which
> eventually calls back to UDFunction constructor where the
> Schema.instance.getKeyspaceMetadata() is called with the keyspace for the UDF
> name as the argument. However, the keyspace for the UDF name is being
> constructed and is not yet in the instance so the method returns null for the
> KeyspaceMetadata. That null KeyspaceMetadata is then used in the udfContext.
> Later when the UDF method is called, if there is a need to call a method on
> the keyspaceMetadata, such as udfContext.newUDTValue() where the
> implementation uses keyspaceMetadata.types, a null pointer is thrown.
> I have verified this affects version 4.0, 4.1 and trunk. I have not verified
> 3.x but I suspect it is the same there.
> I modified UDFunction constructor to assert that the metadata was not null
> and received the following stack trace
> ERROR [main] 2023-08-09 11:44:46,408 CassandraDaemon.java:911 - Exception
> encountered during startup
> java.lang.AssertionError: No metadata for temperatures.city_measurements_sfunc
> at
> org.apache.cassandra.cql3.functions.UDFunction.(UDFunction.java:240)
> at
> org.apache.cassandra.cql3.functions.JavaBasedUDFunction.(JavaBasedUDFunction.java:195)
> at
> org.apache.cassandra.cql3.functions.UDFunction.create(UDFunction.java:276)
> at
> org.apache.cassandra.schema.SchemaKeyspace.createUDFFromRow(SchemaKeyspace.java:1182)
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchUDFs(SchemaKeyspace.java:1131)
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchFunctions(SchemaKeyspace.java:1119)
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspace(SchemaKeyspace.java:859)
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspacesWithout(SchemaKeyspace.java:848)
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchNonSystemKeyspaces(SchemaKeyspace.java:836)
> at org.apache.cassandra.schema.Schema.loadFromDisk(Schema.java:132)
> at org.apache.cassandra.schema.Schema.loadFromDisk(Schema.java:121)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:287)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:765)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:889)
>
> {{*Possible solution:*}}
> *Version 4.x*
> Create a KeyspaceMetadata.Builder class that uses accepts the types, tables
> and views but uses a builder for the functions.
> Add a KeyspaceMetadata constructor to accept the KeyspaceMetadata.Builder so
> that the function builder keyspaceMetadata value can be set correctly during
> construction of the KeyspaceMetadata.
> Modify SchemaKeyspace.fetchKeyspace(string) so that it uses the
> KeyspaceMetadata.Builder.
>
> *Version 5.x*
> Similar to 4.x except that the KeyspaceMetadata.Builder will have to have
> builders for Views and Tables because the functions necessary to construct
> those objects will not be available until the KeyspaceMetadata.Builder
> constructs it.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe,
[jira] [Assigned] (CASSANDRA-18360) Test Failure: o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
[
https://issues.apache.org/jira/browse/CASSANDRA-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-18360:
Assignee: Brandon Williams
> Test Failure:
> o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
> ---
>
> Key: CASSANDRA-18360
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18360
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test
> {{org.apache.cassandra.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName}}
> is flaky at least on trunk. Flakiness seems lesser than 1%.
> While I haven't seen it on Jenkins yet, it can easily be reproduced on
> CircleCI with the multiplexer:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32235
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32234
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/739a95d3-8e42-4447-93dd-122fc16fdd7d/jobs/32233/tests
> Those runs show two types of errors:
> {code}
> junit.framework.AssertionFailedError: Invalid value for row 0 column 1
> (content of type text), expected but got
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1506)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> {code}
> and:
> {code}
> org.apache.cassandra.serializers.MarshalException: Invalid UTF-8 bytes
> 00e0279515437f00
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:46)
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:29)
> at
> org.apache.cassandra.serializers.TypeSerializer.deserialize(TypeSerializer.java:37)
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1494)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_UTESTS_COUNT=500 \
> -e REPEATED_UTESTS=org.apache.cassandra.cql3.validation.operations.AlterTest
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18503) CircleCI java distributed tests to run in Medium containers
[ https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-18503: -- Reviewers: Andres de la Peña > CircleCI java distributed tests to run in Medium containers > --- > > Key: CASSANDRA-18503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18503 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x > > > With the paid configuration we have in-tree it is enough to run the java > distributed upgrade tests in Medium containers, instead of Large containers -- 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-18503) CircleCI java distributed tests to run in Medium containers
[
https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753208#comment-17753208
]
Andres de la Peña commented on CASSANDRA-18503:
---
I think the executor for repeated JVM upgrade dtests should also use {{medium}}
containers, instead of the current {{large}} containers.
As for the CI runs, all failures seem known:
* testDropCompactWithClusteringAndValueColumn is [in
Butler|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-3.11/failure/org.apache.cassandra.distributed.upgrade/DropCompactStorageWithClusteringAndValueColumnTest/testDropCompactWithClusteringAndValueColumn]
* testDropCompactWithClusteringAndValueColumnWithDeletesAndWrites is [in
Butler|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-3.11/failure/org.apache.cassandra.distributed.upgrade/DropCompactStorageWithDeletesAndWritesTest/testDropCompactWithClusteringAndValueColumnWithDeletesAndWrites]
* testReprepareMixedVersionWithoutReset is CASSANDRA-18021
* testFailingMessage is CASSANDRA-18366
* mixedModeReadColumnSubsetDigestCheck is CASSANDRA-18158
[One of the
containers|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2464/workflows/f94292ac-74c9-443f-a4c4-d20c177935ac/jobs/35666/tests]
for the job java11_separate_tests.j11_jvm_dtests in 4.0 seems to have timed
out, we should probably run it again:
https://app.circleci.com/pipelines/github/adelapena/cassandra/3102/workflows/c06f68a7-f3ac-4518-9802-44c6da9c286a
> CircleCI java distributed tests to run in Medium containers
> ---
>
> Key: CASSANDRA-18503
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18503
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x
>
>
> With the paid configuration we have in-tree it is enough to run the java
> distributed upgrade tests in Medium containers, instead of Large containers
--
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-18503) CircleCI java distributed tests to run in Medium containers
[ https://issues.apache.org/jira/browse/CASSANDRA-18503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-18503: -- Status: Review In Progress (was: Patch Available) > CircleCI java distributed tests to run in Medium containers > --- > > Key: CASSANDRA-18503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18503 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x, 5.1.x > > > With the paid configuration we have in-tree it is enough to run the java > distributed upgrade tests in Medium containers, instead of Large containers -- 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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-18743: Fix Version/s: 5.0 > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753205#comment-17753205 ] Maxim Muzafarov commented on CASSANDRA-18743: - [~brandon.williams] Agree. Changes for the trunk: https://github.com/apache/cassandra/pull/2575 Changes for the 5.0: https://github.com/apache/cassandra/pull/2576 > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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-18158) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck
[
https://issues.apache.org/jira/browse/CASSANDRA-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18158:
-
Fix Version/s: 4.0.x
4.1.x
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck
> -
>
> Key: CASSANDRA-18158
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18158
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Flakey.
> {noformat}
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.UnavailableException: Cannot achieve
> consistency level ALL
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.waitOn(IsolatedExecutor.java:218)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeWithTracing(Coordinator.java:125)
> at
> org.apache.cassandra.distributed.test.ReadDigestConsistencyTest.checkTraceForDigestMismatch(ReadDigestConsistencyTest.java:63)
> at
> org.apache.cassandra.distributed.test.ReadDigestConsistencyTest.testDigestConsistency(ReadDigestConsistencyTest.java:105)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.lambda$mixedModeReadColumnSubsetDigestCheck$2(MixedModeReadTest.java:60)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:222)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck(MixedModeReadTest.java:63)
> Caused by: org.apache.cassandra.exceptions.UnavailableException: Cannot
> achieve consistency level ALL
> at
> org.apache.cassandra.db.ConsistencyLevel.assureSufficientLiveNodes(ConsistencyLevel.java:334)
> at
> org.apache.cassandra.service.AbstractReadExecutor.getReadExecutor(AbstractReadExecutor.java:162)
> at
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.(StorageProxy.java:1897)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1859)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1802)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1707)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1221)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:315)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:285)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:117)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeInternal(Coordinator.java:106)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$asyncExecuteWithTracingWithResult$1(Coordinator.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:84)
> at java.lang.Thread.run(Thread.java:750)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18158) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck
[
https://issues.apache.org/jira/browse/CASSANDRA-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18158:
-
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990)
Complexity: Normal
Discovered By: DTest
Severity: Normal
Status: Open (was: Triage Needed)
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck
> -
>
> Key: CASSANDRA-18158
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18158
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Flakey.
> {noformat}
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.UnavailableException: Cannot achieve
> consistency level ALL
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.waitOn(IsolatedExecutor.java:218)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeWithTracing(Coordinator.java:125)
> at
> org.apache.cassandra.distributed.test.ReadDigestConsistencyTest.checkTraceForDigestMismatch(ReadDigestConsistencyTest.java:63)
> at
> org.apache.cassandra.distributed.test.ReadDigestConsistencyTest.testDigestConsistency(ReadDigestConsistencyTest.java:105)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.lambda$mixedModeReadColumnSubsetDigestCheck$2(MixedModeReadTest.java:60)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:222)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck(MixedModeReadTest.java:63)
> Caused by: org.apache.cassandra.exceptions.UnavailableException: Cannot
> achieve consistency level ALL
> at
> org.apache.cassandra.db.ConsistencyLevel.assureSufficientLiveNodes(ConsistencyLevel.java:334)
> at
> org.apache.cassandra.service.AbstractReadExecutor.getReadExecutor(AbstractReadExecutor.java:162)
> at
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.(StorageProxy.java:1897)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1859)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1802)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1707)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1221)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:315)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:285)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:117)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeInternal(Coordinator.java:106)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$asyncExecuteWithTracingWithResult$1(Coordinator.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:84)
> at java.lang.Thread.run(Thread.java:750)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-18743: Fix Version/s: 5.x > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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-18158) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck
[
https://issues.apache.org/jira/browse/CASSANDRA-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753202#comment-17753202
]
Andres de la Peña commented on CASSANDRA-18158:
---
Seen on 4.0 and 4.1 too, with medium containers:
* 4.0:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2464/workflows/571234a7-8164-4ddc-a7c7-30fb9cbbff24/jobs/35670/tests|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2464/workflows/571234a7-8164-4ddc-a7c7-30fb9cbbff24/jobs/35670/tests]
* 4.1:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2465/workflows/1be8014c-acfc-40e6-b0d0-6dff62ca32dd/jobs/35765/tests]
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck
> -
>
> Key: CASSANDRA-18158
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18158
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 3.11.x, 5.x
>
>
> Flakey.
> {noformat}
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.UnavailableException: Cannot achieve
> consistency level ALL
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.waitOn(IsolatedExecutor.java:218)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeWithTracing(Coordinator.java:125)
> at
> org.apache.cassandra.distributed.test.ReadDigestConsistencyTest.checkTraceForDigestMismatch(ReadDigestConsistencyTest.java:63)
> at
> org.apache.cassandra.distributed.test.ReadDigestConsistencyTest.testDigestConsistency(ReadDigestConsistencyTest.java:105)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.lambda$mixedModeReadColumnSubsetDigestCheck$2(MixedModeReadTest.java:60)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:222)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck(MixedModeReadTest.java:63)
> Caused by: org.apache.cassandra.exceptions.UnavailableException: Cannot
> achieve consistency level ALL
> at
> org.apache.cassandra.db.ConsistencyLevel.assureSufficientLiveNodes(ConsistencyLevel.java:334)
> at
> org.apache.cassandra.service.AbstractReadExecutor.getReadExecutor(AbstractReadExecutor.java:162)
> at
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.(StorageProxy.java:1897)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1859)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1802)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1707)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1221)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:315)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:285)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:117)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeInternal(Coordinator.java:106)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$asyncExecuteWithTracingWithResult$1(Coordinator.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:84)
> at java.lang.Thread.run(Thread.java:750)
> {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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753200#comment-17753200 ] Brandon Williams commented on CASSANDRA-18743: -- Seems like we should deprecate this in 5.0 and remove it in trunk since it's user-facing. > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753198#comment-17753198 ] Maxim Muzafarov commented on CASSANDRA-18743: - [~aratnofsky] Can you take a look at the PR, please? > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-18743: Test and Documentation Plan: Documentation updated accordingly, no test plan is required. Status: Patch Available (was: Open) > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-18743: Change Category: Code Clarity Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned CASSANDRA-18743: --- Assignee: Maxim Muzafarov > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Assignee: Maxim Muzafarov >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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-18743) Remove dependency on archived project metrics-reporter-config
[ https://issues.apache.org/jira/browse/CASSANDRA-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753196#comment-17753196 ] Maxim Muzafarov commented on CASSANDRA-18743: - We use Dropwizard Metrics, the library itself provides a lot of different metrics reporters that can be used instead. For example: https://metrics.dropwizard.io/4.2.0/manual/core.html#man-core-reporters-csv > Remove dependency on archived project metrics-reporter-config > - > > Key: CASSANDRA-18743 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18743 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: Abe Ratnofsky >Priority: Normal > > metrics-reporter-config has been archived for over 3 years, and has received > no updates in nearly 6 years: > https://github.com/addthis/metrics-reporter-config > metrics-reporter-config processes YAML unsafely: > https://github.com/addthis/metrics-reporter-config/blob/master/reporter-config-base/src/main/java/com/addthis/metrics/reporter/config/AbstractReporterConfig.java#L39C34-L39C45 > This is related to CASSANDRA-18614, which is focused on migrating to safe > YAML processing for the main configuration files. -- 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=17753193#comment-17753193 ] Maxim Muzafarov edited comment on CASSANDRA-15254 at 8/11/23 10:38 AM: --- [~blerer] Hi, have you had a chance to look at the changes? I don't want to bother you with a lot of reminders, I just want to make sure it's still on your radar :) The PR has been updated to reflect the latest changes in the trunk: https://github.com/apache/cassandra/pull/2334 was (Author: mmuzaf): [~blerer] Hi, have you had a chance to look at the changes? I don't want to bother you with a lot of reminders, I just want to make sure it's still on your radar :) > 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: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Attachments: Configuration Registry Diagram.png > > Time Spent: 19h 50m > Remaining Estimate: 0h > > 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=17753193#comment-17753193 ] Maxim Muzafarov commented on CASSANDRA-15254: - [~blerer] Hi, have you had a chance to look at the changes? I don't want to bother you with a lot of reminders, I just want to make sure it's still on your radar :) > 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: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Attachments: Configuration Registry Diagram.png > > Time Spent: 19h 50m > Remaining Estimate: 0h > > 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-18534) Make sstable format configurable per table
[
https://issues.apache.org/jira/browse/CASSANDRA-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753142#comment-17753142
]
Branimir Lambov commented on CASSANDRA-18534:
-
bq. for bti-fast and bti-small, what are the specific meanings of fast and
small for sstable or for tables?
To the database, there is no meaning other than to map to a specific definition
in the yaml. This is is for the user or DB administrator to choose and place
any meaning they want.
> Make sstable format configurable per table
> --
>
> Key: CASSANDRA-18534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18534
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.x
>
>
> Some SSTable format settings need to be configurable per table for better
> efficiency. This includes:
> - {{row_index_granularity}}
> - {{bloom_filter_fp_chance}}
> - {{crc_check_chance}}
> - {{min/max_index_interval}}
> Some of these are currently configurable using direct properties of tables.
> Having them as format properties makes better sense and should also support
> specifying useable combinations of settings, e.g.
> {code:java}
> CREATE TABLE ... WITH sstable_format = "bti-fast";
> CREATE TABLE ... WITH sstable_format = "bti-small";
> {code}
> where {{bti-fast}} and {{bti-small}} can be defined in {{cassandra.yaml}}
> e.g. as
> {code:java}
> sstable.format.options:
> - bti-fast:
> row_index_granularity: 1kiB
> bloom_filter_fp_chance: 0.01
> - bti-small:
> row_index_granularity: 32kiB
> bloom_filter_fp_chance: 0.1
> {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-18585) Alter Type does not validate changes like Create Type does
[
https://issues.apache.org/jira/browse/CASSANDRA-18585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753098#comment-17753098
]
Roman Mushchinski commented on CASSANDRA-18585:
---
Hi,
[~smiklosovic] I am planning to wrap it up this weekend (Aug 12-13). Sorry for
delay.
> Alter Type does not validate changes like Create Type does
> --
>
> Key: CASSANDRA-18585
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18585
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: David Capwell
>Assignee: Roman Mushchinski
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Create Type attempts to block undesired field types, but this validation is
> not cared over to Alter Type Add Field; which allows you to add
> unexpected/desired types
> {code}
> Assertions.assertThatThrownBy(() -> createType("CREATE TYPE %s (f
> counter)")).hasRootCauseMessage("A user type cannot contain counters");
> String type = createType(KEYSPACE, "CREATE TYPE %s (a int)");
> schemaChange(String.format("ALTER TYPE %s.%s ADD f counter", KEYSPACE, type));
> UserType udt =
> Keyspace.open(KEYSPACE).getMetadata().types.get(UTF8Type.instance.decompose(type)).get();
> logger.warn("UDT: {}", udt);
> {code}
> {code}
> UDT:
> org.apache.cassandra.db.marshal.UserType(cql_test_keyspace,747970655f3031,61:org.apache.cassandra.db.marshal.Int32Type,66:org.apache.cassandra.db.marshal.CounterColumnType)
> {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-18744) cassandra-stress in simplenative mode and prepared fails with exceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753067#comment-17753067 ] Stefan Miklosovic commented on CASSANDRA-18744: --- I am not sure from what version the bug is present but if it is true that it is in 4.0 as well we should fix it from there. I set fix versions from 4.0.x up. > cassandra-stress in simplenative mode and prepared fails with exceptions > > > Key: CASSANDRA-18744 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18744 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Brad Schoening >Priority: Low > Fix For: 4.0.x, 4.1.x, 5.x > > > % cassandra-stress write n=10 -mode simplenative cql3 prepared > ... > ap'; org.apache.cassandra.transport.messages.ResultMessage$Prepared is in > unnamed module of loader 'app') > java.lang.ClassCastException: class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > java.io.IOException: Operation x10 on key(s) [4e334f364c4c4b373530]: Error > executing: (ClassCastException): class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > > at org.apache.cassandra.stress.Operation.error(Operation.java:127) > at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:91) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:242) > at > org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:471) > java.io.IOException: Operation x10 on key(s) [373038504b3436363830]: Error > executing: (ClassCastException): class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > > at org.apache.cassandra.stress.Operation.error(Operation.java:127) > at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:91) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:242) > at > org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:471) > java.lang.RuntimeException: Failed to execute warmup > at org.apache.cassandra.stress.StressAction.warmup(StressAction.java:128) > at org.apache.cassandra.stress.StressAction.run(StressAction.java:71) > at org.apache.cassandra.stress.Stress.run(Stress.java:101) > at org.apache.cassandra.stress.Stress.main(Stress.java:54) -- 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-18744) cassandra-stress in simplenative mode and prepared fails with exceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18744: -- Fix Version/s: 4.0.x 4.1.x 5.x > cassandra-stress in simplenative mode and prepared fails with exceptions > > > Key: CASSANDRA-18744 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18744 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Brad Schoening >Priority: Low > Fix For: 4.0.x, 4.1.x, 5.x > > > % cassandra-stress write n=10 -mode simplenative cql3 prepared > ... > ap'; org.apache.cassandra.transport.messages.ResultMessage$Prepared is in > unnamed module of loader 'app') > java.lang.ClassCastException: class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > java.io.IOException: Operation x10 on key(s) [4e334f364c4c4b373530]: Error > executing: (ClassCastException): class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > > at org.apache.cassandra.stress.Operation.error(Operation.java:127) > at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:91) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:242) > at > org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:471) > java.io.IOException: Operation x10 on key(s) [373038504b3436363830]: Error > executing: (ClassCastException): class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > > at org.apache.cassandra.stress.Operation.error(Operation.java:127) > at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:91) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:242) > at > org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:471) > java.lang.RuntimeException: Failed to execute warmup > at org.apache.cassandra.stress.StressAction.warmup(StressAction.java:128) > at org.apache.cassandra.stress.StressAction.run(StressAction.java:71) > at org.apache.cassandra.stress.Stress.run(Stress.java:101) > at org.apache.cassandra.stress.Stress.main(Stress.java:54) -- 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-18744) cassandra-stress in simplenative mode and prepared fails with exceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18744: -- Bug Category: Parent values: Code(13163) Complexity: Normal Status: Open (was: Triage Needed) > cassandra-stress in simplenative mode and prepared fails with exceptions > > > Key: CASSANDRA-18744 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18744 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Brad Schoening >Priority: Low > > % cassandra-stress write n=10 -mode simplenative cql3 prepared > ... > ap'; org.apache.cassandra.transport.messages.ResultMessage$Prepared is in > unnamed module of loader 'app') > java.lang.ClassCastException: class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > java.io.IOException: Operation x10 on key(s) [4e334f364c4c4b373530]: Error > executing: (ClassCastException): class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > > at org.apache.cassandra.stress.Operation.error(Operation.java:127) > at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:91) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:242) > at > org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:471) > java.io.IOException: Operation x10 on key(s) [373038504b3436363830]: Error > executing: (ClassCastException): class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > > at org.apache.cassandra.stress.Operation.error(Operation.java:127) > at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:91) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:242) > at > org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:471) > java.lang.RuntimeException: Failed to execute warmup > at org.apache.cassandra.stress.StressAction.warmup(StressAction.java:128) > at org.apache.cassandra.stress.StressAction.run(StressAction.java:71) > at org.apache.cassandra.stress.Stress.run(Stress.java:101) > at org.apache.cassandra.stress.Stress.main(Stress.java:54) -- 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
