[jira] [Comment Edited] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816259#comment-17816259 ] Saranya Krishnakumar edited comment on CASSANDRASC-101 at 2/10/24 1:04 AM: --- Makes sense, updated patch to pick up 4.5.3 version [https://github.com/apache/cassandra-sidecar/pull/97]. Added changes to allow for dynamic traffic shaping options update. Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/146] was (Author: saranya_k): Makes sense, updated patch to pick up 4.5.3 version [https://github.com/apache/cassandra-sidecar/pull/97]. Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/146] > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This leak is caused when > connection pools are recreated for vert.x HttpClient. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. As part of this we > will also pick up dynamic update capability added for read and write > thresholds set for servers > [https://github.com/eclipse-vertx/vert.x/pull/5088]. -- This message was sent by Atlassian Jira (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] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816259#comment-17816259 ] Saranya Krishnakumar commented on CASSANDRASC-101: -- Makes sense, updated patch to pick up 4.5.3 version [https://github.com/apache/cassandra-sidecar/pull/97]. Green CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/146] > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This leak is caused when > connection pools are recreated for vert.x HttpClient. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. As part of this we > will also pick up dynamic update capability added for read and write > thresholds set for servers > [https://github.com/eclipse-vertx/vert.x/pull/5088]. -- This message was sent by Atlassian Jira (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-19342) Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
[
https://issues.apache.org/jira/browse/CASSANDRA-19342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-19342:
Status: Ready to Commit (was: Review In Progress)
> Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
>
>
> Key: CASSANDRA-19342
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19342
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> junit.framework.AssertionFailedError: "RemovalStatus: No removals in
> progress. " does not contain MID_LEAVE at
> org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort(RemoveNodeTest.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=testAbort-trunk
--
This message was sent by Atlassian Jira
(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-19342) Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
[
https://issues.apache.org/jira/browse/CASSANDRA-19342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816249#comment-17816249
]
Ekaterina Dimitrova commented on CASSANDRA-19342:
-
+1, thanks
> Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
>
>
> Key: CASSANDRA-19342
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19342
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> junit.framework.AssertionFailedError: "RemovalStatus: No removals in
> progress. " does not contain MID_LEAVE at
> org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort(RemoveNodeTest.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=testAbort-trunk
--
This message was sent by Atlassian Jira
(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-19342) Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
[
https://issues.apache.org/jira/browse/CASSANDRA-19342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816241#comment-17816241
]
Ekaterina Dimitrova edited comment on CASSANDRA-19342 at 2/9/24 10:50 PM:
--
I started more repeated runs here; let's see what CircleCI will say:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=samt%2F19342]
was (Author: e.dimitrova):
I started more repeats here, let's see what CircleCI will say:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=samt%2F19342
> Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
>
>
> Key: CASSANDRA-19342
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19342
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> junit.framework.AssertionFailedError: "RemovalStatus: No removals in
> progress. " does not contain MID_LEAVE at
> org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort(RemoveNodeTest.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=testAbort-trunk
--
This message was sent by Atlassian Jira
(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-19342) Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
[
https://issues.apache.org/jira/browse/CASSANDRA-19342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816241#comment-17816241
]
Ekaterina Dimitrova commented on CASSANDRA-19342:
-
I started more repeats here, let's see what CircleCI will say:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=samt%2F19342
> Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
>
>
> Key: CASSANDRA-19342
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19342
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> junit.framework.AssertionFailedError: "RemovalStatus: No removals in
> progress. " does not contain MID_LEAVE at
> org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort(RemoveNodeTest.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=testAbort-trunk
--
This message was sent by Atlassian Jira
(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-19168) Test Failure: VectorUpdateDeleteTest fails with heap_buffers
[
https://issues.apache.org/jira/browse/CASSANDRA-19168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-19168:
Test and Documentation Plan:
Both issues were identified and fixed
[here|https://github.com/apache/cassandra/pull/3097]. We had an inaccurate
comparison of buffers (the default config issue) and we were missing some
filtering when creating a View.
This is the 5.0 branch and I have preliminary CI J11
[here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2644/workflows/c69eb9cd-04fc-498c-8683-fb42a174e987].
I will propagate to trunk and run the rest of the tests in CI when we confirm
the patches.
testServiceTopPartitionsSingleTable-system_keyspace_directory_jdk11 - known
failure from CASSANDRA-17798
Status: Patch Available (was: In Progress)
> Test Failure: VectorUpdateDeleteTest fails with heap_buffers
>
>
> Key: CASSANDRA-19168
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19168
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Vector Search
>Reporter: Branimir Lambov
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> When {{memtable_allocation_type}} is set to {{heap_buffers}}, {{updateTest}}
> fails with
> {code}
> junit.framework.AssertionFailedError: Result set does not contain a row with
> pk = 0
> at
> org.apache.cassandra.index.sai.cql.VectorTypeTest.assertContainsInt(VectorTypeTest.java:133)
> at
> org.apache.cassandra.index.sai.cql.VectorUpdateDeleteTest.updateTest(VectorUpdateDeleteTest.java:308)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19168) Test Failure: VectorUpdateDeleteTest fails with heap_buffers
[
https://issues.apache.org/jira/browse/CASSANDRA-19168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816237#comment-17816237
]
Ekaterina Dimitrova commented on CASSANDRA-19168:
-
Both issues were identified and fixed
[here|https://github.com/apache/cassandra/pull/3097]. We had an inaccurate
comparison of buffers (the default config issue) and we were missing some
filtering when creating a View.
This is the 5.0 branch and I have preliminary CI J11
[here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2644/workflows/c69eb9cd-04fc-498c-8683-fb42a174e987].
I will propagate to trunk and run the rest of the tests in CI when we confirm
the patches.
[~adelapena], do you mind to review?
testServiceTopPartitionsSingleTable-system_keyspace_directory_jdk11 - known
failure from CASSANDRA-17798
> Test Failure: VectorUpdateDeleteTest fails with heap_buffers
>
>
> Key: CASSANDRA-19168
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19168
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Vector Search
>Reporter: Branimir Lambov
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> When {{memtable_allocation_type}} is set to {{heap_buffers}}, {{updateTest}}
> fails with
> {code}
> junit.framework.AssertionFailedError: Result set does not contain a row with
> pk = 0
> at
> org.apache.cassandra.index.sai.cql.VectorTypeTest.assertContainsInt(VectorTypeTest.java:133)
> at
> org.apache.cassandra.index.sai.cql.VectorUpdateDeleteTest.updateTest(VectorUpdateDeleteTest.java:308)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> {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-19342) Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
[
https://issues.apache.org/jira/browse/CASSANDRA-19342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-19342:
Reviewers: Ekaterina Dimitrova, Ekaterina Dimitrova
Ekaterina Dimitrova, Ekaterina Dimitrova (was: Ekaterina
Dimitrova)
Status: Review In Progress (was: Patch Available)
> Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
>
>
> Key: CASSANDRA-19342
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19342
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> junit.framework.AssertionFailedError: "RemovalStatus: No removals in
> progress. " does not contain MID_LEAVE at
> org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort(RemoveNodeTest.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=testAbort-trunk
--
This message was sent by Atlassian Jira
(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-17798) Flaky org.apache.cassandra.tools TopPartitionsTest testServiceTopPartitionsSingleTable
[
https://issues.apache.org/jira/browse/CASSANDRA-17798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17798:
Fix Version/s: 5.0.x
> Flaky org.apache.cassandra.tools TopPartitionsTest
> testServiceTopPartitionsSingleTable
> --
>
> Key: CASSANDRA-17798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17798
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
>
> h3.
> {code:java}
> Error Message
> If this failed you probably have to raise the beginLocalSampling duration
> expected:<1> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: If this failed you probably have to
> raise the beginLocalSampling duration expected:<1> but was:<0> at
> org.apache.cassandra.tools.TopPartitionsTest.testServiceTopPartitionsSingleTable(TopPartitionsTest.java:83)
> 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)
> Standard Output
> INFO [main] 2022-08-02 01:49:49,333 YamlConfigurationLoader.java:104 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml DEBUG [main]
> 2022-08-02 01:49:49,339 YamlConfigurationLoader.java:124 - Loading settings
> from file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml INFO
> [main] 2022-08-02 01:49:49,642 Config.java:1167 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 50809 chars]... lizing counter cache with capacity of 2 MiBs
> INFO [MemtableFlushWriter:1] 2022-08-02 01:49:53,519 CacheService.java:163 -
> Scheduling counter cache save to every 7200 seconds (going to save all keys).
> DEBUG [MemtableFlushWriter:1] 2022-08-02 01:49:53,575
> ColumnFamilyStore.java:1330 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/nb-1-big-Data.db')]
> (1 sstables, 4.915KiB), biggest 4.915KiB, smallest 4.915KiB
> {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-19168) Test Failure: VectorUpdateDeleteTest fails with heap_buffers
[
https://issues.apache.org/jira/browse/CASSANDRA-19168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-19168:
Authors: Ekaterina Dimitrova, Joel Knighton, Michael Marshall (was:
Ekaterina Dimitrova)
> Test Failure: VectorUpdateDeleteTest fails with heap_buffers
>
>
> Key: CASSANDRA-19168
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19168
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Vector Search
>Reporter: Branimir Lambov
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> When {{memtable_allocation_type}} is set to {{heap_buffers}}, {{updateTest}}
> fails with
> {code}
> junit.framework.AssertionFailedError: Result set does not contain a row with
> pk = 0
> at
> org.apache.cassandra.index.sai.cql.VectorTypeTest.assertContainsInt(VectorTypeTest.java:133)
> at
> org.apache.cassandra.index.sai.cql.VectorUpdateDeleteTest.updateTest(VectorUpdateDeleteTest.java:308)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-website) branch asf-staging updated (d553e2b16 -> c5bcf197d)
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 d553e2b16 generate docs for a1ebc6a8 new c5bcf197d generate docs for a1ebc6a8 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 (d553e2b16) \ N -- N -- N refs/heads/asf-staging (c5bcf197d) 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 4883646 -> 4883646 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19386) BEGIN TRANSACTIONS throws error using index
[ https://issues.apache.org/jira/browse/CASSANDRA-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816204#comment-17816204 ] Lorina Poland commented on CASSANDRA-19386: --- Ah, Blake E. helped me out with a misunderstanding. `UPDATE` does indeed only work with either PRIMARY KEY or an IN of PRIMARY KEYS. I will add my examples with an explanation of why they fail in the docs. > BEGIN TRANSACTIONS throws error using index > --- > > Key: CASSANDRA-19386 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19386 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: Lorina Poland >Priority: Normal > Attachments: acid-transaction-fail.txt, acid-transaction.cql > > > I'm testing BEGIN TRANSACTION...END TRANSACTION. The only examples I've seen > use a single PRIMARY KEY. > I decided to test using a single PRIMARY KEY and an indexed column, which > seems reasonable. I only get errors. Perhaps my syntax is incorrect, but I'm > not sure how. > When I make that indexed column part of the PRIMARY KEY, the transactions > work just fine. > I've attached the CQL I'm using and the runs I've made with errors. -- This message was sent by Atlassian Jira (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-18543) Waiting for gossip to settle does not wait for live endpoints
[ https://issues.apache.org/jira/browse/CASSANDRA-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816202#comment-17816202 ] Mohammad Aburadeh commented on CASSANDRA-18543: --- Hi Everyone, Do you have any idea if this is an old bug in Cassandra or if it just happens in a specific version of Cassandra ( > 3.11.4 )? I'm asking because we upgraded our production clusters from 3.11.4 to 3.11.15 and we started getting " Unable to contact any seeds! " error when replacing dead node. We have not experienced this issue on Cassandra 3.11.4. Regards Mohammad > Waiting for gossip to settle does not wait for live endpoints > - > > Key: CASSANDRA-18543 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18543 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Cameron Zemek >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.16, 4.0.11, 4.1.3, 5.0-alpha1, 5.0 > > Attachments: gossip.patch, gossip4.patch > > Time Spent: 1h > Remaining Estimate: 0h > > When a node starts it will get endpoint states (via shadow round) but have > all nodes marked as down. The problem is the wait to settle only checks the > size of endpoint states is stable before starting Native transport. Once > native transport starts it will receive queries and fail consistency levels > such as LOCAL_QUORUM since it still thinks nodes are down. > This is problem for a number of large clusters for our customers. The cluster > has quorum but due to this issue a node restart is causing a bunch of query > errors. > My initial solution to this was to only check live endpoints size in addition > to size of endpoint states. This worked but I noticed in testing this fix > that there also a lot of duplication of checking the same node (via Echo > messages) for liveness. So the patch also removes this duplication of > checking node is UP in markAlive. > The final problem I found while testing is sometimes could still not see a > change in live endpoints due to only 1 second polling, so the patch allows > for overridding the settle parameters. I could not reliability reproduce this > but think its worth providing a way to override these hardcoded values. -- This message was sent by Atlassian Jira (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-19386) BEGIN TRANSACTIONS throws error using index
Lorina Poland created CASSANDRA-19386: - Summary: BEGIN TRANSACTIONS throws error using index Key: CASSANDRA-19386 URL: https://issues.apache.org/jira/browse/CASSANDRA-19386 Project: Cassandra Issue Type: Bug Components: Accord Reporter: Lorina Poland Attachments: acid-transaction-fail.txt, acid-transaction.cql I'm testing BEGIN TRANSACTION...END TRANSACTION. The only examples I've seen use a single PRIMARY KEY. I decided to test using a single PRIMARY KEY and an indexed column, which seems reasonable. I only get errors. Perhaps my syntax is incorrect, but I'm not sure how. When I make that indexed column part of the PRIMARY KEY, the transactions work just fine. I've attached the CQL I'm using and the runs I've made with errors. -- This message was sent by Atlassian Jira (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-19369) [Analytics] Use XXHash32 for digest calculation of SSTables
[
https://issues.apache.org/jira/browse/CASSANDRA-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-19369:
--
Reviewers: Yifan Cai
Status: Review In Progress (was: Patch Available)
> [Analytics] Use XXHash32 for digest calculation of SSTables
> ---
>
> Key: CASSANDRA-19369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19369
> Project: Cassandra
> Issue Type: Improvement
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 1h
> Remaining Estimate: 0h
>
> During bulk writes, Cassandra Analytics calculates the MD5 checksum of every
> SSTable it produces. During SSTable upload to Cassandra Sidecar, Cassandra
> Analytics includes the {{content-md5}} header as part of the upload request.
> This information is used by Cassandra Sidecar to validate the integrity of
> the uploaded SSTable and prevent issues with bit flips and corrupted SSTables.
> Recently, Cassandra Sidecar introduced [support for additional checksum
> validations|https://issues.apache.org/jira/browse/CASSANDRASC-97] during
> SSTable upload. Notably the XXHash32 digest support was added which offers
> for more performant checksum calculations. This support now allows Cassandra
> Analytics to use a more efficient digest algorithm that is friendlier on the
> CPU usage of Sidecar and spark resources.
--
This message was sent by Atlassian Jira
(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-19369) [Analytics] Use XXHash32 for digest calculation of SSTables
[
https://issues.apache.org/jira/browse/CASSANDRA-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816184#comment-17816184
]
Yifan Cai commented on CASSANDRA-19369:
---
The patch looks good to me. Thank you for addressing my comments. Adding the
XXHash32 in addition to the existing MD5 can be much more CPU efficient.
Waiting for the CI to be green :)
> [Analytics] Use XXHash32 for digest calculation of SSTables
> ---
>
> Key: CASSANDRA-19369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19369
> Project: Cassandra
> Issue Type: Improvement
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 1h
> Remaining Estimate: 0h
>
> During bulk writes, Cassandra Analytics calculates the MD5 checksum of every
> SSTable it produces. During SSTable upload to Cassandra Sidecar, Cassandra
> Analytics includes the {{content-md5}} header as part of the upload request.
> This information is used by Cassandra Sidecar to validate the integrity of
> the uploaded SSTable and prevent issues with bit flips and corrupted SSTables.
> Recently, Cassandra Sidecar introduced [support for additional checksum
> validations|https://issues.apache.org/jira/browse/CASSANDRASC-97] during
> SSTable upload. Notably the XXHash32 digest support was added which offers
> for more performant checksum calculations. This support now allows Cassandra
> Analytics to use a more efficient digest algorithm that is friendlier on the
> CPU usage of Sidecar and spark resources.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-19369 Use XXHash32 for digest calculation of SSTables [cassandra-analytics]
JeetKunDoug commented on code in PR #38:
URL:
https://github.com/apache/cassandra-analytics/pull/38#discussion_r1484658554
##
cassandra-analytics-core/src/main/java/org/apache/cassandra/spark/bulkwriter/BulkSparkConf.java:
##
@@ -128,12 +128,13 @@ public class BulkSparkConf implements Serializable
protected boolean useOpenSsl;
protected int ringRetryCount;
protected final Set blockedInstances;
+protected final DigestTypeOption digestTypeOption;
public BulkSparkConf(SparkConf conf, Map options)
{
this.conf = conf;
Optional sidecarPortFromOptions =
MapUtils.getOptionalInt(options, WriterOptions.SIDECAR_PORT.name(), "sidecar
port");
-this.userProvidedSidecarPort = sidecarPortFromOptions.isPresent() ?
sidecarPortFromOptions.get() : getOptionalInt(SIDECAR_PORT).orElse(-1);
+this.userProvidedSidecarPort = sidecarPortFromOptions.orElseGet(() ->
getOptionalInt(SIDECAR_PORT).orElse(-1));
Review Comment:
Agree with @frankgh here... I prefer `orElseGet` when using optionals.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19384) Avoid exposing intermediate node state during startup
[ https://issues.apache.org/jira/browse/CASSANDRA-19384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19384: Test and Documentation Plan: ci run Status: Patch Available (was: Open) > Avoid exposing intermediate node state during startup > - > > Key: CASSANDRA-19384 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19384 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html, result_details.tar.gz > > Time Spent: 10m > Remaining Estimate: 0h > > During startup we replay the local log, during this time we might expose > intermediate node states (via JMX for example). -- This message was sent by Atlassian Jira (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-19384) Avoid exposing intermediate node state during startup
[ https://issues.apache.org/jira/browse/CASSANDRA-19384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19384: Bug Category: Parent values: Correctness(12982)Level 1 values: Transient Incorrect Response(12987) Complexity: Low Hanging Fruit Discovered By: Adhoc Test Reviewers: Alex Petrov, Sam Tunnicliffe Severity: Low Status: Open (was: Triage Needed) Attached test results have 6 python dtest failures due to running with the wrong dtest branch (started it before merging the CASSANDRA-19189 dtest pr). And one timeout, which passes locally. > Avoid exposing intermediate node state during startup > - > > Key: CASSANDRA-19384 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19384 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html, result_details.tar.gz > > Time Spent: 10m > Remaining Estimate: 0h > > During startup we replay the local log, during this time we might expose > intermediate node states (via JMX for example). -- This message was sent by Atlassian Jira (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-19385) ALTER ROLE WITH LOGIN=FALSE and REVOKE ROLE do not disconnect existing users
Abe Ratnofsky created CASSANDRA-19385: - Summary: ALTER ROLE WITH LOGIN=FALSE and REVOKE ROLE do not disconnect existing users Key: CASSANDRA-19385 URL: https://issues.apache.org/jira/browse/CASSANDRA-19385 Project: Cassandra Issue Type: Bug Components: Messaging/Client Reporter: Abe Ratnofsky Currently, if users want to block a role from connecting to Cassandra, ALTER ROLE WITH LOGIN=FALSE and REVOKE ROLE seem like the sensible options. But these commands do not disconnect existing connections authenticated with the given role, and these connections will stay alive until they're disconnected for another reason. Subsequent attempts to connect with that role will fail. There is currently no way to disconnect all connections for a given user either. nodetool disablebinary will disconnect all client connections for a given node, and client sessions can be shut down. But in the case of a credential leak or a misconfigured user, it can be desirable to prevent login for a given role and disconnect all existing connections for that role. -- This message was sent by Atlassian Jira (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-19384) Avoid exposing intermediate node state during startup
[ https://issues.apache.org/jira/browse/CASSANDRA-19384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19384: Attachment: ci_summary.html result_details.tar.gz > Avoid exposing intermediate node state during startup > - > > Key: CASSANDRA-19384 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19384 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html, result_details.tar.gz > > Time Spent: 10m > Remaining Estimate: 0h > > During startup we replay the local log, during this time we might expose > intermediate node states (via JMX for example). -- This message was sent by Atlassian Jira (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-19384) Avoid exposing intermediate node state during startup
Marcus Eriksson created CASSANDRA-19384: --- Summary: Avoid exposing intermediate node state during startup Key: CASSANDRA-19384 URL: https://issues.apache.org/jira/browse/CASSANDRA-19384 Project: Cassandra Issue Type: Bug Components: Transactional Cluster Metadata Reporter: Marcus Eriksson Assignee: Marcus Eriksson During startup we replay the local log, during this time we might expose intermediate node states (via JMX for example). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-100) Fix flaky SSTableImportHandlerTest
[ https://issues.apache.org/jira/browse/CASSANDRASC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Guerrero updated CASSANDRASC-100: --- Fix Version/s: 1.0 Source Control Link: https://github.com/apache/cassandra-sidecar/commit/2914d57f0428643b3a92b6af8f4da1b209d80c2a Resolution: Fixed Status: Resolved (was: Ready to Commit) > Fix flaky SSTableImportHandlerTest > -- > > Key: CASSANDRASC-100 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-100 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > Fix For: 1.0 > > > Few of SSTableImportHandlerTest are flaky, causing multiple re-triggers for > PR green: > - testSucceeds > - testSucceedsWithClearRepaired > - testSucceedsWithExtendedVerify > They are failing with error: > org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue: > 'healthCheck' is a *void method* and it *cannot* be stubbed with a *return > value*! -- This message was sent by Atlassian Jira (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] (CASSANDRASC-100) Fix flaky SSTableImportHandlerTest
[ https://issues.apache.org/jira/browse/CASSANDRASC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816155#comment-17816155 ] ASF subversion and git services commented on CASSANDRASC-100: - Commit 2914d57f0428643b3a92b6af8f4da1b209d80c2a in cassandra-sidecar's branch refs/heads/trunk from Saranya Krishnakumar [ https://gitbox.apache.org/repos/asf?p=cassandra-sidecar.git;h=2914d57 ] CASSANDRASC-100 Fix flaky SSTableImportHandlerTest Patch by Saranya Krishnakumar; Reviewed by Francisco Guerrero and Yifan Cai for CASSANDRASC-100 > Fix flaky SSTableImportHandlerTest > -- > > Key: CASSANDRASC-100 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-100 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Few of SSTableImportHandlerTest are flaky, causing multiple re-triggers for > PR green: > - testSucceeds > - testSucceedsWithClearRepaired > - testSucceedsWithExtendedVerify > They are failing with error: > org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue: > 'healthCheck' is a *void method* and it *cannot* be stubbed with a *return > value*! -- This message was sent by Atlassian 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-sidecar) branch trunk updated: CASSANDRASC-100 Fix flaky SSTableImportHandlerTest
This is an automated email from the ASF dual-hosted git repository.
frankgh pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-sidecar.git
The following commit(s) were added to refs/heads/trunk by this push:
new 2914d57 CASSANDRASC-100 Fix flaky SSTableImportHandlerTest
2914d57 is described below
commit 2914d57f0428643b3a92b6af8f4da1b209d80c2a
Author: Saranya Krishnakumar
AuthorDate: Thu Feb 1 14:37:39 2024 -0800
CASSANDRASC-100 Fix flaky SSTableImportHandlerTest
Patch by Saranya Krishnakumar; Reviewed by Francisco Guerrero and Yifan Cai
for CASSANDRASC-100
---
.../sidecar/cluster/CassandraAdapterDelegate.java | 8 ++-
.../sstableuploads/BaseUploadsHandlerTest.java | 68 --
.../sstableuploads/SSTableImportHandlerTest.java | 19 +-
3 files changed, 71 insertions(+), 24 deletions(-)
diff --git
a/src/main/java/org/apache/cassandra/sidecar/cluster/CassandraAdapterDelegate.java
b/src/main/java/org/apache/cassandra/sidecar/cluster/CassandraAdapterDelegate.java
index 3e904fc..7bc3a64 100644
---
a/src/main/java/org/apache/cassandra/sidecar/cluster/CassandraAdapterDelegate.java
+++
b/src/main/java/org/apache/cassandra/sidecar/cluster/CassandraAdapterDelegate.java
@@ -129,8 +129,14 @@ public class CassandraAdapterDelegate implements
ICassandraAdapter, Host.StateLi
this.versionProvider = versionProvider;
this.cqlSessionProvider = session;
this.jmxClient = jmxClient;
-notificationListener = new JmxNotificationListener();
+notificationListener = initializeJmxListener();
+}
+
+protected JmxNotificationListener initializeJmxListener()
+{
+JmxNotificationListener notificationListener = new
JmxNotificationListener();
this.jmxClient.registerListener(notificationListener);
+return notificationListener;
}
private void maybeRegisterHostListener(@NotNull Session session)
diff --git
a/src/test/java/org/apache/cassandra/sidecar/routes/sstableuploads/BaseUploadsHandlerTest.java
b/src/test/java/org/apache/cassandra/sidecar/routes/sstableuploads/BaseUploadsHandlerTest.java
index 86ee719..30bf04b 100644
---
a/src/test/java/org/apache/cassandra/sidecar/routes/sstableuploads/BaseUploadsHandlerTest.java
+++
b/src/test/java/org/apache/cassandra/sidecar/routes/sstableuploads/BaseUploadsHandlerTest.java
@@ -49,8 +49,10 @@ import io.vertx.core.Vertx;
import io.vertx.ext.web.client.WebClient;
import io.vertx.junit5.VertxTestContext;
import org.apache.cassandra.sidecar.TestModule;
+import org.apache.cassandra.sidecar.adapters.base.CassandraTableOperations;
import org.apache.cassandra.sidecar.cluster.CassandraAdapterDelegate;
import org.apache.cassandra.sidecar.cluster.InstancesConfig;
+import org.apache.cassandra.sidecar.common.TableOperations;
import org.apache.cassandra.sidecar.config.SSTableUploadConfiguration;
import org.apache.cassandra.sidecar.config.ServiceConfiguration;
import org.apache.cassandra.sidecar.config.SidecarConfiguration;
@@ -60,6 +62,7 @@ import
org.apache.cassandra.sidecar.config.yaml.SidecarConfigurationImpl;
import org.apache.cassandra.sidecar.server.MainModule;
import org.apache.cassandra.sidecar.server.Server;
import org.apache.cassandra.sidecar.snapshots.SnapshotUtils;
+import org.jetbrains.annotations.Nullable;
import static
org.apache.cassandra.sidecar.config.yaml.TrafficShapingConfigurationImpl.DEFAULT_CHECK_INTERVAL;
import static
org.apache.cassandra.sidecar.config.yaml.TrafficShapingConfigurationImpl.DEFAULT_INBOUND_FILE_GLOBAL_BANDWIDTH_LIMIT;
@@ -68,7 +71,6 @@ import static
org.apache.cassandra.sidecar.config.yaml.TrafficShapingConfigurati
import static
org.apache.cassandra.sidecar.config.yaml.TrafficShapingConfigurationImpl.DEFAULT_PEAK_OUTBOUND_GLOBAL_BANDWIDTH_LIMIT;
import static
org.apache.cassandra.sidecar.snapshots.SnapshotUtils.mockInstancesConfig;
import static org.assertj.core.api.Assertions.assertThat;
-import static org.mockito.Mockito.doNothing;
import static org.mockito.Mockito.mock;
import static org.mockito.Mockito.when;
@@ -82,7 +84,7 @@ class BaseUploadsHandlerTest
protected Vertx vertx;
protected Server server;
protected WebClient client;
-protected CassandraAdapterDelegate mockDelegate;
+protected TestCassandraAdapterDelegate testDelegate;
protected SidecarConfiguration sidecarConfiguration;
@TempDir
protected Path temporaryPath;
@@ -90,13 +92,15 @@ class BaseUploadsHandlerTest
protected SSTableUploadConfiguration mockSSTableUploadConfiguration;
protected TrafficShapingConfiguration trafficShapingConfiguration;
protected SidecarRateLimiter ingressFileRateLimiter;
+protected CassandraTableOperations mockCFOperations;
+
+
@BeforeEach
void setup() throws InterruptedException, IOException
{
canonicalTemporaryPath = temporaryPath.toFile().getCanonicalPath();
-mockDelegate =
[jira] [Updated] (CASSANDRA-19381) StreamingTombstoneHistogramBuilder.DataHolder does not merge histogram points correctly on overflow
[ https://issues.apache.org/jira/browse/CASSANDRA-19381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-19381: --- Summary: StreamingTombstoneHistogramBuilder.DataHolder does not merge histogram points correctly on overflow (was: StreamingTombstoneHistogramBuilder.DataHolder does not merge bins correctly on overflow) > StreamingTombstoneHistogramBuilder.DataHolder does not merge histogram points > correctly on overflow > --- > > Key: CASSANDRA-19381 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19381 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable >Reporter: Ariel Weisberg >Assignee: Ariel Weisberg >Priority: Normal > Fix For: 5.0, 5.1 > > > The algorithm tries to merge the two nearest points in the histogram and > create a new point that is in between the two merged points based on the > weight of each point. This can overflow long arithmetic with the code that is > currently there and the work around is pick one of the points and just put > it there. > This can be worked around by changing the midpoint calculation to not > overflow. -- This message was sent by Atlassian Jira (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] (CASSANDRASC-100) Fix flaky SSTableImportHandlerTest
[ https://issues.apache.org/jira/browse/CASSANDRASC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816131#comment-17816131 ] Saranya Krishnakumar commented on CASSANDRASC-100: -- Repeated run CI [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar/142] > Fix flaky SSTableImportHandlerTest > -- > > Key: CASSANDRASC-100 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-100 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Few of SSTableImportHandlerTest are flaky, causing multiple re-triggers for > PR green: > - testSucceeds > - testSucceedsWithClearRepaired > - testSucceedsWithExtendedVerify > They are failing with error: > org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue: > 'healthCheck' is a *void method* and it *cannot* be stubbed with a *return > value*! -- This message was sent by Atlassian Jira (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-19383) Restarting a node causes MV unavailable exceptions afterward
[
https://issues.apache.org/jira/browse/CASSANDRA-19383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-19383:
-
Summary: Restarting a node causes MV unavailable exceptions afterward
(was: Restarting a node causes MV unavaible exceptions afterward)
> Restarting a node causes MV unavailable exceptions afterward
>
>
> Key: CASSANDRA-19383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19383
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> If a cluster is started with materialized views enabled and a client is
> constantly writing to one, when a node is restarted shortly after startup it
> may throw UEs:
> {quote}
> INFO [GossipStage:1] 2024-02-09 06:17:10,073 Gossiper.java:1419 - Node
> /10.5.11.102:7000 has restarted, now UP
> ERROR [MutationStage-2] 2024-02-09 06:17:10,074 Keyspace.java:650 - Unknown
> exception caught while attempting to update MaterializedView!
> stresstest.transport_orders
> org.apache.cassandra.exceptions.UnavailableException: Cannot achieve
> consistency level ONE
> at
> org.apache.cassandra.exceptions.UnavailableException.create(UnavailableException.java:37)
> at
> org.apache.cassandra.locator.ReplicaPlans.assureSufficientLiveReplicas(ReplicaPlans.java:169)
> at
> org.apache.cassandra.locator.ReplicaPlans.assureSufficientLiveReplicasForWrite(ReplicaPlans.java:112)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:353)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:344)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:338)
> at
> org.apache.cassandra.service.StorageProxy.wrapViewBatchResponseHandler(StorageProxy.java:1417)
> at
> org.apache.cassandra.service.StorageProxy.mutateMV(StorageProxy.java:1077)
> at
> org.apache.cassandra.db.view.TableViews.pushViewReplicaUpdates(TableViews.java:169)
> at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:645)
> at org.apache.cassandra.db.Keyspace.applyFuture(Keyspace.java:476)
> at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:223)
> at
> org.apache.cassandra.db.MutationVerbHandler.doVerb(MutationVerbHandler.java:54)
> at
> org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:78)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:97)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:45)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:430)
> at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:142)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:750)
> {quote}
> It's not immediately clear what the impact of this is since the error is on
> restart and not communicated back to the client.
--
This message was sent by Atlassian Jira
(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-19189) Revisit use of sealed period lookup tables
[
https://issues.apache.org/jira/browse/CASSANDRA-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19189:
Source Control Link:
https://github.com/apache/cassandra/commit/6ffd2677ee0d01c9e5493703a67255b0148106a4
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Revisit use of sealed period lookup tables
> --
>
> Key: CASSANDRA-19189
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19189
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Metadata snapshots are stored locally in the {{system.metadata_snapshots}}
> table, which is keyed by epoch. Snapshots are retrieved from this table for
> three purposes:
> * to replay locally during startup
> * to provide log state for a peer requesting catchup
> * to create point-in-time ClusterMetadata, for disaster recovery
> In the majority of cases, we always want to replay from the most recent
> snapshot so we can usually select the appropriate snapshot by simply scanning
> the snapshots table in reverse, which allows us to considerably simplify the
> process of looking up the desired snapshot. We will continue to persist
> historical snapshots, at least for now, so that we are able to select
> arbitrary snapshots should we want to reconstruct metadata state for
> arbitrary epochs.
--
This message was sent by Atlassian Jira
(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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Source Control Link: https://github.com/apache/cassandra/commit/6b3958f1d83777e295690a663610b6b29ed1efae Resolution: Fixed Status: Resolved (was: Ready to Commit) > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary.html, result_details.tar.gz > > -- This message was sent by Atlassian 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/02: Improve setup and initialisation of LocalLog/LogSpec
This is an automated email from the ASF dual-hosted git repository.
marcuse pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 6b3958f1d83777e295690a663610b6b29ed1efae
Author: Alex Petrov
AuthorDate: Fri Nov 17 17:13:30 2023 +0100
Improve setup and initialisation of LocalLog/LogSpec
Patch by Alex Petrov; reviewed by Sam Tunnicliffe and marcuse for
CASSANDRA-19271
---
CHANGES.txt| 1 +
.../apache/cassandra/schema/DistributedSchema.java | 9 +-
.../cassandra/tcm/ClusterMetadataService.java | 38 ++--
src/java/org/apache/cassandra/tcm/Period.java | 5 +-
src/java/org/apache/cassandra/tcm/Startup.java | 52 ++---
.../cassandra/tcm/StubClusterMetadataService.java | 8 +-
.../cassandra/tcm/listeners/SchemaListener.java| 10 +-
.../org/apache/cassandra/tcm/log/LocalLog.java | 231 -
.../org/apache/cassandra/tcm/log/LogStorage.java | 1 +
.../cassandra/tcm/log/SystemKeyspaceStorage.java | 5 +
.../distributed/test/jmx/JMXFeatureTest.java | 3 +-
.../distributed/test/log/CMSTestBase.java | 9 +-
.../test/log/ClusterMetadataTestHelper.java| 64 +++---
.../test/log/CoordinatorPathTestBase.java | 18 +-
.../distributed/test/ring/DecommissionTest.java| 9 +-
.../unit/org/apache/cassandra/ServerTestUtils.java | 41 ++--
.../apache/cassandra/hints/HintsUpgradeTest.java | 2 +
.../cassandra/service/ClientWarningsTest.java | 67 +++---
.../apache/cassandra/tcm/BootWithMetadataTest.java | 3 +-
.../cassandra/tcm/DiscoverySimulationTest.java | 7 +-
.../org/apache/cassandra/tcm/LogStateTest.java | 16 +-
.../org/apache/cassandra/tcm/log/LocalLogTest.java | 25 ++-
.../tcm/log/LogListenerNotificationTest.java | 9 +-
.../io/sstable/StressCQLSSTableWriter.java | 3 -
24 files changed, 370 insertions(+), 266 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 5ad47d72bd..64841aa886 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
5.1
+ * Improve setup and initialisation of LocalLog/LogSpec (CASSANDRA-19271)
* Refactor structure of caching metrics and expose auth cache metrics via JMX
(CASSANDRA-17062)
* Allow CQL client certificate authentication to work without sending an
AUTHENTICATE request (CASSANDRA-18857)
* Extend nodetool tpstats and system_views.thread_pools with detailed pool
parameters (CASSANDRA-19289)
diff --git a/src/java/org/apache/cassandra/schema/DistributedSchema.java
b/src/java/org/apache/cassandra/schema/DistributedSchema.java
index fbdf9c1c88..86dd1d5117 100644
--- a/src/java/org/apache/cassandra/schema/DistributedSchema.java
+++ b/src/java/org/apache/cassandra/schema/DistributedSchema.java
@@ -123,6 +123,10 @@ public class DistributedSchema implements
MetadataValue
{
keyspaceInstances.putAll(prev.keyspaceInstances);
+// If there are keyspaces in schema, but none of them are initialised,
we're in first boot. Initialise all.
+if (!prev.isEmpty() && prev.keyspaceInstances.isEmpty())
+prev = DistributedSchema.empty();
+
Keyspaces.KeyspacesDiff ksDiff = Keyspaces.diff(prev.getKeyspaces(),
getKeyspaces());
SchemaChangeNotifier schemaChangeNotifier =
Schema.instance.schemaChangeNotifier();
@@ -148,8 +152,8 @@ public class DistributedSchema implements
MetadataValue
assert delta.before.name.equals(delta.after.name);
// drop tables and views
-delta.views.dropped.forEach(v -> dropView(keyspace, v, true));
-delta.tables.dropped.forEach(t -> dropTable(keyspace, t,
true));
+delta.views.dropped.forEach(v -> dropView(keyspace, v,
loadSSTables));
+delta.tables.dropped.forEach(t -> dropTable(keyspace, t,
loadSSTables));
// add tables and views
delta.tables.created.forEach(t -> createTable(keyspace, t,
loadSSTables));
@@ -164,7 +168,6 @@ public class DistributedSchema implements
MetadataValue
keyspace.viewManager.reload(keyspaces.get(keyspace.getName()).get());
}
-//schemaChangeNotifier.notifyKeyspaceAltered(delta);
SchemaDiagnostics.keyspaceAltered(Schema.instance, delta);
});
diff --git a/src/java/org/apache/cassandra/tcm/ClusterMetadataService.java
b/src/java/org/apache/cassandra/tcm/ClusterMetadataService.java
index 01abe4abdf..1077e2dded 100644
--- a/src/java/org/apache/cassandra/tcm/ClusterMetadataService.java
+++ b/src/java/org/apache/cassandra/tcm/ClusterMetadataService.java
@@ -40,6 +40,7 @@ import org.apache.cassandra.concurrent.ScheduledExecutors;
import org.apache.cassandra.config.CassandraRelevantProperties;
import org.apache.cassandra.config.DatabaseDescriptor;
import org.apache.cassandra.exceptions.ExceptionCode;
+import
(cassandra) branch trunk updated (5ca972b145 -> 6ffd2677ee)
This is an automated email from the ASF dual-hosted git repository. marcuse pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 5ca972b145 Merge branch 'cassandra-5.0' into trunk new 6b3958f1d8 Improve setup and initialisation of LocalLog/LogSpec new 6ffd2677ee Remove sealed_periods and last_sealed_period tables The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 2 + .../org/apache/cassandra/db/SystemKeyspace.java| 102 ++- .../cassandra/dht/ByteOrderedPartitioner.java | 2 + .../cassandra/dht/OrderPreservingPartitioner.java | 2 + src/java/org/apache/cassandra/net/Verb.java| 2 +- .../schema/DistributedMetadataLogKeyspace.java | 121 +++-- .../apache/cassandra/schema/DistributedSchema.java | 9 +- .../cassandra/tcm/AbstractLocalProcessor.java | 26 +- .../cassandra/tcm/AtomicLongBackedProcessor.java | 86 +++--- .../cassandra/tcm/ClusterMetadataService.java | 66 +++-- src/java/org/apache/cassandra/tcm/Commit.java | 22 +- .../org/apache/cassandra/tcm/FetchPeerLog.java | 5 +- .../apache/cassandra/tcm/MetadataSnapshots.java| 50 +++- src/java/org/apache/cassandra/tcm/Period.java | 182 - .../cassandra/tcm/RecentlySealedPeriods.java | 140 -- .../org/apache/cassandra/tcm/RemoteProcessor.java | 2 +- src/java/org/apache/cassandra/tcm/Sealed.java | 128 - src/java/org/apache/cassandra/tcm/Startup.java | 51 ++-- .../cassandra/tcm/StubClusterMetadataService.java | 8 +- .../tcm/extensions/AbstractExtensionValue.java | 16 ++ .../tcm/listeners/MetadataSnapshotListener.java| 2 - .../cassandra/tcm/listeners/SchemaListener.java| 10 +- .../org/apache/cassandra/tcm/log/LocalLog.java | 235 +--- .../org/apache/cassandra/tcm/log/LogReader.java| 137 +- .../org/apache/cassandra/tcm/log/LogState.java | 301 - .../org/apache/cassandra/tcm/log/LogStorage.java | 34 ++- .../org/apache/cassandra/tcm/log/Replication.java | 260 -- .../cassandra/tcm/log/SystemKeyspaceStorage.java | 109 +--- .../tcm/serialization/MessageSerializers.java | 11 - .../tcm/transformations/CustomTransformation.java | 30 ++ .../cassandra/distributed/shared/ClusterUtils.java | 2 +- .../distributed/test/jmx/JMXFeatureTest.java | 3 +- .../distributed/test/log/CMSTestBase.java | 9 +- .../test/log/ClusterMetadataTestHelper.java| 63 ++--- .../test/log/CoordinatorPathTestBase.java | 33 ++- .../distributed/test/log/DistributedLogTest.java | 7 +- .../test/log/FetchLogFromPeersTest.java| 8 +- .../distributed/test/log/ForceSnapshotTest.java| 2 +- .../distributed/test/log/ReplayPersistedTest.java | 154 +++ .../test/log/SystemKeyspaceStorageTest.java| 82 ++ .../distributed/test/ring/DecommissionTest.java| 9 +- .../ClusterMetadataSingleNodeUpgradeTest.java | 2 +- .../unit/org/apache/cassandra/ServerTestUtils.java | 41 +-- .../apache/cassandra/dht/PartitionerTestCase.java | 1 + .../apache/cassandra/hints/HintsUpgradeTest.java | 2 + .../cassandra/service/ClientWarningsTest.java | 67 +++-- .../apache/cassandra/tcm/BootWithMetadataTest.java | 3 +- .../cassandra/tcm/DiscoverySimulationTest.java | 7 +- .../org/apache/cassandra/tcm/GetLogStateTest.java | 198 ++ .../org/apache/cassandra/tcm/LogStateTest.java | 16 +- .../cassandra/tcm/RecentlySealedPeriodsTest.java | 112 .../cassandra/tcm/log/DistributedLogStateTest.java | 31 +-- .../org/apache/cassandra/tcm/log/LocalLogTest.java | 25 +- .../tcm/log/LocalStorageLogStateTest.java | 24 +- .../tcm/log/LogListenerNotificationTest.java | 9 +- .../apache/cassandra/tcm/log/LogStateTestBase.java | 133 + .../io/sstable/StressCQLSSTableWriter.java | 3 - 57 files changed, 1458 insertions(+), 1739 deletions(-) delete mode 100644 src/java/org/apache/cassandra/tcm/RecentlySealedPeriods.java delete mode 100644 src/java/org/apache/cassandra/tcm/Sealed.java delete mode 100644 src/java/org/apache/cassandra/tcm/log/Replication.java create mode 100644 test/distributed/org/apache/cassandra/distributed/test/log/ReplayPersistedTest.java create mode 100644 test/unit/org/apache/cassandra/tcm/GetLogStateTest.java delete mode 100644 test/unit/org/apache/cassandra/tcm/RecentlySealedPeriodsTest.java - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail:
(cassandra-dtest) branch trunk updated: Stop trying to snapshot removed tables in snapshot_test.py
This is an automated email from the ASF dual-hosted git repository.
marcuse pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new 26b939dc Stop trying to snapshot removed tables in snapshot_test.py
26b939dc is described below
commit 26b939dca68dcc8573a7fa36b5c0598fbd1c95fb
Author: Marcus Eriksson
AuthorDate: Wed Jan 24 09:14:34 2024 +0100
Stop trying to snapshot removed tables in snapshot_test.py
Patch by marcuse; reviewed by Sam Tunnicliffe for CASSANDRA-19189
---
snapshot_test.py | 12
1 file changed, 12 deletions(-)
diff --git a/snapshot_test.py b/snapshot_test.py
index 5766f636..2a72b98d 100644
--- a/snapshot_test.py
+++ b/snapshot_test.py
@@ -343,8 +343,6 @@ class TestArchiveCommitlog(SnapshotTester):
if self.cluster.version() >= LooseVersion('5.1'):
local_dirs = self.make_snapshot(node1, 'system',
'local_metadata_log', 'local_metadata_log')
metadata_snapshot_dirs = self.make_snapshot(node1, 'system',
'metadata_snapshots', 'metadata_snapshots')
-sealed_dirs = self.make_snapshot(node1, 'system',
'metadata_sealed_periods', 'metadata_sealed_periods')
-last_sealed_dirs = self.make_snapshot(node1, 'system',
'metadata_last_sealed_period', 'metadata_last_sealed_period')
cluster_metadata_snapshot_dirs = self.make_snapshot(node1,
'system_cluster_metadata', 'distributed_metadata_log',
'distributed_metadata_log')
try:
@@ -427,10 +425,6 @@ class TestArchiveCommitlog(SnapshotTester):
self.restore_snapshot(local_dir, node1, 'system',
'local_metadata_log', 'local_metadata_log')
for snapshot_dir in metadata_snapshot_dirs:
self.restore_snapshot(snapshot_dir, node1, 'system',
'metadata_snapshots', 'metadata_snapshots')
-for sealed_dir in sealed_dirs:
-self.restore_snapshot(sealed_dir, node1, 'system',
'metadata_sealed_periods', 'metadata_sealed_periods')
-for last_sealed_dir in last_sealed_dirs:
-self.restore_snapshot(last_sealed_dir, node1, 'system',
'metadata_last_sealed_period', 'metadata_last_sealed_period')
for cm_dir in cluster_metadata_snapshot_dirs:
self.restore_snapshot(cm_dir, node1,
'system_cluster_metadata', 'distributed_metadata_log',
'distributed_metadata_log')
@@ -508,12 +502,6 @@ class TestArchiveCommitlog(SnapshotTester):
logger.debug("removing snapshot_dir: " +
",".join(metadata_snapshot_dirs))
for metadata_snapshot_dir in metadata_snapshot_dirs:
shutil.rmtree(metadata_snapshot_dir)
-logger.debug("removing snapshot_dir: " + ",".join(sealed_dirs))
-for sealed_snapshot_dir in sealed_dirs:
-shutil.rmtree(sealed_snapshot_dir)
-logger.debug("removing snapshot_dir: " +
",".join(last_sealed_dirs))
-for last_sealed_snapshot_dir in last_sealed_dirs:
-shutil.rmtree(last_sealed_snapshot_dir)
logger.debug("removing snapshot_dir: " +
",".join(cluster_metadata_snapshot_dirs))
for cm_snapshot_dir in cluster_metadata_snapshot_dirs:
shutil.rmtree(cm_snapshot_dir)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19189) Revisit use of sealed period lookup tables
[
https://issues.apache.org/jira/browse/CASSANDRA-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816102#comment-17816102
]
Marcus Eriksson commented on CASSANDRA-19189:
-
attached test run on CASSANDRA-19271 including this patch
> Revisit use of sealed period lookup tables
> --
>
> Key: CASSANDRA-19189
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19189
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Metadata snapshots are stored locally in the {{system.metadata_snapshots}}
> table, which is keyed by epoch. Snapshots are retrieved from this table for
> three purposes:
> * to replay locally during startup
> * to provide log state for a peer requesting catchup
> * to create point-in-time ClusterMetadata, for disaster recovery
> In the majority of cases, we always want to replay from the most recent
> snapshot so we can usually select the appropriate snapshot by simply scanning
> the snapshots table in reverse, which allows us to considerably simplify the
> process of looking up the desired snapshot. We will continue to persist
> historical snapshots, at least for now, so that we are able to select
> arbitrary snapshots should we want to reconstruct metadata state for
> arbitrary epochs.
--
This message was sent by Atlassian Jira
(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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816101#comment-17816101 ] Marcus Eriksson commented on CASSANDRA-19271: - Attaching test results - the pydtest failures were due to me running on the wrong dtest-branch. Test run includes both this and CASSANDRA-19189 > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary.html, result_details.tar.gz > > -- This message was sent by Atlassian Jira (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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Attachment: ci_summary.html result_details.tar.gz > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary.html, result_details.tar.gz > > -- This message was sent by Atlassian Jira (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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Attachment: (was: ci_summary.html) > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary.html, result_details.tar.gz > > -- This message was sent by Atlassian Jira (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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Attachment: (was: ci_summary-1.html) > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary.html, result_details.tar.gz > > -- This message was sent by Atlassian Jira (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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Attachment: (was: result_details.tar.gz) > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary.html, result_details.tar.gz > > -- This message was sent by Atlassian Jira (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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Attachment: (was: result_details.tar-1.gz) > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary.html, result_details.tar.gz > > -- This message was sent by Atlassian Jira (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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Reviewers: Marcus Eriksson, Sam Tunnicliffe (was: Sam Tunnicliffe) Status: Review In Progress (was: Patch Available) > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary-1.html, ci_summary.html, > result_details.tar-1.gz, result_details.tar.gz > > -- This message was sent by Atlassian Jira (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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Status: Ready to Commit (was: Review In Progress) +1 > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary-1.html, ci_summary.html, > result_details.tar-1.gz, result_details.tar.gz > > -- This message was sent by Atlassian Jira (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-19383) Restarting a node causes MV unavaible exceptions afterward
[
https://issues.apache.org/jira/browse/CASSANDRA-19383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816036#comment-17816036
]
Brandon Williams commented on CASSANDRA-19383:
--
This only happens in certain configurations - 6 nodes reproduces easily, but 3
does not.
> Restarting a node causes MV unavaible exceptions afterward
> --
>
> Key: CASSANDRA-19383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19383
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> If a cluster is started with materialized views enabled and a client is
> constantly writing to one, when a node is restarted shortly after startup it
> may throw UEs:
> {quote}
> INFO [GossipStage:1] 2024-02-09 06:17:10,073 Gossiper.java:1419 - Node
> /10.5.11.102:7000 has restarted, now UP
> ERROR [MutationStage-2] 2024-02-09 06:17:10,074 Keyspace.java:650 - Unknown
> exception caught while attempting to update MaterializedView!
> stresstest.transport_orders
> org.apache.cassandra.exceptions.UnavailableException: Cannot achieve
> consistency level ONE
> at
> org.apache.cassandra.exceptions.UnavailableException.create(UnavailableException.java:37)
> at
> org.apache.cassandra.locator.ReplicaPlans.assureSufficientLiveReplicas(ReplicaPlans.java:169)
> at
> org.apache.cassandra.locator.ReplicaPlans.assureSufficientLiveReplicasForWrite(ReplicaPlans.java:112)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:353)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:344)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:338)
> at
> org.apache.cassandra.service.StorageProxy.wrapViewBatchResponseHandler(StorageProxy.java:1417)
> at
> org.apache.cassandra.service.StorageProxy.mutateMV(StorageProxy.java:1077)
> at
> org.apache.cassandra.db.view.TableViews.pushViewReplicaUpdates(TableViews.java:169)
> at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:645)
> at org.apache.cassandra.db.Keyspace.applyFuture(Keyspace.java:476)
> at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:223)
> at
> org.apache.cassandra.db.MutationVerbHandler.doVerb(MutationVerbHandler.java:54)
> at
> org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:78)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:97)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:45)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:430)
> at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:142)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:750)
> {quote}
> It's not immediately clear what the impact of this is since the error is on
> restart and not communicated back to the client.
--
This message was sent by Atlassian Jira
(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-19383) Restarting a node causes MV unavaible exceptions afterward
[
https://issues.apache.org/jira/browse/CASSANDRA-19383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-19383:
-
Bug Category: Parent values: Availability(12983)Level 1 values:
Unavailable(12994)
Complexity: Normal
Discovered By: User Report
Fix Version/s: 4.0.x
4.1.x
5.0.x
5.x
Severity: Normal
Status: Open (was: Triage Needed)
> Restarting a node causes MV unavaible exceptions afterward
> --
>
> Key: CASSANDRA-19383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19383
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> If a cluster is started with materialized views enabled and a client is
> constantly writing to one, when a node is restarted shortly after startup it
> may throw UEs:
> {quote}
> INFO [GossipStage:1] 2024-02-09 06:17:10,073 Gossiper.java:1419 - Node
> /10.5.11.102:7000 has restarted, now UP
> ERROR [MutationStage-2] 2024-02-09 06:17:10,074 Keyspace.java:650 - Unknown
> exception caught while attempting to update MaterializedView!
> stresstest.transport_orders
> org.apache.cassandra.exceptions.UnavailableException: Cannot achieve
> consistency level ONE
> at
> org.apache.cassandra.exceptions.UnavailableException.create(UnavailableException.java:37)
> at
> org.apache.cassandra.locator.ReplicaPlans.assureSufficientLiveReplicas(ReplicaPlans.java:169)
> at
> org.apache.cassandra.locator.ReplicaPlans.assureSufficientLiveReplicasForWrite(ReplicaPlans.java:112)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:353)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:344)
> at
> org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:338)
> at
> org.apache.cassandra.service.StorageProxy.wrapViewBatchResponseHandler(StorageProxy.java:1417)
> at
> org.apache.cassandra.service.StorageProxy.mutateMV(StorageProxy.java:1077)
> at
> org.apache.cassandra.db.view.TableViews.pushViewReplicaUpdates(TableViews.java:169)
> at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:645)
> at org.apache.cassandra.db.Keyspace.applyFuture(Keyspace.java:476)
> at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:223)
> at
> org.apache.cassandra.db.MutationVerbHandler.doVerb(MutationVerbHandler.java:54)
> at
> org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:78)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:97)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:45)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:430)
> at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:142)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:750)
> {quote}
> It's not immediately clear what the impact of this is since the error is on
> restart and not communicated back to the client.
--
This message was sent by Atlassian Jira
(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-19383) Restarting a node causes MV unavaible exceptions afterward
Brandon Williams created CASSANDRA-19383:
Summary: Restarting a node causes MV unavaible exceptions afterward
Key: CASSANDRA-19383
URL: https://issues.apache.org/jira/browse/CASSANDRA-19383
Project: Cassandra
Issue Type: Bug
Components: Feature/Materialized Views
Reporter: Brandon Williams
If a cluster is started with materialized views enabled and a client is
constantly writing to one, when a node is restarted shortly after startup it
may throw UEs:
{quote}
INFO [GossipStage:1] 2024-02-09 06:17:10,073 Gossiper.java:1419 - Node
/10.5.11.102:7000 has restarted, now UP
ERROR [MutationStage-2] 2024-02-09 06:17:10,074 Keyspace.java:650 - Unknown
exception caught while attempting to update MaterializedView!
stresstest.transport_orders
org.apache.cassandra.exceptions.UnavailableException: Cannot achieve
consistency level ONE
at
org.apache.cassandra.exceptions.UnavailableException.create(UnavailableException.java:37)
at
org.apache.cassandra.locator.ReplicaPlans.assureSufficientLiveReplicas(ReplicaPlans.java:169)
at
org.apache.cassandra.locator.ReplicaPlans.assureSufficientLiveReplicasForWrite(ReplicaPlans.java:112)
at
org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:353)
at
org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:344)
at
org.apache.cassandra.locator.ReplicaPlans.forWrite(ReplicaPlans.java:338)
at
org.apache.cassandra.service.StorageProxy.wrapViewBatchResponseHandler(StorageProxy.java:1417)
at
org.apache.cassandra.service.StorageProxy.mutateMV(StorageProxy.java:1077)
at
org.apache.cassandra.db.view.TableViews.pushViewReplicaUpdates(TableViews.java:169)
at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:645)
at org.apache.cassandra.db.Keyspace.applyFuture(Keyspace.java:476)
at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:223)
at
org.apache.cassandra.db.MutationVerbHandler.doVerb(MutationVerbHandler.java:54)
at
org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:78)
at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:97)
at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:45)
at
org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:430)
at
org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:142)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:750)
{quote}
It's not immediately clear what the impact of this is since the error is on
restart and not communicated back to the client.
--
This message was sent by Atlassian 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 (bf2d01802 -> d553e2b16)
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 bf2d01802 generate docs for a1ebc6a8 new d553e2b16 generate docs for a1ebc6a8 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 (bf2d01802) \ N -- N -- N refs/heads/asf-staging (d553e2b16) 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: .../managing/tools/nodetool/gettimeout.html| 3 +-- .../tools/nodetool/invalidatecountercache.html | 3 +-- .../managing/tools/nodetool/gettimeout.html| 3 +-- .../tools/nodetool/invalidatecountercache.html | 3 +-- content/search-index.js| 2 +- site-ui/build/ui-bundle.zip| Bin 4883646 -> 4883646 bytes 6 files changed, 5 insertions(+), 9 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19189) Revisit use of sealed period lookup tables
[
https://issues.apache.org/jira/browse/CASSANDRA-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815977#comment-17815977
]
Alex Petrov commented on CASSANDRA-19189:
-
+1, great to simplify snapshots so much
> Revisit use of sealed period lookup tables
> --
>
> Key: CASSANDRA-19189
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19189
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html, result_details.tar.gz
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Metadata snapshots are stored locally in the {{system.metadata_snapshots}}
> table, which is keyed by epoch. Snapshots are retrieved from this table for
> three purposes:
> * to replay locally during startup
> * to provide log state for a peer requesting catchup
> * to create point-in-time ClusterMetadata, for disaster recovery
> In the majority of cases, we always want to replay from the most recent
> snapshot so we can usually select the appropriate snapshot by simply scanning
> the snapshots table in reverse, which allows us to considerably simplify the
> process of looking up the desired snapshot. We will continue to persist
> historical snapshots, at least for now, so that we are able to select
> arbitrary snapshots should we want to reconstruct metadata state for
> arbitrary epochs.
--
This message was sent by Atlassian Jira
(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-19342) Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
[
https://issues.apache.org/jira/browse/CASSANDRA-19342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815966#comment-17815966
]
Sam Tunnicliffe commented on CASSANDRA-19342:
-
bq. we might want to run it again 1000 times, not only 200. To be on the safe
side.
Yep, that would be great. Unfortunately, I could only manage to get 200
iterations using the circle free tier config as the jobs time out after an
hour.
> Test Failure: org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort
>
>
> Key: CASSANDRA-19342
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19342
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> junit.framework.AssertionFailedError: "RemovalStatus: No removals in
> progress. " does not contain MID_LEAVE at
> org.apache.cassandra.distributed.test.RemoveNodeTest.testAbort(RemoveNodeTest.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=testAbort-trunk
--
This message was sent by Atlassian Jira
(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-19271) Improve setup and initialisation of LocalLog/LogSpec
[ https://issues.apache.org/jira/browse/CASSANDRA-19271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19271: Attachment: ci_summary-1.html result_details.tar-1.gz > Improve setup and initialisation of LocalLog/LogSpec > > > Key: CASSANDRA-19271 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19271 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Fix For: 5.1 > > Attachments: ci_summary-1.html, ci_summary.html, > result_details.tar-1.gz, result_details.tar.gz > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
