[jira] [Created] (CASSANDRA-18773) Compactions are slow
Cameron Zemek created CASSANDRA-18773:
-
Summary: Compactions are slow
Key: CASSANDRA-18773
URL: https://issues.apache.org/jira/browse/CASSANDRA-18773
Project: Cassandra
Issue Type: Improvement
Reporter: Cameron Zemek
Attachments: stress.yaml
I have noticed that compactions involving a lot of sstables are very slow (for
example major compactions). I have attached a cassandra stress profile that can
generate such a dataset under ccm. In my local test I have 2567 sstables at 4Mb
each.
I added code to track wall clock time of various parts of the code. One
problematic part is ManyToOne constructor. Tracing through the code for every
partition creating a ManyToOne for all the sstable iterators for each
partition. In my local test get a measy 60Kb/sec read speed, and bottlenecked
on single core CPU (since this code is single threaded) with it spending 85% of
the wall clock time in ManyToOne constructor.
As another datapoint to show its the merge iterator part of the code using the
cfstats from [https://github.com/instaclustr/cassandra-sstable-tools/] which
reads all the sstables but does no merging gets 26Mb/sec read speed.
Tracking back from ManyToOne call I see this in
UnfilteredPartitionIterators::merge
{code:java}
for (int i = 0; i < toMerge.size(); i++)
{
if (toMerge.get(i) == null)
{
if (null == empty)
empty = EmptyIterators.unfilteredRow(metadata,
partitionKey, isReverseOrder);
toMerge.set(i, empty);
}
}
{code}
Not sure what purpose of creating these empty rows are. But on a whim I removed
all these empty iterators before passing to ManyToOne and then all the wall
clock time shifted to CompactionIterator::hasNext() and read speed increased to
1.5Mb/s.
So there are further bottlenecks in this code path it seems, but the first is
this ManyToOne and having to build it for every partition read.
--
This message was sent by Atlassian 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 (7e1bbd43 -> 29b6438e)
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 7e1bbd43 generate docs for cceb2c06 new 29b6438e generate docs for cceb2c06 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 (7e1bbd43) \ N -- N -- N refs/heads/asf-staging (29b6438e) 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] [Comment Edited] (CASSANDRA-18451) CEP-15: (C*) Improve the chaos generation for Burn Tests: slow/flakey connections and dropped messages
[ https://issues.apache.org/jira/browse/CASSANDRA-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754739#comment-17754739 ] David Capwell edited comment on CASSANDRA-18451 at 8/16/23 10:03 PM: - rebased PR to include latest changes https://github.com/apache/cassandra-accord/pull/57 CI link https://app.circleci.com/pipelines/github/dcapwell/cassandra-accord?branch=eviction_CASSANDRA-18451 was (Author: dcapwell): rebased PR to include latest changes https://github.com/apache/cassandra-accord/pull/57 > CEP-15: (C*) Improve the chaos generation for Burn Tests: slow/flakey > connections and dropped messages > -- > > Key: CASSANDRA-18451 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18451 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > Burn test should be enhanced to add the following: > 1) message dropping from one node to another (this is different than the > current partition set logic in accord.impl.basic.Cluster#partitionSet) > 2) for messages with callbacks, trigger failure case > 3) redundant message delivery > Related work: > * Simulator’s > org.apache.cassandra.simulator.systems.SimulatedAction#applyToMessage > - Figures out what delivery action to perform via > org.apache.cassandra.simulator.FutureActionScheduler#shouldDeliver > -- timeout if dropPartition[from] != dropPartition[to] // either to/from is > in drop partition, but not both > -- config asked to override and deliver > -- 50/50 chance to deliver, after that 50/50 to deliver w/ timeout, after > that cause a failure > - in C* failure is an enum with Timeout and Unknown > - knows the schedule time and the message expire time, and can promote a > DELIVER event to DELIVER_AND_TIMEOUT > - triggers the timeout -- This message was sent by Atlassian Jira (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-18764) CEP-15 (C*) When a host replacement happens don't loose the peer mapping right away
[ https://issues.apache.org/jira/browse/CASSANDRA-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-18764: -- Since Version: 5.0 Source Control Link: https://github.com/apache/cassandra-accord/commit/2ad55e03c43ce074cdf5e36cfa14cb4278c2dc0f Resolution: Fixed Status: Resolved (was: Ready to Commit) > CEP-15 (C*) When a host replacement happens don't loose the peer mapping > right away > --- > > Key: CASSANDRA-18764 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18764 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > When a host replacement happens the latest epoch will no longer have the > removed peer, but we may have in-flight messages that still reference it. > When C* restarts we need to also filter out these peers so we don’t wait for > an epoch ack. -- This message was sent by Atlassian 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 (c2281833 -> 7e1bbd43)
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 c2281833 generate docs for cceb2c06 new 7e1bbd43 generate docs for cceb2c06 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 (c2281833) \ N -- N -- N refs/heads/asf-staging (7e1bbd43) 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-in-jvm-dtest-api] tag 0.0.16 created (now 1ba6ef9)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git at 1ba6ef9 (commit) No new revisions were added by this update. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 deleted (was 5353ed6)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git *** WARNING: tag 0.0.16 was deleted! *** tag was 5353ed6 The revisions that were on this annotated tag are still contained in other references; therefore, this change does not discard any commits from the repository. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 created (now 5353ed6)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git at 5353ed6 (tag) tagging fa95ce3fc2cd272cc1109a73e493a2057f5efbac (commit) replaces 0.0.15 by Alex Petrov on Wed Aug 16 23:12:17 2023 +0200 - Log - [maven-release-plugin] copy for tag 0.0.16 --- No new revisions were added by this update. - 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 release updated: [maven-release-plugin] prepare release 0.0.16
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new fa95ce3 [maven-release-plugin] prepare release 0.0.16 fa95ce3 is described below commit fa95ce3fc2cd272cc1109a73e493a2057f5efbac Author: Alex Petrov AuthorDate: Wed Aug 16 23:12:13 2023 +0200 [maven-release-plugin] prepare release 0.0.16 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index daadc91..ed2641a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.16 In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.15 +0.0.16 - 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 release updated: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new ebd40f9 [maven-release-plugin] prepare for next development iteration ebd40f9 is described below commit ebd40f951995efc255c42fb5f728bf8b6c6885ac Author: Alex Petrov AuthorDate: Wed Aug 16 23:12:20 2023 +0200 [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index ed2641a..518f7ef 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16 +-SNAPSHOT In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.16 +0.0.15 - 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 release updated (0395af6 -> f3a3b98)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git discard 0395af6 [maven-release-plugin] prepare for next development iteration discard 80a98f7 [maven-release-plugin] prepare release 0.0.16 discard b15bb00 Temporarily disable log action test as it seems to fail on jdk11 This update removed existing revisions from the reference, leaving the reference pointing at a previous point in the repository history. * -- * -- N refs/heads/release (f3a3b98) \ O -- O -- O (0395af6) Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .../cassandra/distributed/api/LogActionTest.java | 242 + 1 file changed, 242 insertions(+) create mode 100644 src/test/java/org/apache/cassandra/distributed/api/LogActionTest.java - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18770) Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
[
https://issues.apache.org/jira/browse/CASSANDRA-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755262#comment-17755262
]
vaibhav khedkar commented on CASSANDRA-18770:
-
another user in the community notified about seeing this issue with JAVA 8 and
4.0
> Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
> ---
>
> Key: CASSANDRA-18770
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18770
> Project: Cassandra
> Issue Type: Bug
>Reporter: vaibhav khedkar
>Priority: Normal
>
> We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to
> 4.0.5.
> After the upgrade, we are seeing a unique issue where the compacted
> SSTables's file descriptors are still present and are never cleared. This is
> causing false disk alerts. We have to restart nodes very often in order to
> reclaim the disk space.
> We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8.
> We are seeing it for all the tables (Filter, Data ..etc ) when checked with
> `lsof` command
> {code:java}
> /nb-1-big-Statistics.db.tmp (deleted)
> /nb-3-big-Statistics.db.tmp (deleted)
> /nb-2-big-Data.db (deleted)
> /nb-2-big-Statistics.db.tmp (deleted)
> /nb-2-big-Index.db (deleted)
> /nb-2-big-Statistics.db.tmp (deleted)
> /nb-2-big-CompressionInfo.db (deleted)
> /nb-2-big-Filter.db (deleted)
> /nb-2-big-Summary.db (deleted)
> /nb-2-big-Digest.crc32 (deleted)
> {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] tag 0.0.16 deleted (was 80a98f7)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git *** WARNING: tag 0.0.16 was deleted! *** was 80a98f7 [maven-release-plugin] prepare release 0.0.16 The revisions that were on this tag are still contained in other references; therefore, this change does not discard any commits from the repository. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18772) Remove dependency on commons-codec
[ https://issues.apache.org/jira/browse/CASSANDRA-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755257#comment-17755257 ] Ekaterina Dimitrova commented on CASSANDRA-18772: - I removed commons-codec on trunk based [branch|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:18772-trunk], and I am running CI [here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2481/workflows/6f261d27-dafd-4fad-b0e8-2e89a07d7f02] before sending mail to the ML, just in case something explodes... Let's see what happens. > Remove dependency on commons-codec > -- > > Key: CASSANDRA-18772 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18772 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > The dependency doesn't seem to have any direct usage in our codebase. > The only reference to how it might be used was found in CASSANDRA-12790. > Considering we also deprecate in 5.0 and remove metrics-reporter-config as > part of CASSANDRA-18743, I do not see a reason not to remove this one too. > We should probably take the same approach as CASSANDRA-18743 - deprecate in > 5.0 and remove in 5.1. ML thread is to be opened 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-in-jvm-dtest-api] tag 0.0.16 updated (eb60f14 -> 80a98f7)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git *** WARNING: tag 0.0.16 was modified! *** from eb60f14 (tag) to 80a98f7 (commit) omit 1ba6ef9 [maven-release-plugin] prepare release 0.0.16 add b15bb00 Temporarily disable log action test as it seems to fail on jdk11 add 80a98f7 [maven-release-plugin] prepare release 0.0.16 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the tag 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 (eb60f14) \ N -- N -- N refs/tags/0.0.16 (80a98f7) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .../cassandra/distributed/api/LogActionTest.java | 242 - 1 file changed, 242 deletions(-) delete mode 100644 src/test/java/org/apache/cassandra/distributed/api/LogActionTest.java - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] 01/03: Temporarily disable log action test as it seems to fail on jdk11
This is an automated email from the ASF dual-hosted git repository.
ifesdjeen pushed a commit to branch release
in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git
commit b15bb00d6ad4f9349a8ea56df45fa4fc04d56f4a
Author: Alex Petrov
AuthorDate: Wed Aug 16 22:59:08 2023 +0200
Temporarily disable log action test as it seems to fail on jdk11
---
.../cassandra/distributed/api/LogActionTest.java | 242 -
1 file changed, 242 deletions(-)
diff --git
a/src/test/java/org/apache/cassandra/distributed/api/LogActionTest.java
b/src/test/java/org/apache/cassandra/distributed/api/LogActionTest.java
deleted file mode 100644
index bc2100e..000
--- a/src/test/java/org/apache/cassandra/distributed/api/LogActionTest.java
+++ /dev/null
@@ -1,242 +0,0 @@
-/*
- * 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.distributed.api;
-
-import org.assertj.core.api.Assertions;
-import org.junit.jupiter.api.Test;
-import org.mockito.Mockito;
-import org.mockito.stubbing.Answer;
-
-import java.time.Duration;
-import java.util.Arrays;
-import java.util.Iterator;
-import java.util.List;
-import java.util.concurrent.TimeoutException;
-import java.util.function.Predicate;
-
-class LogActionTest
-{
-@Test
-public void watchForTimeout() {
-LogAction logs = mockLogAction(fn -> lineIterator(fn, "a", "b", "c",
"d"));
-
-Duration duration = Duration.ofSeconds(1);
-long startNanos = System.nanoTime();
-Assertions.assertThatThrownBy(() -> logs.watchFor(duration, "^ERROR"))
-.isInstanceOf(TimeoutException.class);
-Assertions.assertThat(System.nanoTime())
-.as("duration was smaller than expected timeout")
-.isGreaterThanOrEqualTo(startNanos + duration.toNanos());
-}
-
-@Test
-public void watchForAndFindFirstAttempt() throws TimeoutException {
-LogAction logs = mockLogAction(fn -> lineIterator(fn, "a", "b", "ERROR
match", "d"));
-
-List matches = logs.watchFor("^ERROR").getResult();
-Assertions.assertThat(matches).isEqualTo(Arrays.asList("ERROR match"));
-}
-
-@Test
-public void watchForAndFindThirdAttempt() throws TimeoutException {
-class Counter
-{
-int count;
-}
-Counter counter = new Counter();
-LogAction logs = mockLogAction(fn -> {
-if (++counter.count == 3) {
-return lineIterator(fn, "a", "b", "ERROR match", "d");
-} else {
-return lineIterator(fn, "a", "b", "c", "d");
-}
-});
-
-List matches = logs.watchFor("^ERROR").getResult();
-Assertions.assertThat(matches).isEqualTo(Arrays.asList("ERROR match"));
-Assertions.assertThat(counter.count).isEqualTo(3);
-}
-
-@Test
-public void grepNoMatch() {
-LogAction logs = mockLogAction(fn -> lineIterator(fn, "a", "b", "c",
"d"));
-
-List matches = logs.grep("^ERROR").getResult();
-Assertions.assertThat(matches).isEmpty();
-}
-
-@Test
-public void grepMatch() {
-LogAction logs = mockLogAction(fn -> lineIterator(fn, "a", "b", "ERROR
match", "d"));
-
-List matches = logs.grep("^ERROR").getResult();
-Assertions.assertThat(matches).isEqualTo(Arrays.asList("ERROR match"));
-}
-
-@Test
-public void grepForErrorsNoMatch() {
-LogAction logs = mockLogAction(fn -> lineIterator(fn, "a", "b", "c",
"d"));
-
-List matches = logs.grepForErrors().getResult();
-Assertions.assertThat(matches).isEmpty();
-}
-
-@Test
-public void grepForErrorsNoStacktrace() {
-LogAction logs = mockLogAction(fn -> lineIterator(fn, "INFO a", "INFO
b", "ERROR match", "INFO d"));
-
-List matches = logs.grepForErrors().getResult();
-Assertions.assertThat(matches).isEqualTo(Arrays.asList("ERROR match"));
-}
-
-@Test
-public void grepForErrorsWithStacktrace() {
-LogAction logs = mockLogAction(fn -> lineIterator(fn,
-"INFO a", "INFO b",
-"ERROR match",
-"\t\tat class.method(42)",
-
[cassandra-in-jvm-dtest-api] 02/03: [maven-release-plugin] prepare release 0.0.16
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git commit 80a98f759c45a60925d63f2d4659e2fedc24d322 Author: Alex Petrov AuthorDate: Wed Aug 16 19:06:15 2023 +0200 [maven-release-plugin] prepare release 0.0.16 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index daadc91..ed2641a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.16 In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.15 +0.0.16 - 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 release updated (1e93a27 -> 0395af6)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git discard 1e93a27 [maven-release-plugin] prepare for next development iteration discard 296f2a7 [maven-release-plugin] prepare release 0.0.16 new b15bb00 Temporarily disable log action test as it seems to fail on jdk11 new 80a98f7 [maven-release-plugin] prepare release 0.0.16 new 0395af6 [maven-release-plugin] prepare for next development iteration 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 (1e93a27) \ N -- N -- N refs/heads/release (0395af6) 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 3 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: .../cassandra/distributed/api/LogActionTest.java | 242 - 1 file changed, 242 deletions(-) delete mode 100644 src/test/java/org/apache/cassandra/distributed/api/LogActionTest.java - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] 03/03: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git commit 0395af65a8c529c7c252c03142e97a7be7351b53 Author: Alex Petrov AuthorDate: Wed Aug 16 19:06:29 2023 +0200 [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index ed2641a..daadc91 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16 +0.0.16-SNAPSHOT In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.16 +0.0.15 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18772) Remove dependency on commons-codec
[
https://issues.apache.org/jira/browse/CASSANDRA-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755256#comment-17755256
]
Ekaterina Dimitrova commented on CASSANDRA-18772:
-
{quote}I'll do some more digging to find a robust solution.
{quote}
That would be great, thanks :)
> Remove dependency on commons-codec
> --
>
> Key: CASSANDRA-18772
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18772
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The dependency doesn't seem to have any direct usage in our codebase.
> The only reference to how it might be used was found in CASSANDRA-12790.
> Considering we also deprecate in 5.0 and remove metrics-reporter-config as
> part of CASSANDRA-18743, I do not see a reason not to remove this one too.
> We should probably take the same approach as CASSANDRA-18743 - deprecate in
> 5.0 and remove in 5.1. ML thread is to be opened 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-in-jvm-dtest-api] branch trunk updated: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. djoshi 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 b9640c8 [maven-release-plugin] prepare for next development iteration b9640c8 is described below commit b9640c8cc8a9036c744cf230691c3cfb0f79f554 Author: Dinesh Joshi AuthorDate: Wed Aug 16 13:59:33 2023 -0700 [maven-release-plugin] prepare for next development iteration --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index ed2641a..9422744 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16 +0.0.17-SNAPSHOT In JVM Test API In JVM Test API - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 created (now eb60f14)
This is an automated email from the ASF dual-hosted git repository. djoshi pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git at eb60f14 (tag) tagging 1ba6ef93d0721741b5f6d6d72cba3da03fe78438 (commit) replaces 0.0.15 by Dinesh Joshi on Wed Aug 16 13:59:20 2023 -0700 - Log - [maven-release-plugin] copy for tag 0.0.16 --- No new revisions were added by this update. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 deleted (was 45dfcf0)
This is an automated email from the ASF dual-hosted git repository. djoshi pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git *** WARNING: tag 0.0.16 was deleted! *** tag was 45dfcf0 The revisions that were on this annotated tag are still contained in other references; therefore, this change does not discard any commits from the repository. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18772) Remove dependency on commons-codec
[ https://issues.apache.org/jira/browse/CASSANDRA-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755254#comment-17755254 ] Maxim Muzafarov commented on CASSANDRA-18772: - I was thinking about how we could find other dependencies that are no longer used, and how we could find them during the build. One I've found: https://docs.jboss.org/tattletale/userguide/1.2/en-US/html/ant.html https://tattletale.jboss.org/ I'll do some more digging to find a robust solution. > Remove dependency on commons-codec > -- > > Key: CASSANDRA-18772 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18772 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > The dependency doesn't seem to have any direct usage in our codebase. > The only reference to how it might be used was found in CASSANDRA-12790. > Considering we also deprecate in 5.0 and remove metrics-reporter-config as > part of CASSANDRA-18743, I do not see a reason not to remove this one too. > We should probably take the same approach as CASSANDRA-18743 - deprecate in > 5.0 and remove in 5.1. ML thread is to be opened 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-in-jvm-dtest-api] branch trunk updated: [maven-release-plugin] prepare release 0.0.16
This is an automated email from the ASF dual-hosted git repository. djoshi 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 1ba6ef9 [maven-release-plugin] prepare release 0.0.16 1ba6ef9 is described below commit 1ba6ef93d0721741b5f6d6d72cba3da03fe78438 Author: Dinesh Joshi AuthorDate: Wed Aug 16 13:55:40 2023 -0700 [maven-release-plugin] prepare release 0.0.16 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index daadc91..ed2641a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.16 In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.15 +0.0.16 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18772) Remove dependency on commons-codec
[ https://issues.apache.org/jira/browse/CASSANDRA-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18772: Fix Version/s: 5.0.x 5.x > Remove dependency on commons-codec > -- > > Key: CASSANDRA-18772 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18772 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > The dependency doesn't seem to have any direct usage in our codebase. > The only reference to how it might be used was found in CASSANDRA-12790. > Considering we also deprecate in 5.0 and remove metrics-reporter-config as > part of CASSANDRA-18743, I do not see a reason not to remove this one too. > We should probably take the same approach as CASSANDRA-18743 - deprecate in > 5.0 and remove in 5.1. ML thread is to be opened 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] [Created] (CASSANDRA-18772) Remove dependency on commons-codec
Ekaterina Dimitrova created CASSANDRA-18772: --- Summary: Remove dependency on commons-codec Key: CASSANDRA-18772 URL: https://issues.apache.org/jira/browse/CASSANDRA-18772 Project: Cassandra Issue Type: Bug Reporter: Ekaterina Dimitrova The dependency doesn't seem to have any direct usage in our codebase. The only reference to how it might be used was found in CASSANDRA-12790. Considering we also deprecate in 5.0 and remove metrics-reporter-config as part of CASSANDRA-18743, I do not see a reason not to remove this one too. We should probably take the same approach as CASSANDRA-18743 - deprecate in 5.0 and remove in 5.1. ML thread is to be opened 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-18772) Remove dependency on commons-codec
[ https://issues.apache.org/jira/browse/CASSANDRA-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18772: Bug Category: Parent values: Correctness(12982) Complexity: Normal Component/s: Dependencies Discovered By: User Report Severity: Normal Assignee: Ekaterina Dimitrova Status: Open (was: Triage Needed) > Remove dependency on commons-codec > -- > > Key: CASSANDRA-18772 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18772 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > The dependency doesn't seem to have any direct usage in our codebase. > The only reference to how it might be used was found in CASSANDRA-12790. > Considering we also deprecate in 5.0 and remove metrics-reporter-config as > part of CASSANDRA-18743, I do not see a reason not to remove this one too. > We should probably take the same approach as CASSANDRA-18743 - deprecate in > 5.0 and remove in 5.1. ML thread is to be opened 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-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=17755250#comment-17755250 ] Ekaterina Dimitrova commented on CASSANDRA-18743: - [~mmuzaf] , I think our comments crashed. I will open a separate ticket. Indeed, I also noticed the code compiles without it. > 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] [Comment Edited] (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=17755249#comment-17755249
]
Maxim Muzafarov edited comment on CASSANDRA-18743 at 8/16/23 8:39 PM:
--
I haven't found usages of the {{org.apache.commons.codec}} package, so I think
we can easily remove this dependency, the code also compiles without it.
However, I'm not sure if such a change is related to the patch itself as there
is no requirement for this package from the metrics-reporter-config side.
Should we file an separate issue for that?
was (Author: mmuzaf):
I haven't found usages of the {{org.apache.commons.codec}} package, so I think
we can easily remove this dependency, the code also compiles without it.
However, I'm not sure if such a change is related to the patch itself as there
is no requirement for this package from the metrics-reporter-config side.
> 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=17755249#comment-17755249
]
Maxim Muzafarov commented on CASSANDRA-18743:
-
I haven't found usages of the {{org.apache.commons.codec}} package, so I think
we can easily remove this dependency, the code also compiles without it.
However, I'm not sure if such a change is related to the patch itself as there
is no requirement for this package from the metrics-reporter-config side.
> 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] [Comment Edited] (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=17755248#comment-17755248
]
Ekaterina Dimitrova edited comment on CASSANDRA-18743 at 8/16/23 8:38 PM:
--
{quote}[~e.dimitrova] I don't see any usage for commons-codec - I'm supportive
of removing the dependency, but is there any requirement to do so as part of
this ticket?
{quote}
No, no requirement. I noticed it might be related(based on CASSANDRA-12790), so
I wanted to ask if you have more information I might be missing. I will open a
ticket to explore its potential deprecation/removal, thanks.
{quote}I was thinking it would be good to have a separate ticket to audit
dependencies before 5.0, so we can do any deprecations necessary as part of
upgrades / workarounds.
{quote}
We have some dependencies that can get some love. We upgraded some for 5.0, but
still, some can get some love.
was (Author: e.dimitrova):
{quote}[~e.dimitrova] I don't see any usage for commons-codec - I'm supportive
of removing the dependency, but is there any requirement to do so as part of
this ticket?
{quote}
No, no requirement. I noticed it might be related(based on CASSANDRA-12790), so
I wanted to ask if you have more information I might be missing.
{quote}I was thinking it would be good to have a separate ticket to audit
dependencies before 5.0, so we can do any deprecations necessary as part of
upgrades / workarounds.
{quote}
We have some dependencies that can get some love. We upgraded some for 5.0, but
still, some can get some love.
> 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=17755248#comment-17755248
]
Ekaterina Dimitrova commented on CASSANDRA-18743:
-
{quote}[~e.dimitrova] I don't see any usage for commons-codec - I'm supportive
of removing the dependency, but is there any requirement to do so as part of
this ticket?
{quote}
No, no requirement. I noticed it might be related(based on CASSANDRA-12790), so
I wanted to ask if you have more information I might be missing.
{quote}I was thinking it would be good to have a separate ticket to audit
dependencies before 5.0, so we can do any deprecations necessary as part of
upgrades / workarounds.
{quote}
We have some dependencies that can get some love. We upgraded some for 5.0, but
still, some can get some love.
> 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-18733) Waiting indefinitely on ReceivedMessage response in StreamSession#receive() can cause deadlock
[
https://issues.apache.org/jira/browse/CASSANDRA-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755247#comment-17755247
]
Jon Meredith commented on CASSANDRA-18733:
--
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|cassandra-4.1|[branch|https://github.com/jonmeredith/cassandra/tree/commit_remote_branch/CASSANDRA-18733-cassandra-4.1-3B701280-17E1-427A-8F6B-EAD2F6E02C40]|[build|https://app.circleci.com/pipelines/github/jonmeredith/cassandra?branch=commit_remote_branch%2FCASSANDRA-18733-cassandra-4.1-3B701280-17E1-427A-8F6B-EAD2F6E02C40]|[build\|unknown]|
|cassandra-5.0|[branch|https://github.com/jonmeredith/cassandra/tree/commit_remote_branch/CASSANDRA-18733-cassandra-5.0-3B701280-17E1-427A-8F6B-EAD2F6E02C40]|[build|https://app.circleci.com/pipelines/github/jonmeredith/cassandra?branch=commit_remote_branch%2FCASSANDRA-18733-cassandra-5.0-3B701280-17E1-427A-8F6B-EAD2F6E02C40]|[build\|unknown]|
|trunk|[branch|https://github.com/jonmeredith/cassandra/tree/commit_remote_branch/CASSANDRA-18733-trunk-3B701280-17E1-427A-8F6B-EAD2F6E02C40]|[build|https://app.circleci.com/pipelines/github/jonmeredith/cassandra?branch=commit_remote_branch%2FCASSANDRA-18733-trunk-3B701280-17E1-427A-8F6B-EAD2F6E02C40]|[build\|unknown]|
> Waiting indefinitely on ReceivedMessage response in StreamSession#receive()
> can cause deadlock
> --
>
> Key: CASSANDRA-18733
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18733
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Consistency/Streaming
>Reporter: Caleb Rackliffe
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.1.x, 5.0, 5.x
>
>
> I've observed in a recent stack trace from a node running 4.1 what looks like
> a deadlock around the {{StreamSession}} monitor lock when
> {{StreamSession#receive()}} waits via {{syncUninteruptibly()}} for a response
> to a control message.
> {noformat}
> "Messaging-EventLoop-3-10" #320 daemon prio=5 os_prio=0 cpu=57979617.98ms
> elapsed=5587916.03s tid=0x7f056e88ae00 nid=0x80ec waiting for monitor
> entry [0x7f056d277000]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.cassandra.streaming.StreamSession.closeSession(StreamSession.java:524)
> - waiting to lock <0x0006816fae70> (a
> org.apache.cassandra.streaming.StreamSession)
> at
> org.apache.cassandra.streaming.StreamSession.onError(StreamSession.java:690)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.onMessageComplete(StreamingMultiplexedChannel.java:264)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.lambda$sendMessage$1(StreamingMultiplexedChannel.java:233)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel$$Lambda$2029/0x0008007a0c40.operationComplete(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:134)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:148)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$GenericFutureListenerList.notifySelf(ListenerList.java:190)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.lambda$notifyExclusive$0(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$$Lambda$950/0x000800666040.accept(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.IntrusiveStack.forEach(IntrusiveStack.java:195)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyExclusive(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notify(ListenerList.java:96)
> at
> org.apache.cassandra.utils.concurrent.AsyncFuture.trySet(AsyncFuture.java:104)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.tryFailure(AbstractFuture.java:148)
> at
> org.apache.cassandra.utils.concurrent.AsyncPromise.tryFailure(AsyncPromise.java:139)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:1009)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:870)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1367)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:717)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:764)
> at
> io.netty.channel.AbstractChannelHandlerContext$WriteTask.run(AbstractChannelHandlerContext.java:1071)
> at
>
[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=17755246#comment-17755246 ] Abe Ratnofsky commented on CASSANDRA-18743: --- Just posted to the list for consensus on a 5.1 removal; let's wait on merging the removal on trunk til that consensus is reached. [~e.dimitrova] I don't see any usage for commons-codec - I'm supportive of removing the dependency, but is there any requirement to do so as part of this ticket? I was thinking it would be good to have a separate ticket to audit dependencies before 5.0, so we can do any deprecations necessary as part of upgrades / workarounds. > 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=17755240#comment-17755240 ] Ekaterina Dimitrova commented on CASSANDRA-18743: - I stumbled into CASSANDRA-12790 and commons-codec, which according to that ticket is used together with the metrics reporter when storing metrics for InfluxDB. I found out commons-codes was originally added in CASSANDRA-1851. I am not sure how else we use and whether we still need it. Anyone any thoughts? > 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-18771) Cassandra 4.0.5 nodes fails to start when replacing dead node
[
https://issues.apache.org/jira/browse/CASSANDRA-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755234#comment-17755234
]
Brandon Williams commented on CASSANDRA-18771:
--
Can you attach the debug.log?
> Cassandra 4.0.5 nodes fails to start when replacing dead node
> -
>
> Key: CASSANDRA-18771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18771
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: ANSHUL SAINI
>Priority: Urgent
>
> Trying to replace a down node the new nodes fail to start, using property
> {_}*replace_address*{_}.
> Below message appears continuously in system logs.
> {noformat}
> WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95
> - /xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
> dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
> reaching the network
> INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92
> - /xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed
> to connect
> io.netty.channel.ConnectTimeoutException: connection timed out:
> /xxx.xxx.xxx.xxx:7000
> at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
> at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
> at
> io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
>
> {noformat}
> DEBUG [ScheduledTasks:1] 2023-08-16 19:09:56,919 StorageService.java:2399 -
> Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not
> a member in token metadata
> DEBUG [ScheduledTasks:1] 2023-08-16 19:10:56,920 StorageService.java:2399 -
> Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not
> a member in token metadata
> {noformat}
> xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
> NO other ERROR/WARNING appears in logs. The node goes into UJ state, but
> never joins the ring.
> While this doesn't happen always, but we are seeing this increased behaviour
> since upgrading from 3.11.9 to 4.0.5.
> Configuration are all fine as to mitigate this we terminate the node and
> spawn a new one with same configs.
--
This message was sent by Atlassian Jira
(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-18771) Cassandra 4.0.5 nodes fails to start when replacing dead node
[
https://issues.apache.org/jira/browse/CASSANDRA-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755233#comment-17755233
]
ANSHUL SAINI commented on CASSANDRA-18771:
--
Yes NO ERROR shows up in logs, but node just remains in a hung state (UJ) for
days without actually joining the cluster.
Could be related/similar to CASSANDRA-16877 (but this was fixed in 4.0.1).
> Cassandra 4.0.5 nodes fails to start when replacing dead node
> -
>
> Key: CASSANDRA-18771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18771
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: ANSHUL SAINI
>Priority: Urgent
>
> Trying to replace a down node the new nodes fail to start, using property
> {_}*replace_address*{_}.
> Below message appears continuously in system logs.
> {noformat}
> WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95
> - /xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
> dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
> reaching the network
> INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92
> - /xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed
> to connect
> io.netty.channel.ConnectTimeoutException: connection timed out:
> /xxx.xxx.xxx.xxx:7000
> at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
> at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
> at
> io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
>
> {noformat}
> DEBUG [ScheduledTasks:1] 2023-08-16 19:09:56,919 StorageService.java:2399 -
> Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not
> a member in token metadata
> DEBUG [ScheduledTasks:1] 2023-08-16 19:10:56,920 StorageService.java:2399 -
> Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not
> a member in token metadata
> {noformat}
> xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
> NO other ERROR/WARNING appears in logs. The node goes into UJ state, but
> never joins the ring.
> While this doesn't happen always, but we are seeing this increased behaviour
> since upgrading from 3.11.9 to 4.0.5.
> Configuration are all fine as to mitigate this we terminate the node and
> spawn a new one with same configs.
--
This message was sent by Atlassian Jira
(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-18771) Cassandra 4.0.5 nodes fails to start when replacing dead node
[
https://issues.apache.org/jira/browse/CASSANDRA-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755231#comment-17755231
]
Brandon Williams commented on CASSANDRA-18771:
--
None of the log messages indicate a fatal error, what causes the nodes to fail
to start?
> Cassandra 4.0.5 nodes fails to start when replacing dead node
> -
>
> Key: CASSANDRA-18771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18771
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: ANSHUL SAINI
>Priority: Urgent
>
> Trying to replace a down node the new nodes fail to start, using property
> {_}*replace_address*{_}.
> Below message appears continuously in system logs.
> {noformat}
> WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95
> - /xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
> dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
> reaching the network
> INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92
> - /xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed
> to connect
> io.netty.channel.ConnectTimeoutException: connection timed out:
> /xxx.xxx.xxx.xxx:7000
> at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
> at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
> at
> io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
>
> {noformat}
> DEBUG [ScheduledTasks:1] 2023-08-16 19:09:56,919 StorageService.java:2399 -
> Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not
> a member in token metadata
> DEBUG [ScheduledTasks:1] 2023-08-16 19:10:56,920 StorageService.java:2399 -
> Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not
> a member in token metadata
> {noformat}
> xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
> NO other ERROR/WARNING appears in logs. The node goes into UJ state, but
> never joins the ring.
> While this doesn't happen always, but we are seeing this increased behaviour
> since upgrading from 3.11.9 to 4.0.5.
> Configuration are all fine as to mitigate this we terminate the node and
> spawn a new one with same configs.
--
This message was sent by Atlassian Jira
(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-18771) Cassandra 4.0.5 nodes fails to start when replacing dead node
[
https://issues.apache.org/jira/browse/CASSANDRA-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ANSHUL SAINI updated CASSANDRA-18771:
-
Severity: Critical
> Cassandra 4.0.5 nodes fails to start when replacing dead node
> -
>
> Key: CASSANDRA-18771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18771
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: ANSHUL SAINI
>Priority: Urgent
>
> Trying to replace a down node the new nodes fail to start, using property
> {_}*replace_address*{_}.
> Below message appears continuously in system logs.
> {noformat}
> WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95
> - /xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
> dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
> reaching the network
> INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92
> - /xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed
> to connect
> io.netty.channel.ConnectTimeoutException: connection timed out:
> /xxx.xxx.xxx.xxx:7000
> at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
> at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
> at
> io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
>
> {noformat}
> DEBUG [ScheduledTasks:1] 2023-08-16 19:09:56,919 StorageService.java:2399 -
> Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not
> a member in token metadata
> DEBUG [ScheduledTasks:1] 2023-08-16 19:10:56,920 StorageService.java:2399 -
> Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not
> a member in token metadata
> {noformat}
> xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
> NO other ERROR/WARNING appears in logs. The node goes into UJ state, but
> never joins the ring.
> While this doesn't happen always, but we are seeing this increased behaviour
> since upgrading from 3.11.9 to 4.0.5.
> Configuration are all fine as to mitigate this we terminate the node and
> spawn a new one with same configs.
--
This message was sent by Atlassian Jira
(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-18771) Cassandra 4.0.5 nodes fails to start when replacing dead node
[
https://issues.apache.org/jira/browse/CASSANDRA-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ANSHUL SAINI updated CASSANDRA-18771:
-
Description:
Trying to replace a down node the new nodes fail to start, using property
{_}*replace_address*{_}.
Below message appears continuously in system logs.
{noformat}
WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95 -
/xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
reaching the network
INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92 -
/xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed to
connect
io.netty.channel.ConnectTimeoutException: connection timed out:
/xxx.xxx.xxx.xxx:7000
at
io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at
io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
{noformat}
{noformat}
DEBUG [ScheduledTasks:1] 2023-08-16 19:09:56,919 StorageService.java:2399 -
Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not a
member in token metadata
DEBUG [ScheduledTasks:1] 2023-08-16 19:10:56,920 StorageService.java:2399 -
Ignoring application state LOAD from /yyy.yyy.yyy.yyy:7000 because it is not a
member in token metadata
{noformat}
xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
NO other ERROR/WARNING appears in logs. The node goes into UJ state, but never
joins the ring.
While this doesn't happen always, but we are seeing this increased behaviour
since upgrading from 3.11.9 to 4.0.5.
Configuration are all fine as to mitigate this we terminate the node and spawn
a new one with same configs.
was:
Trying to replace a down node the new nodes fail to start, using property
{_}*replace_address*{_}.
Below message appears continuously in system logs.
{noformat}
WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95 -
/xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
reaching the network
INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92 -
/xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed to
connect
io.netty.channel.ConnectTimeoutException: connection timed out:
/xxx.xxx.xxx.xxx:7000
at
io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at
io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
{noformat}
{noformat}
DEBUG [ScheduledTasks:1] 2023-08-16 19:08:56,919 StorageService.java:2399 -
Ignoring application state LOAD from /10.133.66.188:7000 because it is not a
member in token metadata DEBUG [ScheduledTasks:1] 2023-08-16 19:09:56,919
StorageService.java:2399 - Ignoring application state LOAD from
/10.133.66.188:7000 because it is not a member in token metadata DEBUG
[ScheduledTasks:1] 2023-08-16 19:10:56,920 StorageService.java:2399 - Ignoring
application state LOAD from /10.133.66.188:7000 because it is not a member in
token metadata DEBUG [ScheduledTasks:1] 2023-08-16 19:11:56,920
StorageService.java:2399 - Ignoring application state LOAD from
/10.133.66.188:7000 because it is not a member in token metadata
{noformat}
xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
NO other ERROR/WARNING appears in logs.
[jira] [Updated] (CASSANDRA-18771) Cassandra 4.0.5 nodes fails to start when replacing dead node
[
https://issues.apache.org/jira/browse/CASSANDRA-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ANSHUL SAINI updated CASSANDRA-18771:
-
Description:
Trying to replace a down node the new nodes fail to start, using property
{_}*replace_address*{_}.
Below message appears continuously in system logs.
{noformat}
WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95 -
/xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
reaching the network
INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92 -
/xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed to
connect
io.netty.channel.ConnectTimeoutException: connection timed out:
/xxx.xxx.xxx.xxx:7000
at
io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at
io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
{noformat}
{noformat}
DEBUG [ScheduledTasks:1] 2023-08-16 19:08:56,919 StorageService.java:2399 -
Ignoring application state LOAD from /10.133.66.188:7000 because it is not a
member in token metadata DEBUG [ScheduledTasks:1] 2023-08-16 19:09:56,919
StorageService.java:2399 - Ignoring application state LOAD from
/10.133.66.188:7000 because it is not a member in token metadata DEBUG
[ScheduledTasks:1] 2023-08-16 19:10:56,920 StorageService.java:2399 - Ignoring
application state LOAD from /10.133.66.188:7000 because it is not a member in
token metadata DEBUG [ScheduledTasks:1] 2023-08-16 19:11:56,920
StorageService.java:2399 - Ignoring application state LOAD from
/10.133.66.188:7000 because it is not a member in token metadata
{noformat}
xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
NO other ERROR/WARNING appears in logs. The node goes into UJ state, but never
joins the ring.
While this doesn't happen always, but we are seeing this increased behaviour
since upgrading from 3.11.9 to 4.0.5.
Configuration are all fine as to mitigate this we terminate the node and spawn
a new one with same configs.
was:
Trying to replace a down node the new nodes fail to start, using property
{_}*replace_address*{_}.
Below message appears continuously in system logs.
{noformat}
WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95 -
/xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
reaching the network
INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92 -
/xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed to
connect
io.netty.channel.ConnectTimeoutException: connection timed out:
/xxx.xxx.xxx.xxx:7000
at
io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at
io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
{noformat}
xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
NO other ERROR/WARNING appears in logs. The node goes into UJ state, but never
joins the ring.
While this doesn't happen always, but we are seeing this increased behaviour
since upgrading from 3.11.9 to 4.0.5.
Configuration are all fine as to mitigate this we terminate the node and spawn
a new one with same configs.
> Cassandra 4.0.5 nodes fails to start when replacing dead node
>
[jira] [Created] (CASSANDRA-18771) Cassandra 4.0.5 nodes fails to start when replacing dead node
ANSHUL SAINI created CASSANDRA-18771:
Summary: Cassandra 4.0.5 nodes fails to start when replacing dead
node
Key: CASSANDRA-18771
URL: https://issues.apache.org/jira/browse/CASSANDRA-18771
Project: Cassandra
Issue Type: Bug
Components: Cluster/Gossip
Reporter: ANSHUL SAINI
Trying to replace a down node the new nodes fail to start, using property
{_}*replace_address*{_}.
Below message appears continuously in system logs.
{noformat}
WARN [Messaging-EventLoop-3-2] 2023-08-16 14:18:58,565 NoSpamLogger.java:95 -
/xxx.xxx.xxx.xxx:7000->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel]
dropping message of type GOSSIP_DIGEST_SYN whose timeout expired before
reaching the network
INFO [Messaging-EventLoop-3-2] 2023-08-16 14:19:23,910 NoSpamLogger.java:92 -
/xxx.xxx.xxx.xxx->/yyy.yyy.yyy.yyy:7000-URGENT_MESSAGES-[no-channel] failed to
connect
io.netty.channel.ConnectTimeoutException: connection timed out:
/xxx.xxx.xxx.xxx:7000
at
io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at
io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
{noformat}
xxx.xxx.xxx.xxx - IP of down node yyy.yyy.yyy.yyy - IP of new node
NO other ERROR/WARNING appears in logs. The node goes into UJ state, but never
joins the ring.
While this doesn't happen always, but we are seeing this increased behaviour
since upgrading from 3.11.9 to 4.0.5.
Configuration are all fine as to mitigate this we terminate the node and spawn
a new one with same configs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-accord] branch trunk updated: CEP-15 (C*) When a host replacement happens don't loose the peer mapping right away (#60)
This is an automated email from the ASF dual-hosted git repository.
dcapwell pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-accord.git
The following commit(s) were added to refs/heads/trunk by this push:
new 2ad55e03 CEP-15 (C*) When a host replacement happens don't loose the
peer mapping right away (#60)
2ad55e03 is described below
commit 2ad55e03c43ce074cdf5e36cfa14cb4278c2dc0f
Author: dcapwell
AuthorDate: Wed Aug 16 11:47:52 2023 -0700
CEP-15 (C*) When a host replacement happens don't loose the peer mapping
right away (#60)
patch by David Capwell; reviewed by Blake Eggleston for CASSANDRA-18764
---
accord-core/src/main/java/accord/api/ConfigurationService.java | 2 +-
.../src/main/java/accord/impl/AbstractConfigurationService.java | 6 +++---
accord-core/src/main/java/accord/local/Node.java| 2 +-
accord-core/src/main/java/accord/utils/async/AsyncResults.java | 6 ++
.../src/test/java/accord/burn/BurnTestConfigurationService.java | 2 +-
.../src/test/java/accord/impl/AbstractConfigurationServiceTest.java | 6 +++---
.../src/test/java/accord/impl/mock/MockConfigurationService.java| 2 +-
.../src/main/java/accord/maelstrom/SimpleConfigService.java | 2 +-
8 files changed, 17 insertions(+), 11 deletions(-)
diff --git a/accord-core/src/main/java/accord/api/ConfigurationService.java
b/accord-core/src/main/java/accord/api/ConfigurationService.java
index 4e6943fc..6ad9f205 100644
--- a/accord-core/src/main/java/accord/api/ConfigurationService.java
+++ b/accord-core/src/main/java/accord/api/ConfigurationService.java
@@ -173,7 +173,7 @@ public interface ConfigurationService
* On invocation the system is not necessarily ready to process the epoch,
and the BootstrapReady parameter
* provides indications of when the bootstrap has completed various phases
of setup.
*/
-void acknowledgeEpoch(EpochReady ready);
+void acknowledgeEpoch(EpochReady ready, boolean startSync);
void reportEpochClosed(Ranges ranges, long epoch);
diff --git
a/accord-core/src/main/java/accord/impl/AbstractConfigurationService.java
b/accord-core/src/main/java/accord/impl/AbstractConfigurationService.java
index 7132f8d1..d8ebab8f 100644
--- a/accord-core/src/main/java/accord/impl/AbstractConfigurationService.java
+++ b/accord-core/src/main/java/accord/impl/AbstractConfigurationService.java
@@ -233,10 +233,10 @@ public abstract class
AbstractConfigurationService {
synchronized (AbstractConfigurationService.this)
@@ -247,7 +247,7 @@ public abstract class
AbstractConfigurationService {
synchronized (AbstractConfigurationService.this)
{
-localSyncComplete(epochs.getOrCreate(ready.epoch).topology);
+localSyncComplete(epochs.getOrCreate(ready.epoch).topology,
startSync);
}
});
}
diff --git a/accord-core/src/main/java/accord/local/Node.java
b/accord-core/src/main/java/accord/local/Node.java
index 48bf5f51..7cf84dfe 100644
--- a/accord-core/src/main/java/accord/local/Node.java
+++ b/accord-core/src/main/java/accord/local/Node.java
@@ -209,7 +209,7 @@ public class Node implements ConfigurationService.Listener,
NodeTimeService
return AsyncResults.success(null);
EpochReady ready = onTopologyUpdateInternal(topology, startSync);
ready.coordination.addCallback(() ->
this.topology.onEpochSyncComplete(id, topology.epoch()));
-configService.acknowledgeEpoch(ready);
+configService.acknowledgeEpoch(ready, startSync);
return ready.coordination;
}
diff --git a/accord-core/src/main/java/accord/utils/async/AsyncResults.java
b/accord-core/src/main/java/accord/utils/async/AsyncResults.java
index 98e5ccf0..dfa7fe08 100644
--- a/accord-core/src/main/java/accord/utils/async/AsyncResults.java
+++ b/accord-core/src/main/java/accord/utils/async/AsyncResults.java
@@ -201,6 +201,12 @@ public class AsyncResults
throw new IllegalStateException("Result succeeded");
return result.failure;
}
+
+@Override
+public String toString()
+{
+return getClass().getSimpleName() + "{status=" + (isDone() ?
isSuccess() ? "success" : "failure" : "pending") + "}";
+}
}
static class Chain extends AbstractResult
diff --git
a/accord-core/src/test/java/accord/burn/BurnTestConfigurationService.java
b/accord-core/src/test/java/accord/burn/BurnTestConfigurationService.java
index b872a176..4c9ce6c0 100644
--- a/accord-core/src/test/java/accord/burn/BurnTestConfigurationService.java
+++ b/accord-core/src/test/java/accord/burn/BurnTestConfigurationService.java
@@ -158,7 +158,7 @@ public class BurnTestConfigurationService extends
AbstractConfigurationService.M
}
@Override
-protected void localSyncComplete(Topology topology)
+protected void
[jira] [Updated] (CASSANDRA-18764) CEP-15 (C*) When a host replacement happens don't loose the peer mapping right away
[ https://issues.apache.org/jira/browse/CASSANDRA-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-18764: -- Reviewers: Blake Eggleston, David Capwell Status: Review In Progress (was: Patch Available) > CEP-15 (C*) When a host replacement happens don't loose the peer mapping > right away > --- > > Key: CASSANDRA-18764 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18764 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > When a host replacement happens the latest epoch will no longer have the > removed peer, but we may have in-flight messages that still reference it. > When C* restarts we need to also filter out these peers so we don’t wait for > an epoch ack. -- This message was sent by Atlassian Jira (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-18764) CEP-15 (C*) When a host replacement happens don't loose the peer mapping right away
[ https://issues.apache.org/jira/browse/CASSANDRA-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-18764: -- Reviewers: Blake Eggleston (was: Blake Eggleston, David Capwell) > CEP-15 (C*) When a host replacement happens don't loose the peer mapping > right away > --- > > Key: CASSANDRA-18764 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18764 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > When a host replacement happens the latest epoch will no longer have the > removed peer, but we may have in-flight messages that still reference it. > When C* restarts we need to also filter out these peers so we don’t wait for > an epoch ack. -- This message was sent by Atlassian Jira (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-18764) CEP-15 (C*) When a host replacement happens don't loose the peer mapping right away
[ https://issues.apache.org/jira/browse/CASSANDRA-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-18764: -- Status: Ready to Commit (was: Review In Progress) +1 from [~bdeggleston] in GH > CEP-15 (C*) When a host replacement happens don't loose the peer mapping > right away > --- > > Key: CASSANDRA-18764 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18764 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > When a host replacement happens the latest epoch will no longer have the > removed peer, but we may have in-flight messages that still reference it. > When C* restarts we need to also filter out these peers so we don’t wait for > an epoch ack. -- This message was sent by Atlassian Jira (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-18770) Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
[
https://issues.apache.org/jira/browse/CASSANDRA-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vaibhav khedkar updated CASSANDRA-18770:
Description:
We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to
4.0.5.
After the upgrade, we are seeing a unique issue where the compacted SSTables's
file descriptors are still present and are never cleared. This is causing false
disk alerts. We have to restart nodes very often in order to reclaim the disk
space.
We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8.
We are seeing it for all the tables (Filter, Data ..etc ) when checked with
`lsof` command
{code:java}
/nb-1-big-Statistics.db.tmp (deleted)
/nb-3-big-Statistics.db.tmp (deleted)
/nb-2-big-Data.db (deleted)
/nb-2-big-Statistics.db.tmp (deleted)
/nb-2-big-Index.db (deleted)
/nb-2-big-Statistics.db.tmp (deleted)
/nb-2-big-CompressionInfo.db (deleted)
/nb-2-big-Filter.db (deleted)
/nb-2-big-Summary.db (deleted)
/nb-2-big-Digest.crc32 (deleted)
{code}
was:
We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to
4.0.5.
After the upgrade, we are seeing a unique issue where the compacted SSTables's
file descriptors are still present and are never cleared. This is causing false
disk alerts. We have to restart nodes very often in order to reclaim the disk
space.
We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8.
We are seeing it for all the tables (Filter, Data ..etc ) when checked with
`lsof` command
```
/nb-1-big-Statistics.db.tmp (deleted)
/nb-3-big-Statistics.db.tmp (deleted)
/nb-2-big-Data.db (deleted)
/nb-2-big-Statistics.db.tmp (deleted)
/nb-2-big-Index.db (deleted)
/nb-2-big-Statistics.db.tmp (deleted)
/nb-2-big-CompressionInfo.db (deleted)
/nb-2-big-Filter.db (deleted)
/nb-2-big-Summary.db (deleted)
/nb-2-big-Digest.crc32 (deleted)
```
> Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
> ---
>
> Key: CASSANDRA-18770
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18770
> Project: Cassandra
> Issue Type: Bug
>Reporter: vaibhav khedkar
>Priority: Normal
>
> We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to
> 4.0.5.
> After the upgrade, we are seeing a unique issue where the compacted
> SSTables's file descriptors are still present and are never cleared. This is
> causing false disk alerts. We have to restart nodes very often in order to
> reclaim the disk space.
> We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8.
> We are seeing it for all the tables (Filter, Data ..etc ) when checked with
> `lsof` command
> {code:java}
> /nb-1-big-Statistics.db.tmp (deleted)
> /nb-3-big-Statistics.db.tmp (deleted)
> /nb-2-big-Data.db (deleted)
> /nb-2-big-Statistics.db.tmp (deleted)
> /nb-2-big-Index.db (deleted)
> /nb-2-big-Statistics.db.tmp (deleted)
> /nb-2-big-CompressionInfo.db (deleted)
> /nb-2-big-Filter.db (deleted)
> /nb-2-big-Summary.db (deleted)
> /nb-2-big-Digest.crc32 (deleted)
> {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-18770) Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vaibhav khedkar updated CASSANDRA-18770: Description: We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to 4.0.5. After the upgrade, we are seeing a unique issue where the compacted SSTables's file descriptors are still present and are never cleared. This is causing false disk alerts. We have to restart nodes very often in order to reclaim the disk space. We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8. We are seeing it for all the tables (Filter, Data ..etc ) when checked with `lsof` command ``` /nb-1-big-Statistics.db.tmp (deleted) /nb-3-big-Statistics.db.tmp (deleted) /nb-2-big-Data.db (deleted) /nb-2-big-Statistics.db.tmp (deleted) /nb-2-big-Index.db (deleted) /nb-2-big-Statistics.db.tmp (deleted) /nb-2-big-CompressionInfo.db (deleted) /nb-2-big-Filter.db (deleted) /nb-2-big-Summary.db (deleted) /nb-2-big-Digest.crc32 (deleted) ``` was: We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to 4.0.5. After the upgrade, we are seeing a unique issue where the compacted SSTables's file descriptors are still present and are never cleared. This is causing false disk alerts. We have to restart nodes very often in order to reclaim the disk space. We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8. We are seeing it for all the tables (Filter, Data ..etc ) when checked with `lsof` command /nb-1-big-Statistics.db.tmp (deleted) /nb-3-big-Statistics.db.tmp (deleted) /nb-2-big-Data.db (deleted) /nb-2-big-Statistics.db.tmp (deleted) /nb-2-big-Index.db (deleted) /nb-2-big-Statistics.db.tmp (deleted) /nb-2-big-CompressionInfo.db (deleted) /nb-2-big-Filter.db (deleted) /nb-2-big-Summary.db (deleted) /nb-2-big-Digest.crc32 (deleted) > Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5 > --- > > Key: CASSANDRA-18770 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18770 > Project: Cassandra > Issue Type: Bug >Reporter: vaibhav khedkar >Priority: Normal > > We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to > 4.0.5. > After the upgrade, we are seeing a unique issue where the compacted > SSTables's file descriptors are still present and are never cleared. This is > causing false disk alerts. We have to restart nodes very often in order to > reclaim the disk space. > We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8. > We are seeing it for all the tables (Filter, Data ..etc ) when checked with > `lsof` command > ``` > /nb-1-big-Statistics.db.tmp (deleted) > /nb-3-big-Statistics.db.tmp (deleted) > /nb-2-big-Data.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-Index.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-CompressionInfo.db (deleted) > /nb-2-big-Filter.db (deleted) > /nb-2-big-Summary.db (deleted) > /nb-2-big-Digest.crc32 (deleted) > ``` -- This message was sent by Atlassian Jira (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-18767) tablestats should show speculative retries
[ https://issues.apache.org/jira/browse/CASSANDRA-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18767: - Test and Documentation Plan: run CI Status: Patch Available (was: Open) > tablestats should show speculative retries > -- > > Key: CASSANDRA-18767 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18767 > Project: Cassandra > Issue Type: Bug > Components: Observability/Metrics >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > NodeProbe makes > [provisions|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tools/NodeProbe.java#L1921] > for it, but it is never used later. -- This message was sent by Atlassian Jira (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-18770) Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755206#comment-17755206 ] Brandon Williams commented on CASSANDRA-18770: -- I don't recall any bugs around this, but 4.0.5 is over a year old so it may be worth trying 4.0.11. > Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5 > --- > > Key: CASSANDRA-18770 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18770 > Project: Cassandra > Issue Type: Bug >Reporter: vaibhav khedkar >Priority: Normal > > We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to > 4.0.5. > After the upgrade, we are seeing a unique issue where the compacted > SSTables's file descriptors are still present and are never cleared. This is > causing false disk alerts. We have to restart nodes very often in order to > reclaim the disk space. > We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8. > We are seeing it for all the tables (Filter, Data ..etc ) when checked with > `lsof` command > /nb-1-big-Statistics.db.tmp (deleted) > /nb-3-big-Statistics.db.tmp (deleted) > /nb-2-big-Data.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-Index.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-CompressionInfo.db (deleted) > /nb-2-big-Filter.db (deleted) > /nb-2-big-Summary.db (deleted) > /nb-2-big-Digest.crc32 (deleted) -- This message was sent by Atlassian Jira (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-18770) Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755202#comment-17755202 ] vaibhav khedkar commented on CASSANDRA-18770: - yes java is holding these open. We do not have any in-jvm monitoring and nothing else runs the same JVM except for C*. The weird part is it only happens after we upgrade to 4.0.5, in the same VM with same JVM settings, we are not seeing this issue before upgrade. > Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5 > --- > > Key: CASSANDRA-18770 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18770 > Project: Cassandra > Issue Type: Bug >Reporter: vaibhav khedkar >Priority: Normal > > We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to > 4.0.5. > After the upgrade, we are seeing a unique issue where the compacted > SSTables's file descriptors are still present and are never cleared. This is > causing false disk alerts. We have to restart nodes very often in order to > reclaim the disk space. > We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8. > We are seeing it for all the tables (Filter, Data ..etc ) when checked with > `lsof` command > /nb-1-big-Statistics.db.tmp (deleted) > /nb-3-big-Statistics.db.tmp (deleted) > /nb-2-big-Data.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-Index.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-CompressionInfo.db (deleted) > /nb-2-big-Filter.db (deleted) > /nb-2-big-Summary.db (deleted) > /nb-2-big-Digest.crc32 (deleted) -- This message was sent by Atlassian Jira (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-18770) Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755189#comment-17755189 ] Brandon Williams commented on CASSANDRA-18770: -- Does lsof say java is holding these open? If so do you have any in-jvm monitoring or anything else that runs in the same jvm? > Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5 > --- > > Key: CASSANDRA-18770 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18770 > Project: Cassandra > Issue Type: Bug >Reporter: vaibhav khedkar >Priority: Normal > > We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to > 4.0.5. > After the upgrade, we are seeing a unique issue where the compacted > SSTables's file descriptors are still present and are never cleared. This is > causing false disk alerts. We have to restart nodes very often in order to > reclaim the disk space. > We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8. > We are seeing it for all the tables (Filter, Data ..etc ) when checked with > `lsof` command > /nb-1-big-Statistics.db.tmp (deleted) > /nb-3-big-Statistics.db.tmp (deleted) > /nb-2-big-Data.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-Index.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-CompressionInfo.db (deleted) > /nb-2-big-Filter.db (deleted) > /nb-2-big-Summary.db (deleted) > /nb-2-big-Digest.crc32 (deleted) -- This message was sent by Atlassian Jira (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-18770) Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vaibhav khedkar updated CASSANDRA-18770: Platform: Java8 (was: All) > Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5 > --- > > Key: CASSANDRA-18770 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18770 > Project: Cassandra > Issue Type: Bug >Reporter: vaibhav khedkar >Priority: Normal > > We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to > 4.0.5. > After the upgrade, we are seeing a unique issue where the compacted > SSTables's file descriptors are still present and are never cleared. This is > causing false disk alerts. We have to restart nodes very often in order to > reclaim the disk space. > We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8. > We are seeing it for all the tables (Filter, Data ..etc ) when checked with > `lsof` command > /nb-1-big-Statistics.db.tmp (deleted) > /nb-3-big-Statistics.db.tmp (deleted) > /nb-2-big-Data.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-Index.db (deleted) > /nb-2-big-Statistics.db.tmp (deleted) > /nb-2-big-CompressionInfo.db (deleted) > /nb-2-big-Filter.db (deleted) > /nb-2-big-Summary.db (deleted) > /nb-2-big-Digest.crc32 (deleted) -- This message was sent by Atlassian Jira (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-18770) Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5
vaibhav khedkar created CASSANDRA-18770: --- Summary: Open File Descriptors not cleared post upgrade from 3.11.9 to 4.0.5 Key: CASSANDRA-18770 URL: https://issues.apache.org/jira/browse/CASSANDRA-18770 Project: Cassandra Issue Type: Bug Reporter: vaibhav khedkar We recently upgraded our fleet of ~2500 Cassandra instances from 3.11.9 to 4.0.5. After the upgrade, we are seeing a unique issue where the compacted SSTables's file descriptors are still present and are never cleared. This is causing false disk alerts. We have to restart nodes very often in order to reclaim the disk space. We use the *Apache* version of C* along with CentOS Linux 7.9.2009 and Java 8. We are seeing it for all the tables (Filter, Data ..etc ) when checked with `lsof` command /nb-1-big-Statistics.db.tmp (deleted) /nb-3-big-Statistics.db.tmp (deleted) /nb-2-big-Data.db (deleted) /nb-2-big-Statistics.db.tmp (deleted) /nb-2-big-Index.db (deleted) /nb-2-big-Statistics.db.tmp (deleted) /nb-2-big-CompressionInfo.db (deleted) /nb-2-big-Filter.db (deleted) /nb-2-big-Summary.db (deleted) /nb-2-big-Digest.crc32 (deleted) -- This message was sent by Atlassian 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 release updated: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new 1e93a27 [maven-release-plugin] prepare for next development iteration 1e93a27 is described below commit 1e93a271d5da7a00e7fb57c1dd4f3c15e6f2f0bc Author: Alex Petrov AuthorDate: Wed Aug 16 19:06:29 2023 +0200 [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index ed2641a..daadc91 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16 +0.0.16-SNAPSHOT In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.16 +0.0.15 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 created (now 45dfcf0)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git at 45dfcf0 (tag) tagging 296f2a7c32ae4e035f488a4a3eb68d1627dc4e73 (commit) replaces 0.0.15 by Alex Petrov on Wed Aug 16 19:06:22 2023 +0200 - Log - [maven-release-plugin] copy for tag 0.0.16 --- No new revisions were added by this update. - 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 release updated: [maven-release-plugin] prepare release 0.0.16
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new 296f2a7 [maven-release-plugin] prepare release 0.0.16 296f2a7 is described below commit 296f2a7c32ae4e035f488a4a3eb68d1627dc4e73 Author: Alex Petrov AuthorDate: Wed Aug 16 19:06:15 2023 +0200 [maven-release-plugin] prepare release 0.0.16 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index daadc91..ed2641a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.16 In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.15 +0.0.16 - 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 release updated (00cba75 -> f3a3b98)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git discard 00cba75 [maven-release-plugin] prepare release 0.0.16 This update removed existing revisions from the reference, leaving the reference pointing at a previous point in the repository history. * -- * -- N refs/heads/release (f3a3b98) \ O -- O -- O (00cba75) Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) - 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 release updated: [maven-release-plugin] prepare release 0.0.16
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new 00cba75 [maven-release-plugin] prepare release 0.0.16 00cba75 is described below commit 00cba752aa5791f2d2edf40d9a3c2decfba21c16 Author: Alex Petrov AuthorDate: Wed Aug 16 19:04:36 2023 +0200 [maven-release-plugin] prepare release 0.0.16 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index daadc91..ed2641a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.16 In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.15 +0.0.16 - 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 release updated (edd9f74 -> f3a3b98)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git discard edd9f74 [maven-release-plugin] prepare for next development iteration discard d913dee [maven-release-plugin] prepare release 0.0.16 This update removed existing revisions from the reference, leaving the reference pointing at a previous point in the repository history. * -- * -- N refs/heads/release (f3a3b98) \ O -- O -- O (edd9f74) Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 deleted (was 668bade)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git *** WARNING: tag 0.0.16 was deleted! *** tag was 668bade The revisions that were on this annotated tag are still contained in other references; therefore, this change does not discard any commits from the repository. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18769) Fix flaky test: org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace
[
https://issues.apache.org/jira/browse/CASSANDRA-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18769:
-
Resolution: Duplicate
Status: Resolved (was: Open)
Huh, I missed that one. ;)
> Fix flaky test:
> org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace
> -
>
> Key: CASSANDRA-18769
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18769
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Memtable
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.0.x
>
>
> {noformat}
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final jdk.management.jfr.StreamManager
> jdk.management.jfr.FlightRecorderMXBeanImpl.streamHandler accessible: module
> jdk.management.jfr does not "opens jdk.management.jfr" to unnamed module
> @6db9f5a4
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at
> java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
> at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at org.apache.cassandra.Util.runCatchingAssertionError(Util.java:644)
> at org.apache.cassandra.Util.flakyTest(Util.java:669)
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace(MemtableSizeTest.java:61)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1203/workflows/087cb08a-d035-491f-bb90-208b25a5fd4b/jobs/44699/tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18769) Fix flaky test: org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace
[
https://issues.apache.org/jira/browse/CASSANDRA-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755181#comment-17755181
]
Ekaterina Dimitrova commented on CASSANDRA-18769:
-
I think this is a duplicate of CASSANDRA-18447
> Fix flaky test:
> org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace
> -
>
> Key: CASSANDRA-18769
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18769
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Memtable
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.0.x
>
>
> {noformat}
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final jdk.management.jfr.StreamManager
> jdk.management.jfr.FlightRecorderMXBeanImpl.streamHandler accessible: module
> jdk.management.jfr does not "opens jdk.management.jfr" to unnamed module
> @6db9f5a4
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at
> java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
> at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at org.apache.cassandra.Util.runCatchingAssertionError(Util.java:644)
> at org.apache.cassandra.Util.flakyTest(Util.java:669)
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace(MemtableSizeTest.java:61)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1203/workflows/087cb08a-d035-491f-bb90-208b25a5fd4b/jobs/44699/tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18769) Fix flaky test: org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace
[
https://issues.apache.org/jira/browse/CASSANDRA-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18769:
-
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990)
Complexity: Normal
Component/s: Local/Memtable
Discovered By: User Report
Fix Version/s: 4.0.x
Severity: Normal
Status: Open (was: Triage Needed)
> Fix flaky test:
> org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace
> -
>
> Key: CASSANDRA-18769
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18769
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Memtable
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.0.x
>
>
> {noformat}
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> final jdk.management.jfr.StreamManager
> jdk.management.jfr.FlightRecorderMXBeanImpl.streamHandler accessible: module
> jdk.management.jfr does not "opens jdk.management.jfr" to unnamed module
> @6db9f5a4
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at
> java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
> at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at org.apache.cassandra.Util.runCatchingAssertionError(Util.java:644)
> at org.apache.cassandra.Util.flakyTest(Util.java:669)
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace(MemtableSizeTest.java:61)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1203/workflows/087cb08a-d035-491f-bb90-208b25a5fd4b/jobs/44699/tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18769) Fix flaky test: org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace
Brandon Williams created CASSANDRA-18769:
Summary: Fix flaky test:
org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace
Key: CASSANDRA-18769
URL: https://issues.apache.org/jira/browse/CASSANDRA-18769
Project: Cassandra
Issue Type: Bug
Reporter: Brandon Williams
{noformat}
java.lang.reflect.InaccessibleObjectException: Unable to make field private
final jdk.management.jfr.StreamManager
jdk.management.jfr.FlightRecorderMXBeanImpl.streamHandler accessible: module
jdk.management.jfr does not "opens jdk.management.jfr" to unnamed module
@6db9f5a4
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
at
java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
at
org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
at
org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
at org.apache.cassandra.Util.runCatchingAssertionError(Util.java:644)
at org.apache.cassandra.Util.flakyTest(Util.java:669)
at
org.apache.cassandra.cql3.MemtableSizeTest.testTruncationReleasesLogSpace(MemtableSizeTest.java:61)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{noformat}
Seen here:
https://app.circleci.com/pipelines/github/driftx/cassandra/1203/workflows/087cb08a-d035-491f-bb90-208b25a5fd4b/jobs/44699/tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] branch release updated: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new edd9f74 [maven-release-plugin] prepare for next development iteration edd9f74 is described below commit edd9f7425cb4de15274c7796b0ed771f76207af2 Author: Alex Petrov AuthorDate: Wed Aug 16 18:51:21 2023 +0200 [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index ed2641a..daadc91 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16 +0.0.16-SNAPSHOT In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.16 +0.0.15 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 created (now 668bade)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git at 668bade (tag) tagging d913dee5b6379ebe9ebeb57faff9e6221754e939 (commit) replaces 0.0.15 by Alex Petrov on Wed Aug 16 18:51:15 2023 +0200 - Log - [maven-release-plugin] copy for tag 0.0.16 --- No new revisions were added by this update. - 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 release updated: [maven-release-plugin] prepare release 0.0.16
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new d913dee [maven-release-plugin] prepare release 0.0.16 d913dee is described below commit d913dee5b6379ebe9ebeb57faff9e6221754e939 Author: Alex Petrov AuthorDate: Wed Aug 16 18:51:07 2023 +0200 [maven-release-plugin] prepare release 0.0.16 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index daadc91..ed2641a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.16 In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.15 +0.0.16 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 deleted (was 58929e1)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git *** WARNING: tag 0.0.16 was deleted! *** tag was 58929e1 This change permanently discards the following revisions: discard 11072ef [maven-release-plugin] prepare release 0.0.16 - 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 release updated (06c1241 -> f3a3b98)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git discard 06c1241 [maven-release-plugin] prepare for next development iteration omit 11072ef [maven-release-plugin] prepare release 0.0.16 This update removed existing revisions from the reference, leaving the reference pointing at a previous point in the repository history. * -- * -- N refs/heads/release (f3a3b98) \ O -- O -- O (06c1241) Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18766) high speculative retries on v4.1.3
[ https://issues.apache.org/jira/browse/CASSANDRA-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755178#comment-17755178 ] Brandon Williams edited comment on CASSANDRA-18766 at 8/16/23 4:44 PM: --- Fwiw, I did a test against the 4.1 branch and didn't see any speculative retries with stress and 1M partitions. I was using my patch from CASSANDRA-18767 to check though, so maybe I messed up there. was (Author: brandon.williams): Fwiw, I did a test against the 4.1 branch and didn't see any speculative retries with stress an 1M partitions. I was using my patch from CASSANDRA-18767 to check though, so maybe I messed up there. > high speculative retries on v4.1.3 > -- > > Key: CASSANDRA-18766 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18766 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Coordination >Reporter: Ivans Novikovs >Priority: Normal > Fix For: 4.1.x > > Attachments: signature.asc > > > There are up to 10+ times higher speculative retries for reads on 4.1.3 > comparing to 4.0.7 and 4.1.2 when using QUORUM and default setting of 99p. > On 4.1.3 after upgrade I see speculative retries for up to 35% of all reads > for specific table. Latency for reads is stable around 500 microseconds. > java 1.8.0_382 is used -- This message was sent by Atlassian 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 release updated: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new 06c1241 [maven-release-plugin] prepare for next development iteration 06c1241 is described below commit 06c1241643a518b9050a7140d8b4eb39254a5c1f Author: Alex Petrov AuthorDate: Wed Aug 16 18:44:01 2023 +0200 [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index ed2641a..daadc91 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16 +0.0.16-SNAPSHOT In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.16 +0.0.15 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 created (now 58929e1)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git at 58929e1 (tag) tagging 11072efbf922518bcc539b82042785699b2b3a7c (commit) replaces 0.0.15 by Alex Petrov on Wed Aug 16 18:43:54 2023 +0200 - Log - [maven-release-plugin] copy for tag 0.0.16 --- No new revisions were added by this update. - 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 release updated: [maven-release-plugin] prepare release 0.0.16
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new 11072ef [maven-release-plugin] prepare release 0.0.16 11072ef is described below commit 11072efbf922518bcc539b82042785699b2b3a7c Author: Alex Petrov AuthorDate: Wed Aug 16 18:43:47 2023 +0200 [maven-release-plugin] prepare release 0.0.16 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index daadc91..ed2641a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.16 In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.15 +0.0.16 - 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 release updated (a3cc424 -> f3a3b98)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git discard a3cc424 [maven-release-plugin] prepare release 0.0.16 This update removed existing revisions from the reference, leaving the reference pointing at a previous point in the repository history. * -- * -- N refs/heads/release (f3a3b98) \ O -- O -- O (a3cc424) Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 deleted (was 00b05fa)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git *** WARNING: tag 0.0.16 was deleted! *** tag was 00b05fa The revisions that were on this annotated tag are still contained in other references; therefore, this change does not discard any commits from the repository. - 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 release updated: [maven-release-plugin] prepare release 0.0.16
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git The following commit(s) were added to refs/heads/release by this push: new a3cc424 [maven-release-plugin] prepare release 0.0.16 a3cc424 is described below commit a3cc424ce254d74f1a599b16e4c044b2413de0e9 Author: Alex Petrov AuthorDate: Wed Aug 16 18:39:56 2023 +0200 [maven-release-plugin] prepare release 0.0.16 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index daadc91..ed2641a 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.16 In JVM Test API In JVM Test API @@ -164,7 +164,7 @@ scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git scm:git:https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git -0.0.15 +0.0.16 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] annotated tag 0.0.16 created (now 00b05fa)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.16 in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git at 00b05fa (tag) tagging f3a3b982227602ec0752a5d0d4d780dc62ac3f6d (commit) replaces 0.0.15 by Alex Petrov on Wed Aug 16 18:36:32 2023 +0200 - Log - [maven-release-plugin] copy for tag 0.0.16 --- No new revisions were added by this update. - 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 release updated (e973f5b -> f3a3b98)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git discard e973f5b [maven-release-plugin] prepare release 0.0.15 This update removed existing revisions from the reference, leaving the reference pointing at a previous point in the repository history. * -- * -- N refs/heads/release (f3a3b98) \ O -- O -- O (e973f5b) Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: pom.xml | 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-in-jvm-dtest-api] branch release updated (05f4990 -> e973f5b)
This is an automated email from the ASF dual-hosted git repository.
ifesdjeen pushed a change to branch release
in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git
from 05f4990 [maven-release-plugin] prepare for next development iteration
add acaabaf Add support for JMX
add dadade5 Updated setting newVersion to look up the current version
add 369355a Update CHANGES.txt
add ea4b44e [maven-release-plugin] prepare release 0.0.14
add 07cb6fe [maven-release-plugin] prepare for next development iteration
add 1e3bc4c Add JMX utility class to in-jvm dtest to ease development of
new tests using JMX
add 48af78d [maven-release-plugin] prepare release 0.0.15
add 695ef5e [maven-release-plugin] prepare for next development iteration
add f3a3b98 CASSANDRA-18727 - JMXUtil.getJmxConnector should retry
connection attempts (#37)
new e973f5b [maven-release-plugin] prepare release 0.0.15
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| 4 +
README.md | 4 +-
pom.xml| 4 +-
.../apache/cassandra/distributed/api/Feature.java | 2 +-
.../cassandra/distributed/api/IInstanceConfig.java | 2 +
.../cassandra/distributed/api/LogAction.java | 30 +
.../distributed/shared/InstanceClassLoader.java| 61 +-
.../cassandra/distributed/shared/JMXUtil.java | 127 +
...ThrowingRunnable.java => Uninterruptibles.java} | 36 +++---
9 files changed, 225 insertions(+), 45 deletions(-)
create mode 100644
src/main/java/org/apache/cassandra/distributed/shared/JMXUtil.java
copy
src/main/java/org/apache/cassandra/distributed/shared/{ThrowingRunnable.java =>
Uninterruptibles.java} (52%)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] 01/01: [maven-release-plugin] prepare release 0.0.15
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git commit e973f5b70acd92cd5485aec5c207251273610286 Author: Alex Petrov AuthorDate: Wed Aug 16 18:33:24 2023 +0200 [maven-release-plugin] prepare release 0.0.15 --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index daadc91..ace94f1 100644 --- a/pom.xml +++ b/pom.xml @@ -27,7 +27,7 @@ 4.0.0 org.apache.cassandra dtest-api -0.0.16-SNAPSHOT +0.0.15 In JVM Test API In JVM Test API - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18766) high speculative retries on v4.1.3
[ https://issues.apache.org/jira/browse/CASSANDRA-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] miklosovic updated CASSANDRA-18766: --- Attachment: signature.asc Are you able to build Cassandra from source on your own? There is not a lot of changes in 4.1.3. My idea is to git bisect 4.1.2 - 4.1.3 and try each . You should nail down the regression pretty fast. Sent from ProtonMail mobile \ > high speculative retries on v4.1.3 > -- > > Key: CASSANDRA-18766 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18766 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Coordination >Reporter: Ivans Novikovs >Priority: Normal > Fix For: 4.1.x > > Attachments: signature.asc > > > There are up to 10+ times higher speculative retries for reads on 4.1.3 > comparing to 4.0.7 and 4.1.2 when using QUORUM and default setting of 99p. > On 4.1.3 after upgrade I see speculative retries for up to 35% of all reads > for specific table. Latency for reads is stable around 500 microseconds. > java 1.8.0_382 is used -- This message was sent by Atlassian Jira (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-18733) Waiting indefinitely on ReceivedMessage response in StreamSession#receive() can cause deadlock
[
https://issues.apache.org/jira/browse/CASSANDRA-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755174#comment-17755174
]
Caleb Rackliffe commented on CASSANDRA-18733:
-
Minor nits expressed in direct Slack conversation...but +1 to all PRs
> Waiting indefinitely on ReceivedMessage response in StreamSession#receive()
> can cause deadlock
> --
>
> Key: CASSANDRA-18733
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18733
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Consistency/Streaming
>Reporter: Caleb Rackliffe
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.1.x, 5.0, 5.x
>
>
> I've observed in a recent stack trace from a node running 4.1 what looks like
> a deadlock around the {{StreamSession}} monitor lock when
> {{StreamSession#receive()}} waits via {{syncUninteruptibly()}} for a response
> to a control message.
> {noformat}
> "Messaging-EventLoop-3-10" #320 daemon prio=5 os_prio=0 cpu=57979617.98ms
> elapsed=5587916.03s tid=0x7f056e88ae00 nid=0x80ec waiting for monitor
> entry [0x7f056d277000]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.cassandra.streaming.StreamSession.closeSession(StreamSession.java:524)
> - waiting to lock <0x0006816fae70> (a
> org.apache.cassandra.streaming.StreamSession)
> at
> org.apache.cassandra.streaming.StreamSession.onError(StreamSession.java:690)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.onMessageComplete(StreamingMultiplexedChannel.java:264)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.lambda$sendMessage$1(StreamingMultiplexedChannel.java:233)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel$$Lambda$2029/0x0008007a0c40.operationComplete(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:134)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:148)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$GenericFutureListenerList.notifySelf(ListenerList.java:190)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.lambda$notifyExclusive$0(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$$Lambda$950/0x000800666040.accept(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.IntrusiveStack.forEach(IntrusiveStack.java:195)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyExclusive(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notify(ListenerList.java:96)
> at
> org.apache.cassandra.utils.concurrent.AsyncFuture.trySet(AsyncFuture.java:104)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.tryFailure(AbstractFuture.java:148)
> at
> org.apache.cassandra.utils.concurrent.AsyncPromise.tryFailure(AsyncPromise.java:139)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:1009)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:870)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1367)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:717)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:764)
> at
> io.netty.channel.AbstractChannelHandlerContext$WriteTask.run(AbstractChannelHandlerContext.java:1071)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(java.base@11.0.16/Thread.java:829)
> {noformat}
> It seems that while {{receive()} is holding the monitor lock on
> {{StreamSession}}, the callback that executes on a different thread for the
> control message it sends carries an error. This error, when handled in
> {{onError()}}, then calls {{closeSession()}}, which tries to acquire the
> monitor lock already held in
[jira] [Updated] (CASSANDRA-18762) Repair triggers OOM with direct buffer memory
[
https://issues.apache.org/jira/browse/CASSANDRA-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-18762:
---
Description:
We are seeing repeated failures of nodes with 16GB of heap and the same size
(16GB) for direct memory (derived from -Xms). This seems to be related to
CASSANDRA-15202 which moved merkel trees off-heap in 4.0. Using Cassandra
4.0.6.
{noformat}
2023-08-09 04:30:57,470 [INFO ] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 RepairSession.java:202 - [repair
#5e55a3b0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_a from
/169.102.200.241:7000
2023-08-09 04:30:57,567 [INFO ] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 RepairSession.java:202 - [repair
#5e0d2900-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
/169.93.192.29:7000
2023-08-09 04:30:57,568 [INFO ] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 RepairSession.java:202 - [repair
#5e1dcad0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_c from
/169.104.171.134:7000
2023-08-09 04:30:57,591 [INFO ] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 RepairSession.java:202 - [repair
#5e69a0e0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
/169.79.232.67:7000
2023-08-09 04:30:57,876 [INFO ] [Service Thread] cluster_id=101
ip_address=169.0.0.1 GCInspector.java:294 - G1 Old Generation GC in 282ms.
Compressed Class Space: 8444560 -> 8372152; G1 Eden Space: 7809794048 -> 0; G1
Old Gen: 1453478400 -> 820942800; G1 Survivor Space: 419430400 -> 0; Metaspace:
80411136 -> 80176528
2023-08-09 04:30:58,387 [ERROR] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 JVMStabilityInspector.java:102 - OutOfMemory error letting
the JVM handle the error:
java.lang.OutOfMemoryError: Direct buffer memory
at java.base/java.nio.Bits.reserveMemory(Bits.java:175)
at java.base/java.nio.DirectByteBuffer.(DirectByteBuffer.java:118)
at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:318)
at org.apache.cassandra.utils.MerkleTree.allocate(MerkleTree.java:742)
at org.apache.cassandra.utils.MerkleTree.deserializeOffHeap(MerkleTree.java:780)
at org.apache.cassandra.utils.MerkleTree.deserializeTree(MerkleTree.java:751)
at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:720)
at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:698)
at
org.apache.cassandra.utils.MerkleTrees$MerkleTreesSerializer.deserialize(MerkleTrees.java:416)
at
org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:100)
at
org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:84)
at
org.apache.cassandra.net.Message$Serializer.deserializePost40(Message.java:782)
at org.apache.cassandra.net.Message$Serializer.deserialize(Message.java:642)
at
org.apache.cassandra.net.InboundMessageHandler$LargeMessage.deserialize(InboundMessageHandler.java:364)
at
org.apache.cassandra.net.InboundMessageHandler$LargeMessage.access$1100(InboundMessageHandler.java:317)
at
org.apache.cassandra.net.InboundMessageHandler$ProcessLargeMessage.provideMessage(InboundMessageHandler.java:504)
at
org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:429)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834)no* further _formatting_ is
done here{noformat}
-XX:+AlwaysPreTouch
-XX:+CrashOnOutOfMemoryError
-XX:+ExitOnOutOfMemoryError
-XX:+HeapDumpOnOutOfMemoryError
-XX:+ParallelRefProcEnabled
-XX:+PerfDisableSharedMem
-XX:+ResizeTLAB
-XX:+UseG1GC
-XX:+UseNUMA
-XX:+UseTLAB
-XX:+UseThreadPriorities
-XX:-UseBiasedLocking
-XX:CompileCommandFile=/opt/nosql/clusters/cassandra-101/conf/hotspot_compiler
-XX:G1RSetUpdatingPauseTimePercent=5
-XX:G1ReservePercent=20
-XX:HeapDumpPath=/opt/nosql/data/cluster_101/cassandra-1691623098-pid2804737.hprof
-XX:InitiatingHeapOccupancyPercent=70
-XX:MaxGCPauseMillis=200
-XX:StringTableSize=60013
-Xlog:gc*:file=/opt/nosql/clusters/cassandra-101/logs/gc.log:time,uptime:filecount=10,filesize=10485760
-Xms16G
-Xmx16G
-Xss256k
>From our Prometheus metrics, the behavior shows the direct buffer memory
>ramping up until it reaches the max and then causes an OOM. It would appear
>that direct memory is never being released by the JVM until its exhausted.
!Cluster-dm-metrics.PNG!
An Eclipse Memory Analyzer
Class Histogram:
||Class Name||Objects||Shallow Heap||Retained Heap||
[jira] [Updated] (CASSANDRA-18762) Repair triggers OOM with direct buffer memory
[
https://issues.apache.org/jira/browse/CASSANDRA-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-18762:
---
Description:
We are seeing repeated failures of nodes with 16GB of heap and the same size
(16GB) for direct memory (derived from -Xms). This seems to be related to
CASSANDRA-15202 which moved merkel trees off-heap in 4.0. Using Cassandra
4.0.6.
{noformat}
2023-08-09 04:30:57,470 [INFO ] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 RepairSession.java:202 - [repair
#5e55a3b0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_a from
/169.102.200.241:7000
2023-08-09 04:30:57,567 [INFO ] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 RepairSession.java:202 - [repair
#5e0d2900-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
/169.93.192.29:7000
2023-08-09 04:30:57,568 [INFO ] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 RepairSession.java:202 - [repair
#5e1dcad0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_c from
/169.104.171.134:7000
2023-08-09 04:30:57,591 [INFO ] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 RepairSession.java:202 - [repair
#5e69a0e0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
/169.79.232.67:7000
2023-08-09 04:30:57,876 [INFO ] [Service Thread] cluster_id=101
ip_address=169.0.0.1 GCInspector.java:294 - G1 Old Generation GC in 282ms.
Compressed Class Space: 8444560 -> 8372152; G1 Eden Space: 7809794048 -> 0; G1
Old Gen: 1453478400 -> 820942800; G1 Survivor Space: 419430400 -> 0; Metaspace:
80411136 -> 80176528
2023-08-09 04:30:58,387 [ERROR] [AntiEntropyStage:1] cluster_id=101
ip_address=169.0.0.1 JVMStabilityInspector.java:102 - OutOfMemory error letting
the JVM handle the error:
java.lang.OutOfMemoryError: Direct buffer memory
at java.base/java.nio.Bits.reserveMemory(Bits.java:175)
at java.base/java.nio.DirectByteBuffer.(DirectByteBuffer.java:118)
at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:318)
at org.apache.cassandra.utils.MerkleTree.allocate(MerkleTree.java:742)
at org.apache.cassandra.utils.MerkleTree.deserializeOffHeap(MerkleTree.java:780)
at org.apache.cassandra.utils.MerkleTree.deserializeTree(MerkleTree.java:751)
at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:720)
at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:698)
at
org.apache.cassandra.utils.MerkleTrees$MerkleTreesSerializer.deserialize(MerkleTrees.java:416)
at
org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:100)
at
org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:84)
at
org.apache.cassandra.net.Message$Serializer.deserializePost40(Message.java:782)
at org.apache.cassandra.net.Message$Serializer.deserialize(Message.java:642)
at
org.apache.cassandra.net.InboundMessageHandler$LargeMessage.deserialize(InboundMessageHandler.java:364)
at
org.apache.cassandra.net.InboundMessageHandler$LargeMessage.access$1100(InboundMessageHandler.java:317)
at
org.apache.cassandra.net.InboundMessageHandler$ProcessLargeMessage.provideMessage(InboundMessageHandler.java:504)
at
org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:429)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834)no* further _formatting_ is
done here{noformat}
-XX:+AlwaysPreTouch
-XX:+CrashOnOutOfMemoryError
-XX:+ExitOnOutOfMemoryError
-XX:+HeapDumpOnOutOfMemoryError
-XX:+ParallelRefProcEnabled
-XX:+PerfDisableSharedMem
-XX:+ResizeTLAB
-XX:+UseG1GC
-XX:+UseNUMA
-XX:+UseTLAB
-XX:+UseThreadPriorities
-XX:-UseBiasedLocking
-XX:CompileCommandFile=/opt/nosql/clusters/cassandra-101/conf/hotspot_compiler
-XX:G1RSetUpdatingPauseTimePercent=5
-XX:G1ReservePercent=20
-XX:HeapDumpPath=/opt/nosql/data/cluster_101/cassandra-1691623098-pid2804737.hprof
-XX:InitiatingHeapOccupancyPercent=70
-XX:MaxGCPauseMillis=200
-XX:StringTableSize=60013
-Xlog:gc*:file=/opt/nosql/clusters/cassandra-101/logs/gc.log:time,uptime:filecount=10,filesize=10485760
-Xms16G
-Xmx16G
-Xss256k
>From our Prometheus metrics, the behavior shows the direct buffer memory
>ramping up until it reaches the max and then causes an OOM. It would appear
>that direct memory is never being released by the JVM until its exhausted.
!Cluster-dm-metrics.PNG!
An Eclipse Heap Dump analyzer
||Class Name||Objects||Shallow Heap||Retained Heap||
[jira] [Commented] (CASSANDRA-18766) high speculative retries on v4.1.3
[ https://issues.apache.org/jira/browse/CASSANDRA-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755167#comment-17755167 ] Ivans Novikovs commented on CASSANDRA-18766: There are multiple clusters where I see this. All of them were upgraded from v4.0.7 to v4.1.3 using exactly same config file several weeks ago. Most of the clusters are 3 node clusters, with all nodes up and client apps using them constantly. Few clusters are larger in size. I noticed higher than usual speculative retries just now and started investigate, historical metrics show that this changed exactly during upgrade and stays consistently this way, no other anomalies could be found so far. While troubleshooting I tried to downgrade version on one of the nodes in one cluster first to v4.1.2 and then also to v4.0.7 and then back to v4.1.3. Test cluster does not have any significant load, so I used cassandra-stress to first write some test data with default settings and then to read it back on each version change. RF=3, CL=QUORUM. On test node it generates up to 6460 ops/s reads and ~7 ops/s speculative retries, but on v4.1.3 it jumps to 520 ops/s in specific test. Thank you for describing process for me, I do not have much java knowledge, but will look trough that to try to understand what could be the cause in my case if it is not a bug. Regarding node read latency I did not find anything unusual, but perhaps will do more tests and pay more attention to cassandra-stress output, not just metrics. Although additioanl speculative reads should affect anyway. If not find anything will probably look into setting up cluster with default settings, to see if I could reproduce it there. > high speculative retries on v4.1.3 > -- > > Key: CASSANDRA-18766 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18766 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Coordination >Reporter: Ivans Novikovs >Priority: Normal > Fix For: 4.1.x > > > There are up to 10+ times higher speculative retries for reads on 4.1.3 > comparing to 4.0.7 and 4.1.2 when using QUORUM and default setting of 99p. > On 4.1.3 after upgrade I see speculative retries for up to 35% of all reads > for specific table. Latency for reads is stable around 500 microseconds. > java 1.8.0_382 is used -- This message was sent by Atlassian 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 (e417d003 -> c2281833)
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 e417d003 generate docs for cceb2c06 new c2281833 generate docs for cceb2c06 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 (e417d003) \ N -- N -- N refs/heads/asf-staging (c2281833) 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] [Updated] (CASSANDRA-18752) Deal with commented assertion in UFTest#testSchemaChange
[ https://issues.apache.org/jira/browse/CASSANDRA-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18752: Since Version: (was: 5.0) > Deal with commented assertion in UFTest#testSchemaChange > > > Key: CASSANDRA-18752 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18752 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0, 5.1 > > > [~maedhroz] reported that there is an assertion left commented out in > UFTest#testSchemaChange in CASSANDRA-18252. > It should be either removed or fixed if needed. > [https://github.com/apache/cassandra/pull/2154/files#diff-d22803d878bbcebc2bfb5e73ec39cea75ae0800f3cfbeb81d0bce358ab2b3c00R118-R126] -- This message was sent by Atlassian Jira (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-18752) Deal with commented assertion in UFTest#testSchemaChange
[ https://issues.apache.org/jira/browse/CASSANDRA-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18752: Fix Version/s: 5.0 5.1 (was: 5.x) (was: 5.0.x) Since Version: 5.0 Source Control Link: https://github.com/apache/cassandra/commit/816d1ac1812cbf9aaf19c133d1d2b6087a2defad. https://github.com/apache/cassandra/commit/f713a6618fe1d9fde23b1552cd0c8fc7309e3e05 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Deal with commented assertion in UFTest#testSchemaChange > > > Key: CASSANDRA-18752 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18752 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0, 5.1 > > > [~maedhroz] reported that there is an assertion left commented out in > UFTest#testSchemaChange in CASSANDRA-18252. > It should be either removed or fixed if needed. > [https://github.com/apache/cassandra/pull/2154/files#diff-d22803d878bbcebc2bfb5e73ec39cea75ae0800f3cfbeb81d0bce358ab2b3c00R118-R126] -- This message was sent by Atlassian Jira (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-18733) Waiting indefinitely on ReceivedMessage response in StreamSession#receive() can cause deadlock
[
https://issues.apache.org/jira/browse/CASSANDRA-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18733:
Reviewers: Caleb Rackliffe, Caleb Rackliffe (was: Caleb Rackliffe)
Caleb Rackliffe, Caleb Rackliffe (was: Caleb Rackliffe)
Status: Review In Progress (was: Patch Available)
> Waiting indefinitely on ReceivedMessage response in StreamSession#receive()
> can cause deadlock
> --
>
> Key: CASSANDRA-18733
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18733
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Consistency/Streaming
>Reporter: Caleb Rackliffe
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.1.x, 5.0, 5.x
>
>
> I've observed in a recent stack trace from a node running 4.1 what looks like
> a deadlock around the {{StreamSession}} monitor lock when
> {{StreamSession#receive()}} waits via {{syncUninteruptibly()}} for a response
> to a control message.
> {noformat}
> "Messaging-EventLoop-3-10" #320 daemon prio=5 os_prio=0 cpu=57979617.98ms
> elapsed=5587916.03s tid=0x7f056e88ae00 nid=0x80ec waiting for monitor
> entry [0x7f056d277000]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.cassandra.streaming.StreamSession.closeSession(StreamSession.java:524)
> - waiting to lock <0x0006816fae70> (a
> org.apache.cassandra.streaming.StreamSession)
> at
> org.apache.cassandra.streaming.StreamSession.onError(StreamSession.java:690)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.onMessageComplete(StreamingMultiplexedChannel.java:264)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel.lambda$sendMessage$1(StreamingMultiplexedChannel.java:233)
> at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel$$Lambda$2029/0x0008007a0c40.operationComplete(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:134)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:148)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$GenericFutureListenerList.notifySelf(ListenerList.java:190)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.lambda$notifyExclusive$0(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$$Lambda$950/0x000800666040.accept(Unknown
> Source)
> at
> org.apache.cassandra.utils.concurrent.IntrusiveStack.forEach(IntrusiveStack.java:195)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyExclusive(ListenerList.java:124)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notify(ListenerList.java:96)
> at
> org.apache.cassandra.utils.concurrent.AsyncFuture.trySet(AsyncFuture.java:104)
> at
> org.apache.cassandra.utils.concurrent.AbstractFuture.tryFailure(AbstractFuture.java:148)
> at
> org.apache.cassandra.utils.concurrent.AsyncPromise.tryFailure(AsyncPromise.java:139)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:1009)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:870)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1367)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:717)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:764)
> at
> io.netty.channel.AbstractChannelHandlerContext$WriteTask.run(AbstractChannelHandlerContext.java:1071)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(java.base@11.0.16/Thread.java:829)
> {noformat}
> It seems that while {{receive()} is holding the monitor lock on
> {{StreamSession}}, the callback that executes on a different thread for the
> control message it sends carries an error. This error, when handled in
> {{onError()}},
[jira] [Commented] (CASSANDRA-18752) Deal with commented assertion in UFTest#testSchemaChange
[ https://issues.apache.org/jira/browse/CASSANDRA-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755145#comment-17755145 ] Ekaterina Dimitrova commented on CASSANDRA-18752: - To https://github.com/apache/cassandra.git ed3968bf86..816d1ac181 cassandra-5.0 -> cassandra-5.0 d058194354..f713a6618f trunk -> trunk > Deal with commented assertion in UFTest#testSchemaChange > > > Key: CASSANDRA-18752 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18752 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > [~maedhroz] reported that there is an assertion left commented out in > UFTest#testSchemaChange in CASSANDRA-18252. > It should be either removed or fixed if needed. > [https://github.com/apache/cassandra/pull/2154/files#diff-d22803d878bbcebc2bfb5e73ec39cea75ae0800f3cfbeb81d0bce358ab2b3c00R118-R126] -- This message was sent by Atlassian Jira (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-18768) Harry changes required for CEP-21 testing (NTS support, concurrent r/w improvements, and more)
Alex Petrov created CASSANDRA-18768: --- Summary: Harry changes required for CEP-21 testing (NTS support, concurrent r/w improvements, and more) Key: CASSANDRA-18768 URL: https://issues.apache.org/jira/browse/CASSANDRA-18768 Project: Cassandra Issue Type: New Feature Reporter: Alex Petrov -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/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 f713a6618fe1d9fde23b1552cd0c8fc7309e3e05 Merge: d058194354 816d1ac181 Author: Ekaterina Dimitrova AuthorDate: Wed Aug 16 11:25:34 2023 -0400 Merge branch 'cassandra-5.0' into trunk .../org/apache/cassandra/cql3/validation/entities/UFTest.java | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) - 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 (ed3968bf86 -> 816d1ac181)
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 ed3968bf86 Merge branch 'cassandra-4.1' into cassandra-5.0 add 816d1ac181 Fix UFTest#testSchemaChange No new revisions were added by this update. Summary of changes: .../org/apache/cassandra/cql3/validation/entities/UFTest.java | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (d058194354 -> f713a6618f)
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 d058194354 Merge branch 'cassandra-5.0' into trunk add 816d1ac181 Fix UFTest#testSchemaChange new f713a6618f 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: .../org/apache/cassandra/cql3/validation/entities/UFTest.java | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18767) tablestats should show speculative retries
[ https://issues.apache.org/jira/browse/CASSANDRA-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-18767: Assignee: Brandon Williams > tablestats should show speculative retries > -- > > Key: CASSANDRA-18767 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18767 > Project: Cassandra > Issue Type: Bug > Components: Observability/Metrics >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > NodeProbe makes > [provisions|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tools/NodeProbe.java#L1921] > for it, but it is never used later. -- This message was sent by Atlassian 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 (c88bc345 -> e417d003)
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 c88bc345 generate docs for cceb2c06 new e417d003 generate docs for cceb2c06 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 (c88bc345) \ N -- N -- N refs/heads/asf-staging (e417d003) 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] [Updated] (CASSANDRA-18767) tablestats should show speculative retries
[ https://issues.apache.org/jira/browse/CASSANDRA-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18767: - Bug Category: Parent values: Correctness(12982)Level 1 values: Consistency(12989) Complexity: Low Hanging Fruit Component/s: Observability/Metrics Discovered By: User Report Fix Version/s: 3.0.x 3.11.x 4.0.x 4.1.x 5.0.x 5.x Severity: Normal Status: Open (was: Triage Needed) > tablestats should show speculative retries > -- > > Key: CASSANDRA-18767 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18767 > Project: Cassandra > Issue Type: Bug > Components: Observability/Metrics >Reporter: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > NodeProbe makes > [provisions|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tools/NodeProbe.java#L1921] > for it, but it is never used later. -- This message was sent by Atlassian Jira (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-18767) tablestats should show speculative retries
Brandon Williams created CASSANDRA-18767: Summary: tablestats should show speculative retries Key: CASSANDRA-18767 URL: https://issues.apache.org/jira/browse/CASSANDRA-18767 Project: Cassandra Issue Type: Bug Reporter: Brandon Williams NodeProbe makes [provisions|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tools/NodeProbe.java#L1921] for it, but it is never used later. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
