[cassandra-website] branch asf-staging updated (242d9e018 -> 4bf2600b1)
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 242d9e018 generate docs for d7f28f31 new 4bf2600b1 generate docs for d7f28f31 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 (242d9e018) \ N -- N -- N refs/heads/asf-staging (4bf2600b1) 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 4881369 -> 4881369 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-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&focusedCommentId=17761441#comment-17761441
]
Michael Semb Wever commented on CASSANDRA-18733:
Looks like this broke many of the
dtest-large.replace_address_test.TestReplaceAddress tests.
* https://ci-cassandra.apache.org/job/Cassandra-5.0/18/
*
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-5.0/detail/Cassandra-5.0/18/tests
*
https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-5.0/cassandra-5.0
> 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.4, 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 {{recei
[jira] [Updated] (CASSANDRA-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Reviewers: Andres de la Peña, Andres de la Peña (was: Andres de la Peña)
Andres de la Peña, Andres de la Peña (was: Andres de la Peña)
Status: Review In Progress (was: Patch Available)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Status: Patch Available (was: Ready to Commit)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Status: Ready to Commit (was: Review In Progress)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Status: Patch Available (was: In Progress)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Reviewers: Andres de la Peña, Andres de la Peña (was: Andres de la Peña)
Andres de la Peña, Andres de la Peña (was: Andres de la Peña)
Status: Review In Progress (was: Patch Available)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761415#comment-17761415
]
Andres de la Peña commented on CASSANDRA-17476:
---
10K runs for 5.0 and trunk don't reproduce it either:
* 4.0:
[https://app.circleci.com/pipelines/github/adelapena/cassandra/3196/workflows/5a0dd468-8ff1-4af2-acc2-84900fbcff29]
* trunk:
[https://app.circleci.com/pipelines/github/adelapena/cassandra/3197/workflows/ad967712-974c-4742-93d6-361caea11bcb]
Those runs don't hit the related CASSANDRA-17475 either.
Butler reports other relatively recent failures on {{ImportTest}}, but not this
one. So yes, I think we can close this ticket as "can't repro".
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Status: In Progress (was: Patch Available)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Status: Ready to Commit (was: Review In Progress)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Status: Patch Available (was: Ready to Commit)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17475) Test failure: org.apache.cassandra.db.ImportTest.testImportInvalidateCache
[
https://issues.apache.org/jira/browse/CASSANDRA-17475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761414#comment-17761414
]
Andres de la Peña commented on CASSANDRA-17475:
---
It seems that it still doesn't reproduce with 10K iterations in the multiplexer:
* 4.0:
[https://app.circleci.com/pipelines/github/adelapena/cassandra/3196/workflows/5a0dd468-8ff1-4af2-acc2-84900fbcff29]
* trunk:
[https://app.circleci.com/pipelines/github/adelapena/cassandra/3197/workflows/ad967712-974c-4742-93d6-361caea11bcb]
The last reproduction in Jenkins is from [Aug
24|https://ci-cassandra.apache.org/job/Cassandra-trunk/1685/testReport/org.apache.cassandra.db/ImportTest/testImportInvalidateCache_compression_jdk11/]
for trunk, a particularly bad run. So it's either a Jenkins-only failure, as
it was when first reported, or it has recently been fixed.
> Test failure: org.apache.cassandra.db.ImportTest.testImportInvalidateCache
> --
>
> Key: CASSANDRA-17475
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17475
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x
>
>
> Intermittent failure in
> {{org.apache.cassandra.db.ImportTest#testImportInvalidateCache}} in 4.0:
> [https://ci-cassandra.apache.org/job/Cassandra-4.0/365/testReport/org.apache.cassandra.db/ImportTest/testImportInvalidateCache_compression/]
> {code:java}
> Failed 1 times in the last 27 runs. Flakiness: 3%, Stability: 96%
> Error Message
> expected:<10> but was:<20>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<10> but was:<20>
> at
> org.apache.cassandra.db.ImportTest.testImportInvalidateCache(ImportTest.java:537)
> 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-03-22 18:08:35,065 YamlConfigurationLoader.java:97 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2022-03-22 18:08:35,078 YamlConfigurationLoader.java:116 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2022-03-22 18:08:35,198 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2022-03-22 18:08:35,227 PlatformDependent0
> ...[truncated 1295721 chars]...
> ed transaction log, deleting
> /home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb_txn_flush_25995250-aa0b-11ec-b648-21f6c2fa4f09.log
>
> DEBUG [MemtableFlushWriter:1] 2022-03-22 18:08:59,398
> ColumnFamilyStore.java:1197 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-90-big-Data.db')]
> (1 sstables, 4.895KiB), biggest 4.895KiB, smallest 4.895KiB
> {code}
> There is only one failure in Jenkins, and I haven't been able to reproduce
> the failure with 1000 rounds in the multiplexer, with and without compression:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/1411/workflows/01965c3d-3e5b-4f8f-b77c-248e2766518a]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/1414/workflows/6a872fa8-536f-4a71-a689-4e8b8c3735a5]
--
This message was sent by Atlassian 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 (5ef3bc78b -> 242d9e018)
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 5ef3bc78b generate docs for d7f28f31 new 242d9e018 generate docs for d7f28f31 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 (5ef3bc78b) \ N -- N -- N refs/heads/asf-staging (242d9e018) 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 4881369 -> 4881369 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-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761411#comment-17761411 ] Brandon Williams commented on CASSANDRA-18366: -- Alright, we'll stick with your original patch. > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[
https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761408#comment-17761408
]
dan jatnieks commented on CASSANDRA-18366:
--
{quote}the 4.1 version of FailingRepairTest, I see a similar change there:
[https://github.com/apache/cassandra/blob/20125c5053586ab46fa341ac71cc525b64932873/test/distributed/org/apache/cassandra/distributed/test/FailingRepairTest.java#L169-L172]
Maybe it's better to port that change back to 4.0 to keep things consistent?
{quote}
Well, just porting that one change to {{FailingRepairTest}} isn't going to
work. It was part of CASSANDRA-17116 which also added code to have the
{{InstanceKiller}} shutdown the instance when {{killCurrentJVM}} is called.
[https://github.com/apache/cassandra/blob/20125c5053586ab46fa341ac71cc525b64932873/test/distributed/org/apache/cassandra/distributed/impl/Instance.java#L683]
Since that's not in 4.0, the instance is not shutdown, and porting just that
change to {{FailingRepairTest}} from 4.1 doesn't fix the test.
So, unless we want to port all of CASSANDRA-17116 back to 4.0, the original
change I proposed that just re-starts gossip should be okay for 4.0.
> Test failure: org.apache.cassandra.distributed.test.FailingRepairTest -
> testFailingMessage[VALIDATION_REQ/parallel/true]
>
>
> Key: CASSANDRA-18366
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18366
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Assignee: dan jatnieks
>Priority: Normal
> Fix For: 4.0.x
>
>
> First seen
> [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206]
> this test times out for me consistently on both j8 and j11 where 4.1 and
> trunk do not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18815) Fix dtests: replace_address_test.TestReplaceAddress.test_restart_failed_replace and others
[
https://issues.apache.org/jira/browse/CASSANDRA-18815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761407#comment-17761407
]
Jon Meredith commented on CASSANDRA-18815:
--
The difference in behavior is interesting and I don't have a good explanation
for. The clusters we saw the deadlock on were running 4.1 and the changes in
18733 could definitely affect the order threads see the message.
If the test is causing the log error, then adding a suppression for it seems
like the way to go.
> Fix dtests:
> replace_address_test.TestReplaceAddress.test_restart_failed_replace and others
> --
>
> Key: CASSANDRA-18815
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18815
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> https://ci-cassandra.apache.org/job/Cassandra-5.0/18/testReport/dtest-large.replace_address_test/TestReplaceAddress/test_restart_failed_replace/
> This and other similar tests recently started failing:
> {noformat}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[replacement] 'ERROR [Stream-Deserializer-/127.0.0.1:7000-91782e47]
> 2023-08-29 23:05:51,677 StreamSession.java:700 - [Stream
> #990152d0-46c0-11ee-9290-158c46e94542] Socket closed before session
> completion, peer 127.0.0.1:7000 is probably
> down.\njava.nio.channels.ClosedChannelException: null\n\tat
> org.apache.cassandra.net.AsyncStreamingInputPlus.reBuffer(AsyncStreamingInputPlus.java:119)\n\tat
>
> org.apache.cassandra.io.util.RebufferingInputStream.readByte(RebufferingInputStream.java:178)\n\tat
>
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:49)\n\tat
>
> org.apache.cassandra.streaming.StreamDeserializingTask.run(StreamDeserializingTask.java:59)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:833)']
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18815) Fix dtests: replace_address_test.TestReplaceAddress.test_restart_failed_replace and others
[
https://issues.apache.org/jira/browse/CASSANDRA-18815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761404#comment-17761404
]
Brandon Williams commented on CASSANDRA-18815:
--
After digging into this a bit I think this error, though newly appearing, is
actually correct and was missing before: all the dtests that are failing are
resuming or restarting an operation, so they are indeed causing a failure in
the stream session in order to facilitate that. This would mean that
CASSANDRA-18733 actually fixed whatever was suppressing this message before,
and the bug is now in 4.1 where we don't see it. WDYT, [~jmeredithco]?
If this is the case, then in this ticket we should accept this error in the
dtests, and make a new ticket to fix whatever is hiding it in 4.1.
> Fix dtests:
> replace_address_test.TestReplaceAddress.test_restart_failed_replace and others
> --
>
> Key: CASSANDRA-18815
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18815
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> https://ci-cassandra.apache.org/job/Cassandra-5.0/18/testReport/dtest-large.replace_address_test/TestReplaceAddress/test_restart_failed_replace/
> This and other similar tests recently started failing:
> {noformat}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[replacement] 'ERROR [Stream-Deserializer-/127.0.0.1:7000-91782e47]
> 2023-08-29 23:05:51,677 StreamSession.java:700 - [Stream
> #990152d0-46c0-11ee-9290-158c46e94542] Socket closed before session
> completion, peer 127.0.0.1:7000 is probably
> down.\njava.nio.channels.ClosedChannelException: null\n\tat
> org.apache.cassandra.net.AsyncStreamingInputPlus.reBuffer(AsyncStreamingInputPlus.java:119)\n\tat
>
> org.apache.cassandra.io.util.RebufferingInputStream.readByte(RebufferingInputStream.java:178)\n\tat
>
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:49)\n\tat
>
> org.apache.cassandra.streaming.StreamDeserializingTask.run(StreamDeserializingTask.java:59)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:833)']
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (83af0a939 -> 5ef3bc78b)
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 83af0a939 generate docs for d7f28f31 new 5ef3bc78b generate docs for d7f28f31 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 (83af0a939) \ N -- N -- N refs/heads/asf-staging (5ef3bc78b) 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/statusbinary.html | 3 +-- .../managing/tools/nodetool/statusbinary.html | 3 +-- content/search-index.js| 2 +- site-ui/build/ui-bundle.zip| Bin 4881369 -> 4881369 bytes 4 files changed, 3 insertions(+), 5 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18787) Replace obsolete Python functions
[ https://issues.apache.org/jira/browse/CASSANDRA-18787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18787: - Status: Ready to Commit (was: Review In Progress) > Replace obsolete Python functions > - > > Key: CASSANDRA-18787 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18787 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > Fix For: 5.x > > > # Python's stdlib datetime.timezone.utc can replace the custom UTC timezone > in pylib/cqlshlib/util.py. > # Removed unused attributes and functions: > ## field_size _limit > ## trim_if_present() > ## maybe_ensure_text() > # Simplify cql_version handling into a settor > Functionality should remain the same while simplifying the code by > eliminating ~60 lines. -- This message was sent by Atlassian 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-18787) Replace obsolete Python functions
[ https://issues.apache.org/jira/browse/CASSANDRA-18787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18787: - Fix Version/s: 5.1 (was: 5.x) Source Control Link: https://github.com/apache/cassandra/commit/abe09cff346c6f9cb5bc6dbd8e873364c05e026a Resolution: Fixed Status: Resolved (was: Ready to Commit) And with that, I have committed this. Thanks! > Replace obsolete Python functions > - > > Key: CASSANDRA-18787 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18787 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > Fix For: 5.1 > > > # Python's stdlib datetime.timezone.utc can replace the custom UTC timezone > in pylib/cqlshlib/util.py. > # Removed unused attributes and functions: > ## field_size _limit > ## trim_if_present() > ## maybe_ensure_text() > # Simplify cql_version handling into a settor > Functionality should remain the same while simplifying the code by > eliminating ~60 lines. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Clean up obsolete functions and simplify cql_version handling in cqlsh
This is an automated email from the ASF dual-hosted git repository.
brandonwilliams pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new abe09cff34 Clean up obsolete functions and simplify cql_version
handling in cqlsh
abe09cff34 is described below
commit abe09cff346c6f9cb5bc6dbd8e873364c05e026a
Author: Brad Schoening
AuthorDate: Wed Aug 30 23:07:48 2023 -0400
Clean up obsolete functions and simplify cql_version handling in cqlsh
Patch by Brad Schoening; reviewed by brandonwilliams and edimitrova for
CASSANDRA-18787
---
CHANGES.txt | 1 +
conf/cqlshrc.sample | 7 ---
pylib/cqlshlib/cqlshmain.py | 85 -
pylib/cqlshlib/formatting.py| 19 -
pylib/cqlshlib/test/test_unicode.py | 4 +-
pylib/cqlshlib/util.py | 22 --
6 files changed, 40 insertions(+), 98 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 1ef6464363..18b8622715 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
5.1
+ * Clean up obsolete functions and simplify cql_version handling in cqlsh
(CASSANDRA-18787)
Merged from 5.0:
* Fix Depends and Build-Depends for Java for Debian packages (CASSANDRA-18809)
* Update command line flags --add-exports and --add-opens for JDK17
(CASSANDRA-18439)
diff --git a/conf/cqlshrc.sample b/conf/cqlshrc.sample
index 56011f4927..c396edfed9 100644
--- a/conf/cqlshrc.sample
+++ b/conf/cqlshrc.sample
@@ -99,18 +99,11 @@ port = 9042
-[csv]
-;; The size limit for parsed fields
-; field_size_limit = 131072
-
-
-
[tracing]
;; The max number of seconds to wait for a trace to complete
; max_trace_wait = 10.0
-
;[ssl]
; certfile = ~/keys/cassandra.cert
diff --git a/pylib/cqlshlib/cqlshmain.py b/pylib/cqlshlib/cqlshmain.py
index 8161885ffa..84be503668 100755
--- a/pylib/cqlshlib/cqlshmain.py
+++ b/pylib/cqlshlib/cqlshmain.py
@@ -17,7 +17,6 @@
import cmd
import codecs
import configparser
-import csv
import getpass
import argparse
import os
@@ -277,22 +276,10 @@ class DecodeError(Exception):
return '<%s %s>' % (self.__class__.__name__, self.message())
-def maybe_ensure_text(val):
-return str(val) if val else val
-
-
class FormatError(DecodeError):
verb = 'format'
-def full_cql_version(ver):
-while ver.count('.') < 2:
-ver += '.0'
-ver_parts = ver.split('-', 1) + ['']
-vertuple = tuple(list(map(int, ver_parts[0].split('.'))) + [ver_parts[1]])
-return ver, vertuple
-
-
def format_value(val, cqltype, encoding, addcolor=False, date_time_format=None,
float_precision=None, colormap=None, nullval=None):
if isinstance(val, DecodeError):
@@ -412,7 +399,7 @@ class Shell(cmd.Cmd):
self.session.row_factory = ordered_dict_factory
self.session.default_consistency_level = cassandra.ConsistencyLevel.ONE
self.get_connection_versions()
-self.set_expanded_cql_version(self.connection_versions['cql'])
+self.set_cql_version(self.connection_versions['cql'])
self.current_keyspace = keyspace
@@ -450,6 +437,13 @@ class Shell(cmd.Cmd):
self.single_statement = single_statement
self.is_subshell = is_subshell
+self.cql_version = None
+self.cql_version_str = None
+
+# configure length of history shown
+self.max_history_length_shown = 50
+self.lastcmd = ""
+
def check_build_versions(self):
baseversion = self.connection_versions['build']
extra = baseversion.rfind('-')
@@ -462,13 +456,12 @@ class Shell(cmd.Cmd):
def batch_mode(self):
return not self.tty
-def set_expanded_cql_version(self, ver):
-ver, vertuple = full_cql_version(ver)
-self.cql_version = ver
-self.cql_ver_tuple = vertuple
-
-def cqlver_atleast(self, major, minor=0, patch=0):
-return self.cql_ver_tuple[:3] >= (major, minor, patch)
+def set_cql_version(self, ver):
+v = list(map(int, (ver.split("."
+while (len(v) < 3):
+v.append(0)
+self.cql_version = tuple(v)
+self.cql_version_str = ".".join(map(str, v))
def myformat_value(self, val, cqltype=None, **kwargs):
if isinstance(val, DecodeError):
@@ -510,12 +503,8 @@ class Shell(cmd.Cmd):
self.port))
def show_version(self):
-vers = self.connection_versions.copy()
-vers['shver'] = version
-# system.Versions['cql'] apparently does not reflect changes with
-# set_cql_version.
-vers['cql'] = self.cql_version
-print("[cqlsh %(shver)s | Cassandra %(build)s | CQL spec %(cql)s |
Native protocol v%(protocol)s]" % vers)
+vers = self.connection_versions
+print(f"[cqlsh {version} | Cassandra {vers['build']} | CQL spec
{self.cql_vers
[jira] [Commented] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761389#comment-17761389 ] dan jatnieks commented on CASSANDRA-18366: -- Ok, I'll do that and submit a new PR. > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761387#comment-17761387 ] Brandon Williams commented on CASSANDRA-18366: -- bq. Maybe it's better to port that change back to 4.0 to keep things consistent? +1 to that > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[
https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761384#comment-17761384
]
dan jatnieks commented on CASSANDRA-18366:
--
> Do you know why this wasn't a problem on 4.1 or later?
tbh, I hadn't checked, but now that I take a look at the 4.1 version of
{{FailingRepairTest}}, I see a similar change there:
https://github.com/apache/cassandra/blob/20125c5053586ab46fa341ac71cc525b64932873/test/distributed/org/apache/cassandra/distributed/test/FailingRepairTest.java#L169-L172
Maybe it's better to port that change back to 4.0 to keep things consistent?
> Test failure: org.apache.cassandra.distributed.test.FailingRepairTest -
> testFailingMessage[VALIDATION_REQ/parallel/true]
>
>
> Key: CASSANDRA-18366
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18366
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Assignee: dan jatnieks
>Priority: Normal
> Fix For: 4.0.x
>
>
> First seen
> [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206]
> this test times out for me consistently on both j8 and j11 where 4.1 and
> trunk do not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18366: - Status: Needs Committer (was: Review In Progress) > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761382#comment-17761382 ] Brandon Williams commented on CASSANDRA-18366: -- +1 from me > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18756) TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps overlaping SSTable references
[
https://issues.apache.org/jira/browse/CASSANDRA-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761380#comment-17761380
]
Michael Semb Wever commented on CASSANDRA-18756:
> Especially if we change it in patch releases for all supported versions.
Right. I would only do the change in a major, with a NEWS entry.
> TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps
> overlaping SSTable references
> --
>
> Key: CASSANDRA-18756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18756
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Branimir Lambov
>Assignee: Ethan Brown
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{unsafe_aggressive_sstable_expiration}} is turned on, TWCS should not
> create or maintain an iterator of overlapping sstables. However, because
> {{TimeWindowCompactionController}} inherits from {{CompactionController}} and
> only sets {{ignoreOverlaps}} after the base class has constructed the overlap
> iterator, it ends up making an overlap iterator and then never updating it.
> The end result is that such a compaction keeps references to lots of and
> likely _all_ other SSTables on the node and thus delays the deletion of
> obsolete ones by hours or even days.
--
This message was sent by Atlassian 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-18816) Add support for repair coordinator to retry messages that timeout
[ https://issues.apache.org/jira/browse/CASSANDRA-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-18816: -- Test and Documentation Plan: simulation testing Status: Patch Available (was: Open) > Add support for repair coordinator to retry messages that timeout > - > > Key: CASSANDRA-18816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18816 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Repair >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > Now that CASSANDRA-15399 is in, most of the repair messages have a state that > they can check against to make message delivery idempotent, allowing the > coordinator to retry such messages; a few of the most critical messages to > retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and > SYNC_RSP. > With this I propose making the coordinator able to retry these key messages > to try and make repair more resilient to ephemeral issues. -- This message was sent by Atlassian 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-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761376#comment-17761376 ] Brandon Williams commented on CASSANDRA-18366: -- ||Branch||CI|| |[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18366-4.0]|[j8-repeat|https://app.circleci.com/pipelines/github/driftx/cassandra/1258/workflows/c6824217-6d65-403a-aca7-6a12468a4cfb/jobs/50100], [j11-repeat|https://app.circleci.com/pipelines/github/driftx/cassandra/1258/workflows/d2cfc387-51fb-4725-b14a-daa682b29b8c/jobs/50099]| Do you know why this wasn't a problem on 4.1 or later? > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18756) TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps overlaping SSTable references
[
https://issues.apache.org/jira/browse/CASSANDRA-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761375#comment-17761375
]
Branimir Lambov commented on CASSANDRA-18756:
-
There's a risk that making it work as intended will unexpectedly change
behaviour for people that are already using the flag, and I would rather not do
that. Especially if we change it in patch releases for all supported versions.
If we are to enable that functionality, IMHO it should be under a different
flag (and then only for a subset of versions).
> TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps
> overlaping SSTable references
> --
>
> Key: CASSANDRA-18756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18756
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Branimir Lambov
>Assignee: Ethan Brown
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{unsafe_aggressive_sstable_expiration}} is turned on, TWCS should not
> create or maintain an iterator of overlapping sstables. However, because
> {{TimeWindowCompactionController}} inherits from {{CompactionController}} and
> only sets {{ignoreOverlaps}} after the base class has constructed the overlap
> iterator, it ends up making an overlap iterator and then never updating it.
> The end result is that such a compaction keeps references to lots of and
> likely _all_ other SSTables on the node and thus delays the deletion of
> obsolete ones by hours or even days.
--
This message was sent by Atlassian 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-18816) Add support for repair coordinator to retry messages that timeout
[ https://issues.apache.org/jira/browse/CASSANDRA-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-18816: -- Change Category: Operability Complexity: Normal Fix Version/s: 5.x Status: Open (was: Triage Needed) > Add support for repair coordinator to retry messages that timeout > - > > Key: CASSANDRA-18816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18816 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Repair >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > Now that CASSANDRA-15399 is in, most of the repair messages have a state that > they can check against to make message delivery idempotent, allowing the > coordinator to retry such messages; a few of the most critical messages to > retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and > SYNC_RSP. > With this I propose making the coordinator able to retry these key messages > to try and make repair more resilient to ephemeral issues. -- This message was sent by Atlassian 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-18816) Add support for repair coordinator to retry messages that timeout
David Capwell created CASSANDRA-18816: - Summary: Add support for repair coordinator to retry messages that timeout Key: CASSANDRA-18816 URL: https://issues.apache.org/jira/browse/CASSANDRA-18816 Project: Cassandra Issue Type: Improvement Components: Consistency/Repair Reporter: David Capwell Assignee: David Capwell Now that CASSANDRA-15399 is in, most of the repair messages have a state that they can check against to make message delivery idempotent, allowing the coordinator to retry such messages; a few of the most critical messages to retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and SYNC_RSP. With this I propose making the coordinator able to retry these key messages to try and make repair more resilient to ephemeral issues. -- This message was sent by Atlassian 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-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18366: - Reviewers: Brandon Williams, Brandon Williams Brandon Williams, Brandon Williams (was: Brandon Williams) Status: Review In Progress (was: Patch Available) > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18787) Replace obsolete Python functions
[
https://issues.apache.org/jira/browse/CASSANDRA-18787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761374#comment-17761374
]
Brad Schoening commented on CASSANDRA-18787:
Upon looking into this further, it would seem that the [copy
options|https://docs.datastax.com/en/cql-oss/3.x/cql/cql_reference/cqlshCopy.html#Settingcopyoptions]
for CVS in COPY FROM/TO are now provided as args to the copy command (instead
of cqlsh).
{code:java}
cqlsh> help copy from
Available common COPY options and defaults:
DELIMITER=',' - character that appears between records
QUOTE='"' - quoting character to be used to quote fields
ESCAPE='\' - character to appear before the QUOTE char
when quoted
HEADER=false - whether to ignore the first line
... etc
{code}
When copyutil was created with Cassandra 2.1, it seems they didn't include
field_size_limit as one of the options.
> Replace obsolete Python functions
> -
>
> Key: CASSANDRA-18787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18787
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Brad Schoening
>Priority: Low
> Fix For: 5.x
>
>
> # Python's stdlib datetime.timezone.utc can replace the custom UTC timezone
> in pylib/cqlshlib/util.py.
> # Removed unused attributes and functions:
> ## field_size _limit
> ## trim_if_present()
> ## maybe_ensure_text()
> # Simplify cql_version handling into a settor
> Functionality should remain the same while simplifying the code by
> eliminating ~60 lines.
--
This message was sent by Atlassian 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-18787) Replace obsolete Python functions
[
https://issues.apache.org/jira/browse/CASSANDRA-18787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761374#comment-17761374
]
Brad Schoening edited comment on CASSANDRA-18787 at 9/1/23 6:39 PM:
Upon looking into this further, it would seem that the [copy
options|https://docs.datastax.com/en/cql-oss/3.x/cql/cql_reference/cqlshCopy.html#Settingcopyoptions]
for CVS in COPY FROM/TO are now provided as args to the copy command (instead
of cqlsh args).
{code:java}
cqlsh> help copy from
Available common COPY options and defaults:
DELIMITER=',' - character that appears between records
QUOTE='"' - quoting character to be used to quote fields
ESCAPE='\' - character to appear before the QUOTE char
when quoted
HEADER=false - whether to ignore the first line
... etc
{code}
When copyutil was created with Cassandra 2.1, it seems they didn't include
field_size_limit as one of the options.
was (Author: bschoeni):
Upon looking into this further, it would seem that the [copy
options|https://docs.datastax.com/en/cql-oss/3.x/cql/cql_reference/cqlshCopy.html#Settingcopyoptions]
for CVS in COPY FROM/TO are now provided as args to the copy command (instead
of cqlsh).
{code:java}
cqlsh> help copy from
Available common COPY options and defaults:
DELIMITER=',' - character that appears between records
QUOTE='"' - quoting character to be used to quote fields
ESCAPE='\' - character to appear before the QUOTE char
when quoted
HEADER=false - whether to ignore the first line
... etc
{code}
When copyutil was created with Cassandra 2.1, it seems they didn't include
field_size_limit as one of the options.
> Replace obsolete Python functions
> -
>
> Key: CASSANDRA-18787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18787
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Brad Schoening
>Priority: Low
> Fix For: 5.x
>
>
> # Python's stdlib datetime.timezone.utc can replace the custom UTC timezone
> in pylib/cqlshlib/util.py.
> # Removed unused attributes and functions:
> ## field_size _limit
> ## trim_if_present()
> ## maybe_ensure_text()
> # Simplify cql_version handling into a settor
> Functionality should remain the same while simplifying the code by
> eliminating ~60 lines.
--
This message was sent by Atlassian 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-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dan jatnieks updated CASSANDRA-18366: - Test and Documentation Plan: Started CircleCI pre-commit tests here (w/limited resources): https://app.circleci.com/pipelines/github/djatnieks/cassandra?branch=CASSANDRA-18366 Status: Patch Available (was: Open) > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dan jatnieks reassigned CASSANDRA-18366: Assignee: dan jatnieks > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[
https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761371#comment-17761371
]
dan jatnieks commented on CASSANDRA-18366:
--
I ran into this issue and found that when {{DefaultFSErrorHandler}} handles
{{die}} it stops transports, including gossip. When the next test starts,
gossip isn't running and the test hangs. The solution I found is to make sure
gossip is started before starting each test.
Here is a [4.0 PR |https://github.com/apache/cassandra/pull/2659]
> Test failure: org.apache.cassandra.distributed.test.FailingRepairTest -
> testFailingMessage[VALIDATION_REQ/parallel/true]
>
>
> Key: CASSANDRA-18366
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18366
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.0.x
>
>
> First seen
> [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206]
> this test times out for me consistently on both j8 and j11 where 4.1 and
> trunk do not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18756) TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps overlaping SSTable references
[
https://issues.apache.org/jira/browse/CASSANDRA-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761365#comment-17761365
]
Michael Semb Wever commented on CASSANDRA-18756:
Given this feature can only be enabled with both the table option and a system
variable, and it's overly clear the risks (and carefully documented), I would
have no objection to making it work correctly. It can have a dramatic saving
on nodes for its intended use-cases. I leave that call up to you both.
Otherwise, +1 on the patch as it is.
> TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps
> overlaping SSTable references
> --
>
> Key: CASSANDRA-18756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18756
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Branimir Lambov
>Assignee: Ethan Brown
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{unsafe_aggressive_sstable_expiration}} is turned on, TWCS should not
> create or maintain an iterator of overlapping sstables. However, because
> {{TimeWindowCompactionController}} inherits from {{CompactionController}} and
> only sets {{ignoreOverlaps}} after the base class has constructed the overlap
> iterator, it ends up making an overlap iterator and then never updating it.
> The end result is that such a compaction keeps references to lots of and
> likely _all_ other SSTables on the node and thus delays the deletion of
> obsolete ones by hours or even days.
--
This message was sent by Atlassian 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 (c49b8a71b -> 83af0a939)
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 c49b8a71b generate docs for d7f28f31 new 83af0a939 generate docs for d7f28f31 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 (c49b8a71b) \ N -- N -- N refs/heads/asf-staging (83af0a939) 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/statusbinary.html | 3 ++- .../managing/tools/nodetool/statusbinary.html | 3 ++- content/search-index.js| 2 +- site-ui/build/ui-bundle.zip| Bin 4881369 -> 4881369 bytes 4 files changed, 5 insertions(+), 3 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18756) TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps overlaping SSTable references
[
https://issues.apache.org/jira/browse/CASSANDRA-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Brown reassigned CASSANDRA-18756:
---
Assignee: Ethan Brown
> TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps
> overlaping SSTable references
> --
>
> Key: CASSANDRA-18756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18756
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Branimir Lambov
>Assignee: Ethan Brown
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{unsafe_aggressive_sstable_expiration}} is turned on, TWCS should not
> create or maintain an iterator of overlapping sstables. However, because
> {{TimeWindowCompactionController}} inherits from {{CompactionController}} and
> only sets {{ignoreOverlaps}} after the base class has constructed the overlap
> iterator, it ends up making an overlap iterator and then never updating it.
> The end result is that such a compaction keeps references to lots of and
> likely _all_ other SSTables on the node and thus delays the deletion of
> obsolete ones by hours or even days.
--
This message was sent by Atlassian 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-18734) SAI result retriever is filtering too many rows
[ https://issues.apache.org/jira/browse/CASSANDRA-18734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761334#comment-17761334 ] Caleb Rackliffe commented on CASSANDRA-18734: - +1 (w/ one small outstanding comment [here|https://github.com/apache/cassandra/pull/2645#discussion_r1313190721]) > SAI result retriever is filtering too many rows > --- > > Key: CASSANDRA-18734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18734 > Project: Cassandra > Issue Type: Bug > Components: Feature/SAI >Reporter: Mike Adamson >Assignee: Mike Adamson >Priority: Normal > Attachments: flamegraph.svg, image-2023-08-08-13-48-19-701.png, > image-2023-08-08-13-49-19-576.png > > > Performance tests on SAI have shown that the number of rows being filtered > for wide row partitions is more than expected. For a 10k row/partition test - > limit 10, the following has been observed. > !image-2023-08-08-13-49-19-576.png|width=952,height=368! > This is not the expected outcome of row-awareness and needs investigating. > The number of rows read should, roughly, match the number of partitions 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
[jira] [Updated] (CASSANDRA-18756) TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps overlaping SSTable references
[
https://issues.apache.org/jira/browse/CASSANDRA-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18756:
---
Reviewers: Michael Semb Wever
> TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps
> overlaping SSTable references
> --
>
> Key: CASSANDRA-18756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18756
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Branimir Lambov
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{unsafe_aggressive_sstable_expiration}} is turned on, TWCS should not
> create or maintain an iterator of overlapping sstables. However, because
> {{TimeWindowCompactionController}} inherits from {{CompactionController}} and
> only sets {{ignoreOverlaps}} after the base class has constructed the overlap
> iterator, it ends up making an overlap iterator and then never updating it.
> The end result is that such a compaction keeps references to lots of and
> likely _all_ other SSTables on the node and thus delays the deletion of
> obsolete ones by hours or even days.
--
This message was sent by Atlassian 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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Reviewers: Andres de la Peña, Andres de la Peña (was: Andres de la Peña)
Andres de la Peña, Andres de la Peña (was: Andres de la Peña)
Status: Review In Progress (was: Patch Available)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17476:
--
Reviewers: Andres de la Peña
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-website] branch asf-staging updated (ca5c2bd2f -> c49b8a71b)
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 ca5c2bd2f generate docs for d7f28f31 new c49b8a71b generate docs for d7f28f31 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 (ca5c2bd2f) \ N -- N -- N refs/heads/asf-staging (c49b8a71b) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4881369 -> 4881369 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18756) TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps overlaping SSTable references
[
https://issues.apache.org/jira/browse/CASSANDRA-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Branimir Lambov updated CASSANDRA-18756:
Status: Open (was: Triage Needed)
> TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps
> overlaping SSTable references
> --
>
> Key: CASSANDRA-18756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18756
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Branimir Lambov
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{unsafe_aggressive_sstable_expiration}} is turned on, TWCS should not
> create or maintain an iterator of overlapping sstables. However, because
> {{TimeWindowCompactionController}} inherits from {{CompactionController}} and
> only sets {{ignoreOverlaps}} after the base class has constructed the overlap
> iterator, it ends up making an overlap iterator and then never updating it.
> The end result is that such a compaction keeps references to lots of and
> likely _all_ other SSTables on the node and thus delays the deletion of
> obsolete ones by hours or even days.
--
This message was sent by Atlassian 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-18756) TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps overlaping SSTable references
[
https://issues.apache.org/jira/browse/CASSANDRA-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761314#comment-17761314
]
Branimir Lambov commented on CASSANDRA-18756:
-
[~mck], could you do the second review this small patch which corrects a
problem with CASSANDRA-13418? Your name came up as a reviewer for that ticket
and it would be great to get the opinion of someone who has some context on it.
> TimeWindowCompactionStrategy with unsafe_aggressive_sstable_expiration keeps
> overlaping SSTable references
> --
>
> Key: CASSANDRA-18756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18756
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Branimir Lambov
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{unsafe_aggressive_sstable_expiration}} is turned on, TWCS should not
> create or maintain an iterator of overlapping sstables. However, because
> {{TimeWindowCompactionController}} inherits from {{CompactionController}} and
> only sets {{ignoreOverlaps}} after the base class has constructed the overlap
> iterator, it ends up making an overlap iterator and then never updating it.
> The end result is that such a compaction keeps references to lots of and
> likely _all_ other SSTables on the node and thus delays the deletion of
> obsolete ones by hours or even days.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18534) Make sstable format configurable per table
[
https://issues.apache.org/jira/browse/CASSANDRA-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761307#comment-17761307
]
Branimir Lambov commented on CASSANDRA-18534:
-
We can't remove the existing option, only deprecate it (i.e. give a warning
that it may be removed in a later version). We also have to honor the value if
it is present.
I agree that we should throw an exception if both versions are given in the
DDL. The complication is what happens if the format-side option is given in the
yaml: in this case I think we should let the table-side option override it even
if it is given in the legacy way (with perhaps a deprecation warning).
> Make sstable format configurable per table
> --
>
> Key: CASSANDRA-18534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18534
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.x
>
>
> Some SSTable format settings need to be configurable per table for better
> efficiency. This includes:
> - {{row_index_granularity}}
> - {{bloom_filter_fp_chance}}
> - {{crc_check_chance}}
> - {{min/max_index_interval}}
> Some of these are currently configurable using direct properties of tables.
> Having them as format properties makes better sense and should also support
> specifying useable combinations of settings, e.g.
> {code:java}
> CREATE TABLE ... WITH sstable_format = "bti-fast";
> CREATE TABLE ... WITH sstable_format = "bti-small";
> {code}
> where {{bti-fast}} and {{bti-small}} can be defined in {{cassandra.yaml}}
> e.g. as
> {code:java}
> sstable.format.options:
> - bti-fast:
> row_index_granularity: 1kiB
> bloom_filter_fp_chance: 0.01
> - bti-small:
> row_index_granularity: 32kiB
> bloom_filter_fp_chance: 0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18393) Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1: clusterMinVersion=3.11]-compression.jdk1.8 on trun
[
https://issues.apache.org/jira/browse/CASSANDRA-18393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761293#comment-17761293
]
Berenguer Blasi commented on CASSANDRA-18393:
-
Thx for the review! I'll commit on Monday to avoid Murphy's bad commit on a
Friday law... :-DD
> Flaky test:
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1:
> clusterMinVersion=3.11]-compression.jdk1.8 on trunk
>
>
> Key: CASSANDRA-18393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18393
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1.x, 5.0, 5.0.x
>
>
> Failed 1 times in the last 1 runs. Flakiness: 0%, Stability: 0%
> {code}
> Error Message
> 5.0.0-SNAPSHOT boolean:false
> Stacktrace
> junit.framework.AssertionFailedError: 5.0.0-SNAPSHOT boolean:false
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$1(InsertUpdateIfConditionTest.java:70)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:95)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:89)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18393) Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1: clusterMinVersion=3.11]-compression.jdk1.8 on trun
[
https://issues.apache.org/jira/browse/CASSANDRA-18393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761281#comment-17761281
]
Andres de la Peña commented on CASSANDRA-18393:
---
Great, thanks. +1.
> Flaky test:
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1:
> clusterMinVersion=3.11]-compression.jdk1.8 on trunk
>
>
> Key: CASSANDRA-18393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18393
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1.x, 5.0, 5.0.x
>
>
> Failed 1 times in the last 1 runs. Flakiness: 0%, Stability: 0%
> {code}
> Error Message
> 5.0.0-SNAPSHOT boolean:false
> Stacktrace
> junit.framework.AssertionFailedError: 5.0.0-SNAPSHOT boolean:false
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$1(InsertUpdateIfConditionTest.java:70)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:95)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:89)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18393) Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1: clusterMinVersion=3.11]-compression.jdk1.8 on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18393:
--
Status: Ready to Commit (was: Review In Progress)
> Flaky test:
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1:
> clusterMinVersion=3.11]-compression.jdk1.8 on trunk
>
>
> Key: CASSANDRA-18393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18393
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1.x, 5.0, 5.0.x
>
>
> Failed 1 times in the last 1 runs. Flakiness: 0%, Stability: 0%
> {code}
> Error Message
> 5.0.0-SNAPSHOT boolean:false
> Stacktrace
> junit.framework.AssertionFailedError: 5.0.0-SNAPSHOT boolean:false
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$1(InsertUpdateIfConditionTest.java:70)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:95)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:89)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18564) Test Failure: MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
[
https://issues.apache.org/jira/browse/CASSANDRA-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18564:
--
Test and Documentation Plan:
||PR||CI||
|[5.0
|https://github.com/apache/cassandra/pull/2657]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3194/workflows/d7abb1fe-0954-4b11-8f15-0e9696d43f8d]|
|[trunk|https://github.com/apache/cassandra/pull/2658]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3195/workflows/1c6be32a-ac4d-44f8-91a4-238997418c28]|
Status: Patch Available (was: In Progress)
> Test Failure:
> MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
>
>
> Key: CASSANDRA-18564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18564
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The JVM upgrade dtest
> {{MixedModeAvailabilityV3XAllOneTest.testAvailabilityCoordinatorUpgraded}}
> seems to be flaky at least in {{trunk}}:
> {code}
> junit.framework.AssertionFailedError: Error in test '4.0.11 -> [5.0]' while
> upgrading to '5.0'; successful upgrades []
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:348)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:154)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailabilityCoordinatorUpgraded(MixedModeAvailabilityTestBase.java:74)
> Caused by: java.lang.AssertionError: Unexpected error while reading in case
> write-read consistency ALL-ONE with upgraded coordinator and 2 nodes down:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 0 responses.
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$6(MixedModeAvailabilityTestBase.java:145)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:339)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 0 responses.
> at
> org.apache.cassandra.service.reads.ReadCallback.awaitResults(ReadCallback.java:162)
> at
> org.apache.cassandra.service.reads.AbstractReadExecutor.awaitResponses(AbstractReadExecutor.java:387)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:2124)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1995)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1873)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1286)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:364)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:293)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:105)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:750)
> {code}
> This has failed 143 times in 500 iterations of this CircleCI run:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2927/workflows/fcd1cd60-826b-484a-8e81-d3ba640f7de9/jobs/47659/tests
> The failure has also recently appeared on Jenkins too:
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1585/testReport/org.apache.cassandra.distributed.upgrade/MixedModeAvailabilityV3XAllOneTest/testAvailabilityCoordinatorUpgraded__jdk11/
> Given that the failure has just appeared on Jenkins and it fails relatively
> easily on CircleCI, it's likely that it has been broken by a very recent
> change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
--
[jira] [Commented] (CASSANDRA-18564) Test Failure: MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
[
https://issues.apache.org/jira/browse/CASSANDRA-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761279#comment-17761279
]
Andres de la Peña commented on CASSANDRA-18564:
---
This patch makes the test survive 500 runs:
||PR||CI||
|[5.0
|https://github.com/apache/cassandra/pull/2657]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3194/workflows/d7abb1fe-0954-4b11-8f15-0e9696d43f8d]|
|[trunk|https://github.com/apache/cassandra/pull/2658]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3195/workflows/1c6be32a-ac4d-44f8-91a4-238997418c28]|
I have changed the test to skip testing the cases where the query should
timeout, as mentioned above. This allows us to increase the timeouts without
making the test prohibitively slow, which might cause a JUnit or CircleCI
timeout.
I have also grouped the testing of different consistency level combinations, so
they can all be tested into the same cluster run. This means that we only need
to run a third of the clusters. That doesn't make the test less prone to fail,
but it reduces the total CI load.
I have also split the test class by whether the coordinator node is upgraded or
not, so we don't have to run two full sets of upgrade paths in the same JVM.
However, I'm not sure I understand why the test was more prone to fail in 5.0
and trunk than in 4.0 and 4.1. 5.0 and trunk don't support direct upgrades from
3.0 or 3.x. So I think the number of tested upgrade paths is the same. There
should be something in 5.0 and trunk that makes the db, the test or the CI
environment slower. Could it be due to the fact that we are running with J11
instead of J8?
> Test Failure:
> MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
>
>
> Key: CASSANDRA-18564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18564
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The JVM upgrade dtest
> {{MixedModeAvailabilityV3XAllOneTest.testAvailabilityCoordinatorUpgraded}}
> seems to be flaky at least in {{trunk}}:
> {code}
> junit.framework.AssertionFailedError: Error in test '4.0.11 -> [5.0]' while
> upgrading to '5.0'; successful upgrades []
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:348)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:154)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailabilityCoordinatorUpgraded(MixedModeAvailabilityTestBase.java:74)
> Caused by: java.lang.AssertionError: Unexpected error while reading in case
> write-read consistency ALL-ONE with upgraded coordinator and 2 nodes down:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 0 responses.
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$6(MixedModeAvailabilityTestBase.java:145)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:339)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 0 responses.
> at
> org.apache.cassandra.service.reads.ReadCallback.awaitResults(ReadCallback.java:162)
> at
> org.apache.cassandra.service.reads.AbstractReadExecutor.awaitResponses(AbstractReadExecutor.java:387)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:2124)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1995)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1873)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1286)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:364)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:293)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:105)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.Fu
[cassandra-website] branch asf-staging updated (f8e8ede93 -> ca5c2bd2f)
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 f8e8ede93 generate docs for d7f28f31 new ca5c2bd2f generate docs for d7f28f31 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 (f8e8ede93) \ N -- N -- N refs/heads/asf-staging (ca5c2bd2f) 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 4881369 -> 4881369 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-18791) CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and simulation testing
[ https://issues.apache.org/jira/browse/CASSANDRA-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-18791: Fix Version/s: 5.x Source Control Link: https://github.com/apache/cassandra/commit/5cacbbcc758348f2de10898576ee290da2977f80 Resolution: Fixed Status: Resolved (was: Ready to Commit) thanks, pushed to [cep-21-tcm|https://github.com/apache/cassandra/tree/cep-21-tcm] branch > CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and > simulation testing > - > > Key: CASSANDRA-18791 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18791 > Project: Cassandra > Issue Type: Improvement > Components: Cluster/Membership >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.x > > > Full branch: [https://github.com/krummas/cassandra/commits/marcuse/cep-21-tcm] > Tests: > [cci|https://app.circleci.com/pipelines/github/krummas/cassandra/885/workflows/7cc3e1a1-45b9-4069-bb02-2a46855b4dbe] > - current status is: > unit tests: 35/12052 failures > jvm dtests: 23/1459 failures > python dtests: 110/1018 failures > We will spend the next few weeks getting all the test targets down to 0 > Summary of changes; > [CEP-21] Python dtest fixes * maybe fix hintedhandoff test > - [https://github.com/krummas/cassandra/commit/3da91c26fb] > - [https://github.com/krummas/cassandra/commit/98e444adbb] > [CEP-21] In-JVM DTest fixes > - [https://github.com/krummas/cassandra/compare/6491a70041...c9126a8024] > [CEP-21] Unit test fixes > - [https://github.com/krummas/cassandra/compare/02be7aa71c...6491a70041] > [CEP-21] Escape infinite local log loop on replica mis-configuration > - [https://github.com/krummas/cassandra/commit/02be7aa71c] > Currently different replicas can have different configurations (guardrails > for example) If a transformation is not applied on a replica, this node got > stuck in an infinite loop. For now escape that loop until we have a better > solution. > [CEP-21] Fix batchlog consistency errors during epoch bumps > - [https://github.com/krummas/cassandra/commit/c853bf864e] > [CEP-21] Avoid using batches in distributed metadata log keyspace > - [https://github.com/krummas/cassandra/commit/d4b4766e0b] > [CEP-21] Fix table metadata serialization > - [https://github.com/krummas/cassandra/commit/4056bab669] > [CEP-21] add more metrics > - [https://github.com/krummas/cassandra/commit/b6ccb559f5] > [CEP-21] getHostIdForEndpoint return null if unknown endpoint > - [https://github.com/krummas/cassandra/commit/b9243df05b] > [CEP-21] CMS handling > - [https://github.com/krummas/cassandra/commit/15eea30d43] > - [https://github.com/krummas/cassandra/commit/d64da5f5e4] > - [https://github.com/krummas/cassandra/commit/61deb52811] > [CEP-21] Upgrade fixes > - [https://github.com/krummas/cassandra/commit/33d186b4ce] > Properly set system.local host id on upgrade. > - [https://github.com/krummas/cassandra/commit/b96bdc83e1] > If replica misses migration message, set migration as successfull when it > sees the first epoch bump. > - [https://github.com/krummas/cassandra/commit/712828bc82] > Handle hints on upgrade - we change the hostid when enabling CMS, hints > should be delivered before that. > [CEP-21] Catchup/log fetching improvements > - [https://github.com/krummas/cassandra/commit/31a183e236] > When an instance sees a message from a peer with a newer epoch, try to catch > up from that peer instead of the CMS to reduce load on the CMS nodes and to > allow for cluster to quiesce in the case of the CMS being down. > - [https://github.com/krummas/cassandra/commit/8c6a4b35db] > We can get a snapshot when catching up, in this case the pending log should > first apply the snapshot and skip any previous entries. > - [https://github.com/krummas/cassandra/commit/387853487f] > When deserializing partition update, allow if current epoch >= serialized > epoch > - [https://github.com/krummas/cassandra/commit/626d224716] > When we replay from a snapshot we might see a node as LEFT for the first time > (it was bootstrapped and left while we were down) > [CEP-21] Require Paxos V2 for cluster metadata log operations > - [https://github.com/krummas/cassandra/commit/2217f551a6] > TCM is required to use Paxos V2 to because of the way the legacy paxos path > uses a keyspace’s RF to assert whether there are enough available replicas to > perform the read before a CAS. It doesn’t work properly with meta strategy > when adding CMS members > [CEP-21] Disaster recovery > - [https://github.com/krummas/cassandra/commit/9011233604] > Allow an instance to dump its current cluster metadata, and force-boot from > i
[jira] [Comment Edited] (CASSANDRA-18791) CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and simulation testing
[ https://issues.apache.org/jira/browse/CASSANDRA-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761259#comment-17761259 ] Sam Tunnicliffe edited comment on CASSANDRA-18791 at 9/1/23 10:22 AM: -- +1 The majority of outstanding test failures are either fixed in upcoming patches, or known failures that we have on our radar already. was (Author: beobal): +1 > CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and > simulation testing > - > > Key: CASSANDRA-18791 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18791 > Project: Cassandra > Issue Type: Improvement > Components: Cluster/Membership >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > Full branch: [https://github.com/krummas/cassandra/commits/marcuse/cep-21-tcm] > Tests: > [cci|https://app.circleci.com/pipelines/github/krummas/cassandra/885/workflows/7cc3e1a1-45b9-4069-bb02-2a46855b4dbe] > - current status is: > unit tests: 35/12052 failures > jvm dtests: 23/1459 failures > python dtests: 110/1018 failures > We will spend the next few weeks getting all the test targets down to 0 > Summary of changes; > [CEP-21] Python dtest fixes * maybe fix hintedhandoff test > - [https://github.com/krummas/cassandra/commit/3da91c26fb] > - [https://github.com/krummas/cassandra/commit/98e444adbb] > [CEP-21] In-JVM DTest fixes > - [https://github.com/krummas/cassandra/compare/6491a70041...c9126a8024] > [CEP-21] Unit test fixes > - [https://github.com/krummas/cassandra/compare/02be7aa71c...6491a70041] > [CEP-21] Escape infinite local log loop on replica mis-configuration > - [https://github.com/krummas/cassandra/commit/02be7aa71c] > Currently different replicas can have different configurations (guardrails > for example) If a transformation is not applied on a replica, this node got > stuck in an infinite loop. For now escape that loop until we have a better > solution. > [CEP-21] Fix batchlog consistency errors during epoch bumps > - [https://github.com/krummas/cassandra/commit/c853bf864e] > [CEP-21] Avoid using batches in distributed metadata log keyspace > - [https://github.com/krummas/cassandra/commit/d4b4766e0b] > [CEP-21] Fix table metadata serialization > - [https://github.com/krummas/cassandra/commit/4056bab669] > [CEP-21] add more metrics > - [https://github.com/krummas/cassandra/commit/b6ccb559f5] > [CEP-21] getHostIdForEndpoint return null if unknown endpoint > - [https://github.com/krummas/cassandra/commit/b9243df05b] > [CEP-21] CMS handling > - [https://github.com/krummas/cassandra/commit/15eea30d43] > - [https://github.com/krummas/cassandra/commit/d64da5f5e4] > - [https://github.com/krummas/cassandra/commit/61deb52811] > [CEP-21] Upgrade fixes > - [https://github.com/krummas/cassandra/commit/33d186b4ce] > Properly set system.local host id on upgrade. > - [https://github.com/krummas/cassandra/commit/b96bdc83e1] > If replica misses migration message, set migration as successfull when it > sees the first epoch bump. > - [https://github.com/krummas/cassandra/commit/712828bc82] > Handle hints on upgrade - we change the hostid when enabling CMS, hints > should be delivered before that. > [CEP-21] Catchup/log fetching improvements > - [https://github.com/krummas/cassandra/commit/31a183e236] > When an instance sees a message from a peer with a newer epoch, try to catch > up from that peer instead of the CMS to reduce load on the CMS nodes and to > allow for cluster to quiesce in the case of the CMS being down. > - [https://github.com/krummas/cassandra/commit/8c6a4b35db] > We can get a snapshot when catching up, in this case the pending log should > first apply the snapshot and skip any previous entries. > - [https://github.com/krummas/cassandra/commit/387853487f] > When deserializing partition update, allow if current epoch >= serialized > epoch > - [https://github.com/krummas/cassandra/commit/626d224716] > When we replay from a snapshot we might see a node as LEFT for the first time > (it was bootstrapped and left while we were down) > [CEP-21] Require Paxos V2 for cluster metadata log operations > - [https://github.com/krummas/cassandra/commit/2217f551a6] > TCM is required to use Paxos V2 to because of the way the legacy paxos path > uses a keyspace’s RF to assert whether there are enough available replicas to > perform the read before a CAS. It doesn’t work properly with meta strategy > when adding CMS members > [CEP-21] Disaster recovery > - [https://github.com/krummas/cassandra/commit/9011233604] > Allow an instance to dump its current cluster metadata, and force-boot from > it. Basically we need a way to force an instance to become the CMS, in case >
[jira] [Updated] (CASSANDRA-18791) CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and simulation testing
[ https://issues.apache.org/jira/browse/CASSANDRA-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-18791: Status: Review In Progress (was: Patch Available) > CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and > simulation testing > - > > Key: CASSANDRA-18791 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18791 > Project: Cassandra > Issue Type: Improvement > Components: Cluster/Membership >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > Full branch: [https://github.com/krummas/cassandra/commits/marcuse/cep-21-tcm] > Tests: > [cci|https://app.circleci.com/pipelines/github/krummas/cassandra/885/workflows/7cc3e1a1-45b9-4069-bb02-2a46855b4dbe] > - current status is: > unit tests: 35/12052 failures > jvm dtests: 23/1459 failures > python dtests: 110/1018 failures > We will spend the next few weeks getting all the test targets down to 0 > Summary of changes; > [CEP-21] Python dtest fixes * maybe fix hintedhandoff test > - [https://github.com/krummas/cassandra/commit/3da91c26fb] > - [https://github.com/krummas/cassandra/commit/98e444adbb] > [CEP-21] In-JVM DTest fixes > - [https://github.com/krummas/cassandra/compare/6491a70041...c9126a8024] > [CEP-21] Unit test fixes > - [https://github.com/krummas/cassandra/compare/02be7aa71c...6491a70041] > [CEP-21] Escape infinite local log loop on replica mis-configuration > - [https://github.com/krummas/cassandra/commit/02be7aa71c] > Currently different replicas can have different configurations (guardrails > for example) If a transformation is not applied on a replica, this node got > stuck in an infinite loop. For now escape that loop until we have a better > solution. > [CEP-21] Fix batchlog consistency errors during epoch bumps > - [https://github.com/krummas/cassandra/commit/c853bf864e] > [CEP-21] Avoid using batches in distributed metadata log keyspace > - [https://github.com/krummas/cassandra/commit/d4b4766e0b] > [CEP-21] Fix table metadata serialization > - [https://github.com/krummas/cassandra/commit/4056bab669] > [CEP-21] add more metrics > - [https://github.com/krummas/cassandra/commit/b6ccb559f5] > [CEP-21] getHostIdForEndpoint return null if unknown endpoint > - [https://github.com/krummas/cassandra/commit/b9243df05b] > [CEP-21] CMS handling > - [https://github.com/krummas/cassandra/commit/15eea30d43] > - [https://github.com/krummas/cassandra/commit/d64da5f5e4] > - [https://github.com/krummas/cassandra/commit/61deb52811] > [CEP-21] Upgrade fixes > - [https://github.com/krummas/cassandra/commit/33d186b4ce] > Properly set system.local host id on upgrade. > - [https://github.com/krummas/cassandra/commit/b96bdc83e1] > If replica misses migration message, set migration as successfull when it > sees the first epoch bump. > - [https://github.com/krummas/cassandra/commit/712828bc82] > Handle hints on upgrade - we change the hostid when enabling CMS, hints > should be delivered before that. > [CEP-21] Catchup/log fetching improvements > - [https://github.com/krummas/cassandra/commit/31a183e236] > When an instance sees a message from a peer with a newer epoch, try to catch > up from that peer instead of the CMS to reduce load on the CMS nodes and to > allow for cluster to quiesce in the case of the CMS being down. > - [https://github.com/krummas/cassandra/commit/8c6a4b35db] > We can get a snapshot when catching up, in this case the pending log should > first apply the snapshot and skip any previous entries. > - [https://github.com/krummas/cassandra/commit/387853487f] > When deserializing partition update, allow if current epoch >= serialized > epoch > - [https://github.com/krummas/cassandra/commit/626d224716] > When we replay from a snapshot we might see a node as LEFT for the first time > (it was bootstrapped and left while we were down) > [CEP-21] Require Paxos V2 for cluster metadata log operations > - [https://github.com/krummas/cassandra/commit/2217f551a6] > TCM is required to use Paxos V2 to because of the way the legacy paxos path > uses a keyspace’s RF to assert whether there are enough available replicas to > perform the read before a CAS. It doesn’t work properly with meta strategy > when adding CMS members > [CEP-21] Disaster recovery > - [https://github.com/krummas/cassandra/commit/9011233604] > Allow an instance to dump its current cluster metadata, and force-boot from > it. Basically we need a way to force an instance to become the CMS, in case > the original CMS goes down. > [CEP-21] Switch nodeId from uuid to int > - [https://github.com/krummas/cassandra/commit/aea5500ae0] > [CEP-21] Make CQLSSTableWriter exclusively a client utility > - [https://github.c
[jira] [Updated] (CASSANDRA-18791) CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and simulation testing
[ https://issues.apache.org/jira/browse/CASSANDRA-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-18791: Status: Ready to Commit (was: Review In Progress) +1 > CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and > simulation testing > - > > Key: CASSANDRA-18791 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18791 > Project: Cassandra > Issue Type: Improvement > Components: Cluster/Membership >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > Full branch: [https://github.com/krummas/cassandra/commits/marcuse/cep-21-tcm] > Tests: > [cci|https://app.circleci.com/pipelines/github/krummas/cassandra/885/workflows/7cc3e1a1-45b9-4069-bb02-2a46855b4dbe] > - current status is: > unit tests: 35/12052 failures > jvm dtests: 23/1459 failures > python dtests: 110/1018 failures > We will spend the next few weeks getting all the test targets down to 0 > Summary of changes; > [CEP-21] Python dtest fixes * maybe fix hintedhandoff test > - [https://github.com/krummas/cassandra/commit/3da91c26fb] > - [https://github.com/krummas/cassandra/commit/98e444adbb] > [CEP-21] In-JVM DTest fixes > - [https://github.com/krummas/cassandra/compare/6491a70041...c9126a8024] > [CEP-21] Unit test fixes > - [https://github.com/krummas/cassandra/compare/02be7aa71c...6491a70041] > [CEP-21] Escape infinite local log loop on replica mis-configuration > - [https://github.com/krummas/cassandra/commit/02be7aa71c] > Currently different replicas can have different configurations (guardrails > for example) If a transformation is not applied on a replica, this node got > stuck in an infinite loop. For now escape that loop until we have a better > solution. > [CEP-21] Fix batchlog consistency errors during epoch bumps > - [https://github.com/krummas/cassandra/commit/c853bf864e] > [CEP-21] Avoid using batches in distributed metadata log keyspace > - [https://github.com/krummas/cassandra/commit/d4b4766e0b] > [CEP-21] Fix table metadata serialization > - [https://github.com/krummas/cassandra/commit/4056bab669] > [CEP-21] add more metrics > - [https://github.com/krummas/cassandra/commit/b6ccb559f5] > [CEP-21] getHostIdForEndpoint return null if unknown endpoint > - [https://github.com/krummas/cassandra/commit/b9243df05b] > [CEP-21] CMS handling > - [https://github.com/krummas/cassandra/commit/15eea30d43] > - [https://github.com/krummas/cassandra/commit/d64da5f5e4] > - [https://github.com/krummas/cassandra/commit/61deb52811] > [CEP-21] Upgrade fixes > - [https://github.com/krummas/cassandra/commit/33d186b4ce] > Properly set system.local host id on upgrade. > - [https://github.com/krummas/cassandra/commit/b96bdc83e1] > If replica misses migration message, set migration as successfull when it > sees the first epoch bump. > - [https://github.com/krummas/cassandra/commit/712828bc82] > Handle hints on upgrade - we change the hostid when enabling CMS, hints > should be delivered before that. > [CEP-21] Catchup/log fetching improvements > - [https://github.com/krummas/cassandra/commit/31a183e236] > When an instance sees a message from a peer with a newer epoch, try to catch > up from that peer instead of the CMS to reduce load on the CMS nodes and to > allow for cluster to quiesce in the case of the CMS being down. > - [https://github.com/krummas/cassandra/commit/8c6a4b35db] > We can get a snapshot when catching up, in this case the pending log should > first apply the snapshot and skip any previous entries. > - [https://github.com/krummas/cassandra/commit/387853487f] > When deserializing partition update, allow if current epoch >= serialized > epoch > - [https://github.com/krummas/cassandra/commit/626d224716] > When we replay from a snapshot we might see a node as LEFT for the first time > (it was bootstrapped and left while we were down) > [CEP-21] Require Paxos V2 for cluster metadata log operations > - [https://github.com/krummas/cassandra/commit/2217f551a6] > TCM is required to use Paxos V2 to because of the way the legacy paxos path > uses a keyspace’s RF to assert whether there are enough available replicas to > perform the read before a CAS. It doesn’t work properly with meta strategy > when adding CMS members > [CEP-21] Disaster recovery > - [https://github.com/krummas/cassandra/commit/9011233604] > Allow an instance to dump its current cluster metadata, and force-boot from > it. Basically we need a way to force an instance to become the CMS, in case > the original CMS goes down. > [CEP-21] Switch nodeId from uuid to int > - [https://github.com/krummas/cassandra/commit/aea5500ae0] > [CEP-21] Make CQLSSTableWriter exclusively a client utility > - [https://gith
[jira] [Updated] (CASSANDRA-18791) CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and simulation testing
[ https://issues.apache.org/jira/browse/CASSANDRA-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-18791: Test and Documentation Plan: Run CI Pipelines Status: Patch Available (was: Open) > CEP-21 - Multiple TCM fixes for issues discovered by unit, integration and > simulation testing > - > > Key: CASSANDRA-18791 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18791 > Project: Cassandra > Issue Type: Improvement > Components: Cluster/Membership >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > Full branch: [https://github.com/krummas/cassandra/commits/marcuse/cep-21-tcm] > Tests: > [cci|https://app.circleci.com/pipelines/github/krummas/cassandra/885/workflows/7cc3e1a1-45b9-4069-bb02-2a46855b4dbe] > - current status is: > unit tests: 35/12052 failures > jvm dtests: 23/1459 failures > python dtests: 110/1018 failures > We will spend the next few weeks getting all the test targets down to 0 > Summary of changes; > [CEP-21] Python dtest fixes * maybe fix hintedhandoff test > - [https://github.com/krummas/cassandra/commit/3da91c26fb] > - [https://github.com/krummas/cassandra/commit/98e444adbb] > [CEP-21] In-JVM DTest fixes > - [https://github.com/krummas/cassandra/compare/6491a70041...c9126a8024] > [CEP-21] Unit test fixes > - [https://github.com/krummas/cassandra/compare/02be7aa71c...6491a70041] > [CEP-21] Escape infinite local log loop on replica mis-configuration > - [https://github.com/krummas/cassandra/commit/02be7aa71c] > Currently different replicas can have different configurations (guardrails > for example) If a transformation is not applied on a replica, this node got > stuck in an infinite loop. For now escape that loop until we have a better > solution. > [CEP-21] Fix batchlog consistency errors during epoch bumps > - [https://github.com/krummas/cassandra/commit/c853bf864e] > [CEP-21] Avoid using batches in distributed metadata log keyspace > - [https://github.com/krummas/cassandra/commit/d4b4766e0b] > [CEP-21] Fix table metadata serialization > - [https://github.com/krummas/cassandra/commit/4056bab669] > [CEP-21] add more metrics > - [https://github.com/krummas/cassandra/commit/b6ccb559f5] > [CEP-21] getHostIdForEndpoint return null if unknown endpoint > - [https://github.com/krummas/cassandra/commit/b9243df05b] > [CEP-21] CMS handling > - [https://github.com/krummas/cassandra/commit/15eea30d43] > - [https://github.com/krummas/cassandra/commit/d64da5f5e4] > - [https://github.com/krummas/cassandra/commit/61deb52811] > [CEP-21] Upgrade fixes > - [https://github.com/krummas/cassandra/commit/33d186b4ce] > Properly set system.local host id on upgrade. > - [https://github.com/krummas/cassandra/commit/b96bdc83e1] > If replica misses migration message, set migration as successfull when it > sees the first epoch bump. > - [https://github.com/krummas/cassandra/commit/712828bc82] > Handle hints on upgrade - we change the hostid when enabling CMS, hints > should be delivered before that. > [CEP-21] Catchup/log fetching improvements > - [https://github.com/krummas/cassandra/commit/31a183e236] > When an instance sees a message from a peer with a newer epoch, try to catch > up from that peer instead of the CMS to reduce load on the CMS nodes and to > allow for cluster to quiesce in the case of the CMS being down. > - [https://github.com/krummas/cassandra/commit/8c6a4b35db] > We can get a snapshot when catching up, in this case the pending log should > first apply the snapshot and skip any previous entries. > - [https://github.com/krummas/cassandra/commit/387853487f] > When deserializing partition update, allow if current epoch >= serialized > epoch > - [https://github.com/krummas/cassandra/commit/626d224716] > When we replay from a snapshot we might see a node as LEFT for the first time > (it was bootstrapped and left while we were down) > [CEP-21] Require Paxos V2 for cluster metadata log operations > - [https://github.com/krummas/cassandra/commit/2217f551a6] > TCM is required to use Paxos V2 to because of the way the legacy paxos path > uses a keyspace’s RF to assert whether there are enough available replicas to > perform the read before a CAS. It doesn’t work properly with meta strategy > when adding CMS members > [CEP-21] Disaster recovery > - [https://github.com/krummas/cassandra/commit/9011233604] > Allow an instance to dump its current cluster metadata, and force-boot from > it. Basically we need a way to force an instance to become the CMS, in case > the original CMS goes down. > [CEP-21] Switch nodeId from uuid to int > - [https://github.com/krummas/cassandra/commit/aea5500ae0] > [CEP-21] Make CQLSSTableW
[cassandra] branch trunk updated (1c3c5008f9 -> 5aa7da5ebd)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 1c3c5008f9 Merge branch 'cassandra-5.0' into trunk add b4d99c1a07 Prepare debian changelog for 5.0-alpha1 new 5aa7da5ebd 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: - 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. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 5aa7da5ebde093c32a6ac22d28388ed572e77615 Merge: 1c3c5008f9 b4d99c1a07 Author: Mick Semb Wever AuthorDate: Fri Sep 1 11:51:28 2023 +0200 Merge branch 'cassandra-5.0' into trunk * cassandra-5.0: Prepare debian changelog for 5.0-alpha1 - 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 (865954fd99 -> b4d99c1a07)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 865954fd99 Merge branch 'cassandra-4.1' into cassandra-5.0 add b4d99c1a07 Prepare debian changelog for 5.0-alpha1 No new revisions were added by this update. Summary of changes: debian/changelog | 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
svn commit: r63730 - in /dev/cassandra/5.0-alpha1/redhat: ./ noboolean/ noboolean/repodata/ repodata/
Author: mck Date: Fri Sep 1 09:46:38 2023 New Revision: 63730 Log: staging cassandra rpm packages for 5.0-alpha1 Added: dev/cassandra/5.0-alpha1/redhat/ dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.noarch.rpm (with props) dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.src.rpm (with props) dev/cassandra/5.0-alpha1/redhat/cassandra-tools-5.0~alpha1-1.noarch.rpm (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/ dev/cassandra/5.0-alpha1/redhat/noboolean/cassandra-5.0~alpha1-1.noarch.rpm (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/cassandra-5.0~alpha1-1.src.rpm (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/cassandra-tools-5.0~alpha1-1.noarch.rpm (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/ dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/55c6e7f354ce7685d6edc42316635e5ab342523768c81f77e0345ee0db0b79f8-filelists.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/55c6e7f354ce7685d6edc42316635e5ab342523768c81f77e0345ee0db0b79f8-filelists.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/8e39f387d6dc507b8292b15e7795edea21fb5cd106d04ec5ee4eadea2769-other.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/8e39f387d6dc507b8292b15e7795edea21fb5cd106d04ec5ee4eadea2769-other.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/d1d43b92849d4725948120d2077fe663d4ad0c76bb037af6dbbf1d27e802344b-primary.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/d1d43b92849d4725948120d2077fe663d4ad0c76bb037af6dbbf1d27e802344b-primary.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/d4810568fd6378097c0924218444e65e4d985310f0cf544ade7d48a45aa514c8-other.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/d4810568fd6378097c0924218444e65e4d985310f0cf544ade7d48a45aa514c8-other.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/eaeddf670134d11eacf8a446f9227e3d5a16d53facba6952c96e81ee9d8c5d99-filelists.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/eaeddf670134d11eacf8a446f9227e3d5a16d53facba6952c96e81ee9d8c5d99-filelists.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/f23fe5691b922734d2a4be46cd369d5767ee8ccdc0b459723f418995ab99af48-primary.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/f23fe5691b922734d2a4be46cd369d5767ee8ccdc0b459723f418995ab99af48-primary.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/repomd.xml dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/repomd.xml.asc dev/cassandra/5.0-alpha1/redhat/repodata/ dev/cassandra/5.0-alpha1/redhat/repodata/8ab89c82482b950a1ced7eaeacb7cf5ea4941ba4900dc174b95b43289b5ae7ac-filelists.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/repodata/8ab89c82482b950a1ced7eaeacb7cf5ea4941ba4900dc174b95b43289b5ae7ac-filelists.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/repodata/a189e99b8e8a979bee3b162a57b1d2e2944fa3d1c6855b0da2ff3f759f6d3f58-primary.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/repodata/a189e99b8e8a979bee3b162a57b1d2e2944fa3d1c6855b0da2ff3f759f6d3f58-primary.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/repodata/b36a9e14bc6e7a38451eb89e904b2e26d99da23f26d6115a3b3e1904215508a0-other.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/repodata/b36a9e14bc6e7a38451eb89e904b2e26d99da23f26d6115a3b3e1904215508a0-other.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/repodata/d8ffac7980ad0ad6a103dd9bcba88295aa49321633954df595ee15bd735062ab-filelists.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/repodata/d8ffac7980ad0ad6a103dd9bcba88295aa49321633954df595ee15bd735062ab-filelists.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/repodata/e2dd4f65900565bc80221e57c9baac49498954d6da90a69768bd544ef2743149-other.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/repodata/e2dd4f65900565bc80221e57c9baac49498954d6da90a69768bd544ef2743149-other.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/repodata/e8cfce66ce158a4039c5fce28cebc17f99a17df3af05e7e3cca6161041644a83-primary.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/repodata/e8cfce66ce158a4039c5fce28cebc17f99a17df3af05e7e3cca6161041644a83-primary.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/repodata/repomd.xml dev/cassandra/5.0-alpha1/redhat/repodata/repomd.xml.asc Added: dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.noarch.rpm == Binary file - no diff available. Propchange: dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.noarch.rpm -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.s
svn commit: r63729 - in /dev/cassandra/5.0-alpha1/debian: ./ dists/ dists/50x/ dists/50x/main/ dists/50x/main/binary-amd64/ dists/50x/main/binary-arm64/ dists/50x/main/binary-i386/ dists/50x/main/sour
Author: mck Date: Fri Sep 1 09:39:45 2023 New Revision: 63729 Log: staging cassandra debian packages for 5.0-alpha1 Added: dev/cassandra/5.0-alpha1/debian/ dev/cassandra/5.0-alpha1/debian/cassandra-tools_5.0~alpha1_all.deb (with props) dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.dsc dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.tar.gz (with props) dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1_all.deb (with props) dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1_amd64.buildinfo dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1_amd64.changes dev/cassandra/5.0-alpha1/debian/dists/ dev/cassandra/5.0-alpha1/debian/dists/50x/ dev/cassandra/5.0-alpha1/debian/dists/50x/InRelease dev/cassandra/5.0-alpha1/debian/dists/50x/Release dev/cassandra/5.0-alpha1/debian/dists/50x/Release.gpg dev/cassandra/5.0-alpha1/debian/dists/50x/main/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-amd64/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-amd64/Packages dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-amd64/Packages.gz (with props) dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-amd64/Release dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-arm64/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-arm64/Packages dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-arm64/Packages.gz (with props) dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-arm64/Release dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-i386/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-i386/Packages dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-i386/Packages.gz (with props) dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-i386/Release dev/cassandra/5.0-alpha1/debian/dists/50x/main/source/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/source/Release dev/cassandra/5.0-alpha1/debian/dists/50x/main/source/Sources.gz (with props) dev/cassandra/5.0-alpha1/debian/pool/ dev/cassandra/5.0-alpha1/debian/pool/main/ dev/cassandra/5.0-alpha1/debian/pool/main/c/ dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/ dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/cassandra-tools_5.0~alpha1_all.deb (with props) dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/cassandra_5.0~alpha1.dsc dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/cassandra_5.0~alpha1.tar.gz (with props) dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/cassandra_5.0~alpha1_all.deb (with props) Added: dev/cassandra/5.0-alpha1/debian/cassandra-tools_5.0~alpha1_all.deb == Binary file - no diff available. Propchange: dev/cassandra/5.0-alpha1/debian/cassandra-tools_5.0~alpha1_all.deb -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.dsc == --- dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.dsc (added) +++ dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.dsc Fri Sep 1 09:39:45 2023 @@ -0,0 +1,41 @@ +-BEGIN PGP SIGNED MESSAGE- +Hash: SHA512 + +Format: 1.0 +Source: cassandra +Binary: cassandra, cassandra-tools +Architecture: all +Version: 5.0~alpha1 +Maintainer: Eric Evans +Uploaders: Sylvain Lebresne +Homepage: https://cassandra.apache.org +Standards-Version: 3.8.3 +Vcs-Browser: https://gitbox.apache.org/repos/asf?p=cassandra.git +Vcs-Git: https://gitbox.apache.org/repos/asf/cassandra.git +Build-Depends: debhelper (>= 11), openjdk-11-jdk | openjdk-11-jdk-headless | openjdk-17-jdk | openjdk-17-jdk-headless, ant (>= 1.10), ant-optional (>= 1.10), dh-python, python3-dev (>= 3.6), quilt, bash-completion +Package-List: + cassandra deb misc extra arch=all + cassandra-tools deb misc extra arch=all +Checksums-Sha1: + b90f868d12e5202550d21d6de8052a9a1ae3d73f 14721606 cassandra_5.0~alpha1.tar.gz +Checksums-Sha256: + b2a12ae43fcbd1d4302e2deac19ec2b1f3d3c556eed287a5058fe5cd0e155dc9 14721606 cassandra_5.0~alpha1.tar.gz +Files: + 5b8f8dc06f37ac8810edc6a18fbfbbf0 14721606 cassandra_5.0~alpha1.tar.gz + +-BEGIN PGP SIGNATURE- + +iQIzBAEBCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmTxsS8ACgkQ6RM1134+ +h8v31RAAisTVeDs9K26s4JkF9dLjmI1oo5Xfs9NLIxql8Jmus4T/n7WwgOrbuBvg +hSwTiuVWbwqAKJnAD7pjAxeyU+rM4lCKT9PO4UsGLYP31ntJxkIcmqwD/DlnFa9H +kIbc6cUOsdetAfx4vl8u/RY4AorMMYd4RaD7E1Dt0mUtwUuqRCq/sRRuub1dG37o +mzw2oXgDrJnMazxrmCxLDtzOW/oYOvZhjfsfzcRDfJ+TLocom4YT3UDbKL8Z3bS8 +23g32VS62vC/VrhNaGTVmFKCeMRmyOfQTPhwVhcgo+SZ0BcJa4JE9YzOTSwCTMSE +to4MhTlx52dZZ8vNNrf1alBRCK7JIgxDMbnzHDL9B5/+OqAupFZFXw7iaiybhHIP +Qjdmcq9fo4kfKOlFHmARYjKG377YE942pKiw84poyZSiGxYmo8uNTm+c5Qe9BTiG +AAAq8H/Nk0WDgE54fdkb1FRkZMSU85FkmsyL/4cPEVAprWhnEpkGU6LVjg9AKxi1 +qAFpe1PpF
svn commit: r63728 - /dev/cassandra/5.0-alpha1/
Author: mck Date: Fri Sep 1 09:36:29 2023 New Revision: 63728 Log: staging cassandra 5.0-alpha1 Added: dev/cassandra/5.0-alpha1/ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz (with props) dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.asc dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha256 dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha512 dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz (with props) dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.asc dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.sha256 dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.sha512 Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.asc == --- dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.asc (added) +++ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.asc Fri Sep 1 09:36:29 2023 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmTxrn0ACgkQ6RM1134+ +h8vE4w//RFtYcFa2KfHUjHF0WqAvEJhcXcKQDAKalixJWSNedKLeZsJx3HNIi4yO +Z85PldMjIfhHa4RiwXbIHFSKX2CXxqfyTZPeYGr47ll1kmdqLytcaYM/qidvauha +10b1ILMrLGN0+mc7GMHsCdrN+P/9K9FVhl1M/PqDKZhYI3sePM0lkCXarDcImiTk +i/Jqfx9T9ZW6vjP3s1nicYXnnLbaXixjQ1jGwVyR3aDNmKOZewt/5fKpcpMHCw+y +8w6e5zO6JtGn3oLxyx5jh4jT/5Ap0nUsYe8uTYIlBgGBDMe59BbpQUlK/aX6FseZ +NbdUSTfNPJ3QtnvIiIWrZ8oYA3fRFisq4IztDeTcwJN4KkoGK1/NeBnQ/khRPNtH +t9rRFgIhE8rY8FPUZ7H9yAYomFVUzagwuxZ8u7nAqwEZoxy7xQ4xJ5BHsVDGEmq0 +0KmEYSfMfZFgcpZNi5gKhRqUqfmodKz2oO4bW7ccZZDpYqHw+K9q+jrqL1Y5sMTK +A4I/vYlbXtKMyQBjJD09pzYlL0mz73Y4cZjf0TaXnGiR51xI07xHKcTrUeSWHXYo +CrpIqWTK1W4nmyPD8o/jG0WYl2gUNUV0DB2MqiWuLdit3In89vpmLFRZ0M+l2wlm +aIkJSrzImWFJ+loS3MRTt3fjF+vRxT9BL6OHiB712KxzHKhx8UU= +=MC7N +-END PGP SIGNATURE- Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha256 == --- dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha256 (added) +++ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha256 Fri Sep 1 09:36:29 2023 @@ -0,0 +1 @@ +3e13971b90b0bca46e95f550e8f462b1e96d7649bb6ddabf9be5f2cde1ba6efc Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha512 == --- dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha512 (added) +++ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha512 Fri Sep 1 09:36:29 2023 @@ -0,0 +1 @@ +aa9c348a3b3e5bb2521bb7eeb6699cdd3e40fdb3ebc5b8f3cd3ca75b2503989595e7e19a65efcf03925fc6505fb49d3d378f8154ac103720e964936d16d55a95 Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.asc == --- dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.asc (added) +++ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.asc Fri Sep 1 09:36:29 2023 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmTxroAACgkQ6RM1134+ +h8vGsBAAvbuNq594N9DWmcgiK+sFDoYjuCwgKo2KyBS6ectDcLgSc0rzPHRtwgio +LHROEq8dwK2nIaigofQ0qX45qtSAPC9HtvFoY9fdW2GgyZ6UsjxuHnT27Ko2klSF +KNstFTUmeqksH7L/jbcsbhMgDkipgrtFuoymvyullN21aFUSPf+LgihsE4GH1qeI +0YlBKiO6QDTTySDA3ybvuMrTFmUo07acUiV0zEJU67Mwd4PiDfy+/nXNpp3OPRsI +qPpHnN5jrdmRDSlGdFIarezGk4SSpyL3TO/Nm34lIVopjmE01wYZLCE2DMSU5Hbr +FMK9D6cyIPM1A9o2bb6C0AEh65Qzb9DPIDeuxXe4+c9yvkC7s5/pMLFhEjrxufAC +cKV41V4q1Fq+oY0iNBknhHDEBUVzZw0Zdsf3JVoaxUJaDt1OhSeq7ER0D4Egvb3Z +IgDGgQcLS0Xet3ZWHQiZ5FSQ0JuAacV08nDCGttLrBV1FfoGfXnLofl7aec8oxTQ +x2M+AWrhyzf62NmI7OER67AaPB4YtfP5S/kbYMocM6FRhURmYwtZa5b/DhfVFSRs +yYdbXl/Sw5jMg0P+mfqwh3mCycDjB0PrF07hIr/JqJS5/fhsKWGjqX+YiAzaF31Q +gNlqywgHf0c33swXkiCTrEX1RZULgoexIEgyUmUmrIe14Y/9WRU= +=87RK +-END PGP SIGNATURE- Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.sha256 == --- dev/cassand
[cassandra] 01/01: Prepare debian changelog for 5.0-alpha1
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to tag 5.0-alpha1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git commit b4d99c1a07d48970a28bf651acaeba359b9695de Author: Mick Semb Wever AuthorDate: Fri Sep 1 11:23:00 2023 +0200 Prepare debian changelog for 5.0-alpha1 --- debian/changelog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 9593eede17..6388abff14 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,7 +2,7 @@ cassandra (5.0~alpha1) unstable; urgency=medium * New release - -- Mick Semb Wever Mon, 21 Aug 2023 18:21:54 +0200 + -- Mick Semb Wever Fri, 01 Sep 2023 11:22:35 +0200 cassandra (4.0~rc1) unstable; urgency=medium - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] tag 5.0-alpha1-tentative created (now b4d99c1a07)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to tag 5.0-alpha1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git at b4d99c1a07 (commit) This tag includes the following new commits: new b4d99c1a07 Prepare debian changelog for 5.0-alpha1 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. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] tag 5.0-alpha1-tentative deleted (was 62cb03cc73)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to tag 5.0-alpha1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git *** WARNING: tag 5.0-alpha1-tentative was deleted! *** was 62cb03cc73 Prepare debian changelog for 5.0-alpha1 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
svn commit: r63724 - /dev/cassandra/5.0-alpha1/
Author: mck Date: Fri Sep 1 07:27:37 2023 New Revision: 63724 Log: Cassandra 5.0-alpha1 – delete failed cut attempt Removed: dev/cassandra/5.0-alpha1/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17476) Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
[
https://issues.apache.org/jira/browse/CASSANDRA-17476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17476:
Test and Documentation Plan: Can't repro
Status: Patch Available (was: In Progress)
> Test failure: org.apache.cassandra.db.ImportTest.testImportCorrupt
> --
>
> Key: CASSANDRA-17476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17476
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> There are intermittent failures in
> {{org.apache.cassandra.db.ImportTest#testImportCorrupt}} in trunk. This has
> only be hit once in Jenkins, for {{testImportCorrupt-cdc}}:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1029/testReport/org.apache.cassandra.db/ImportTest/testImportCorrupt_cdc_3/
> {code}
> Error Message
> Data dir should contain one file expected:<1> but was:<2>
> Stacktrace
> junit.framework.AssertionFailedError: Data dir should contain one file
> expected:<1> but was:<2>
> at
> org.apache.cassandra.db.ImportTest.testCorruptHelper(ImportTest.java:349)
> at
> org.apache.cassandra.db.ImportTest.testImportCorrupt(ImportTest.java:378)
> 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-03-21 12:53:37,982 YamlConfigurationLoader.java:103 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> DEBUG [main] 2022-03-21 12:53:37,987 YamlConfigurationLoader.java:124 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml
> INFO [main] 2022-03-21 12:53:38,203 Config.java:1119 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> allocate_tokens_for_local_replication_factor=null; allow_extra_insecure
> ...[truncated 2109130 chars]...
> G [main] 2022-03-21 12:54:10,127 DefaultSchemaUpdateHandler.java:237 - Schema
> updated: SchemaTransformationResult{1a9fb97a-05c5-3af1-846c-72e67e40e056 -->
> 2326e45e-6c53-3f40-99c2-af12b234dfcf, diff=KeyspacesDiff{created=[],
> dropped=[KeyspaceMetadata{name=cql_test_keyspace_alt, kind=REGULAR,
> params=KeyspaceParams{durable_writes=true,
> replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
> replication_factor=1}}, tables=[], views=[], functions=[], types=[]}],
> altered=[]}}
> {code}
> However, it's possible to hit the failure on both {{testImportCorrupt}} and
> {{testImportCorruptWithoutValidationWithCopying}} with the test multiplexer,
> although with a very low flakiness:
> https://app.circleci.com/pipelines/github/adelapena/cassandra/1412/workflows/f2ca69cd-f1e3-450f-b444-a6f9fe6d1fd4/jobs/14186/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-18805) Upgrade caffeine to 3.1.8
[ https://issues.apache.org/jira/browse/CASSANDRA-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-18805: Status: Ready to Commit (was: Review In Progress) > Upgrade caffeine to 3.1.8 > - > > Key: CASSANDRA-18805 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18805 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > 3.1.8 is based on Java 11. This version is testing with newer JDK versions, > while 2.x versions are based on JDK8, and as I understand, only bug-fix > releases are expected. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
