[jira] [Commented] (CASSANDRA-18061) Add compaction type output result for nodetool compactionhistory
[ https://issues.apache.org/jira/browse/CASSANDRA-18061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645948#comment-17645948 ] maxwellguo commented on CASSANDRA-18061: hi [~brandonwilliams][~blambov] can you help to look at this little patch ?:D > Add compaction type output result for nodetool compactionhistory > > > Key: CASSANDRA-18061 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18061 > Project: Cassandra > Issue Type: Improvement > Components: Local/Compaction, Tool/nodetool >Reporter: maxwellguo >Assignee: maxwellguo >Priority: Low > Fix For: 4.2 > > Time Spent: 10m > Remaining Estimate: 0h > > If we want to see whether we have made a compaction and what kind of > compaction we have done for this node, we may go to see the > compaction_history system table for some deftails or use nodetool > compactionhistory command , But I found that the table do not specify the > compaction type so does the compactionhistory command too, like index build , > compaction type, clean or scrub for this node. So I think may be it is need > to add a type of compaction column to specify the compaction tpe for > system.compaction_history and so we can get the type of compaction through > system.compaction_history table or nodetool compactionhistory to see whether > we have made a major compact for this node .:) -- This message was sent by Atlassian 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-18094) Add python 3.11 to CI
[
https://issues.apache.org/jira/browse/CASSANDRA-18094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645930#comment-17645930
]
Berenguer Blasi edited comment on CASSANDRA-18094 at 12/12/22 6:43 AM:
---
{quote}all of the py311 tests will fail because we'll need to push a new docker
image, and then commit CASSANDRA-18088 for them to run and pass.{quote}
Correct, that's what I wanted to see and as far as we can go CI wise
{quote}I think that is overkill{quote}
icwym but we can still create branches for default, low and high and see the
workflows show correctly on circle, no need to trigger them yet, just check for
correctness?:
||Branch 1||Default||Low||High||
|4.0|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0-high]|
|4.1|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1-high]|
|trunk|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk-high]|
It seems all is ok besides any mistakes bc of my eyes on picking on these nitty
changes. I think that was necessary bc we have often broken circle on the
default config and similar things :shrug:
Are you going to merge this or base CASSANDRA-18088 off these branches and
merge when that one is done?
was (Author: bereng):
{quote}all of the py311 tests will fail because we'll need to push a new docker
image, and then commit CASSANDRA-18088 for them to run and pass.{quote}
Correct, that's what I wanted to see and as far as we can go CI wise
{quote}I think that is overkill{quote}
icwym but we can still create branches for default, low and high and see the
workflows show correctly on circle, no need to trigger them yet, just check for
correctness?:
||Branch 1||Default||Low||High||
|4.0|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0-high]|
|4.1|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1-high]|
|trunk|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk-high]|
> Add python 3.11 to CI
> -
>
> Key: CASSANDRA-18094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18094
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
>
> Python 3.11 has a small divergence that necessitates a SaferScanner for that
> version and those after it in CASSANDRA-18088, similar to what 3.8 did and we
> solved with CASSANDRA-15573. We should add 3.11 to our docker images so we
> can test with it.
--
This message was sent by Atlassian 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-18094) Add python 3.11 to CI
[
https://issues.apache.org/jira/browse/CASSANDRA-18094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645930#comment-17645930
]
Berenguer Blasi commented on CASSANDRA-18094:
-
{quote}all of the py311 tests will fail because we'll need to push a new docker
image, and then commit CASSANDRA-18088 for them to run and pass.{quote}
Correct, that's what I wanted to see and as far as we can go CI wise
{quote}I think that is overkill{quote}
icwym but we can still create branches for default, low and high and see the
workflows show correctly on circle, no need to trigger them yet, just check for
correctness?:
||Branch 1||Default||Low||High||
|4.0|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.0-high]|
|4.1|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-4.1-high]|
|trunk|[Default|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk]|[Low|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk-low]|[High|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18094-trunk-high]|
> Add python 3.11 to CI
> -
>
> Key: CASSANDRA-18094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18094
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
>
> Python 3.11 has a small divergence that necessitates a SaferScanner for that
> version and those after it in CASSANDRA-18088, similar to what 3.8 did and we
> solved with CASSANDRA-15573. We should add 3.11 to our docker images so we
> can test with it.
--
This message was sent by Atlassian 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-18108) Data loss after a system restart/upgrade (3.11.14)
[
https://issues.apache.org/jira/browse/CASSANDRA-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645916#comment-17645916
]
Caleb Rackliffe commented on CASSANDRA-18108:
-
[~kehan5800] I think this is going to be a case where we just need to prohibit
changing the names of primary key elements. You'll notice that
{{PartitionColumns}} was renamed {{RegularAndStaticColumns}} in CASSANDRA-9425
to more clearly indicate that is isn't meant to deal w/ key elements. (The
assertion from the trace you've posted is making sure {{add()}} is passed
either a regular or static column.)
> Data loss after a system restart/upgrade (3.11.14)
> --
>
> Key: CASSANDRA-18108
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18108
> Project: Cassandra
> Issue Type: Bug
>Reporter: Ke Han
>Priority: Normal
>
> When we upgrade Cassandra from 3.11.14 to 4.0.7, we found a data loss during
> the upgrade process. This bug can also be triggered if simply performing a
> system restart.
> h1. Steps to reproduce
> Start a 3.11.14 or 4.0.7 Cassandra node using default configurations. Execute
> the following cqlsh commands.
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 1 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c3 INT,c2 TEXT, PRIMARY KEY (c1 ))
> WITH speculative_retry = 'ALWAYS';
> INSERT INTO ks.tb (c1, c2) VALUES (2,'val');
> ALTER TABLE ks.tb DROP c2 ;
> ALTER TABLE ks.tb RENAME c1 TO c2; {code}
> Then execute a SELECT command, we get the correct data
> {code:java}
> cqlsh> SELECT * FROM ks.tb;
> c2 | c3
> +--
> 2 | null
> (1 rows){code}
> Flush and stop the Cassandra daemon.
> {code:java}
> bin/nodetool flush
> bin/nodetool stopdaemon{code}
> Then restart the node.
> {code:java}
> bin/cassandra{code}
> Start cqlsh, and execute the same SELECT command. The data in ks.tb is lost.
> {code:java}
> cqlsh> SELECT * FROM ks.tb;
> c2 | c3
> +
> (0 rows){code}
>
> During the node restart, we found an error log about initializing the table,
> but it didn't prevent the system from starting up.
> {code:java}
> INFO [main] 2022-12-09 21:37:54,234 ColumnFamilyStore.java:432 -
> Initializing ks.tb
> ERROR [SSTableBatchOpen:1] 2022-12-09 21:37:54,237 CassandraDaemon.java:244 -
> Exception in thread Thread[SSTableBatchOpen:1,5,main]
> java.lang.AssertionError: null
> at
> org.apache.cassandra.db.PartitionColumns$Builder.add(PartitionColumns.java:161)
> at
> org.apache.cassandra.db.SerializationHeader$Component.toHeader(SerializationHeader.java:340)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:522)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:385)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader$3.run(SSTableReader.java:570)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:84)
> at java.lang.Thread.run(Thread.java:750) {code}
>
> This bug can also be triggered if we perform an upgrade from 3.11.14 to 4.0.7
> and execute the SELECT command in the new version. (*The token_num
> configuration in 4.0.7 is modified to 16 for upgrade compatibility purposes,
> all the other configurations are using default values)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18109) Unknown column cdc during deserialization ERROR when upgrading from 3.0.28 to 3.11.14
[
https://issues.apache.org/jira/browse/CASSANDRA-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18109:
-
Resolution: Not A Problem
Status: Resolved (was: Triage Needed)
> Unknown column cdc during deserialization ERROR when upgrading from 3.0.28 to
> 3.11.14
> -
>
> Key: CASSANDRA-18109
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18109
> Project: Cassandra
> Issue Type: Bug
>Reporter: Ke Han
>Priority: Normal
> Attachments: N0-system.log, N1-system.log, N2-system.log
>
>
> When we performed a rolling upgrade from 3.0.28 to 3.11.14, we encountered
> the following error message during the upgrade process. It doesn't prevent
> the upgrade process, but it's in ERROR log level and causes concerns for the
> upgrade process.
> {code:java}
> ERROR [MessagingService-Incoming-/192.168.107.2] 2022-12-10 04:01:12,449
> CassandraDaemon.java:265 - Exception in thread
> Thread[MessagingService-Incoming-/192.168.107.2,5,main]
> java.lang.RuntimeException: Unknown column cdc during deserialization
> at
> org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:445)
> at
> org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:446)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:190)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:734)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:722)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:337)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:346)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:574)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:557)
> at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:216)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:193)
> at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:96)
> INFO [MigrationStage:1] 2022-12-10 04:01:13,394
> MigrationCoordinator.java:523 - Sending schema pull request to /192.168.107.2
> at 1670644873394 with timeout 1
> ERROR [MessagingService-Incoming-/192.168.107.2] 2022-12-10 04:01:13,427
> CassandraDaemon.java:265 - Exception in thread
> Thread[MessagingService-Incoming-/192.168.107.2,5,main]
> java.lang.RuntimeException: Unknown column cdc during deserialization
> at
> org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:445)
> at
> org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:446)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:190)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:734)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:722)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:337)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:346)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:574)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:557)
> at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:216)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:193)
> at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:96){code}
> h1. Steps to reproduce
> Configure a 3-node Cassandra cluster (N0, N1 and N2) in 3.0.28 using the
> default configuration setting. Configure N0 as the seed node.
> For the new version configuration (3.11.14), set *cdc_enabled: true* in
> cassandra.yaml. All the other configurations use default values.
> Perform a rolling upgrade.
> # Start up the 3-node cluster in 3.0.28.
> # Drain, shutdown and upgrade
[jira] [Commented] (CASSANDRA-18109) Unknown column cdc during deserialization ERROR when upgrading from 3.0.28 to 3.11.14
[
https://issues.apache.org/jira/browse/CASSANDRA-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645822#comment-17645822
]
Ke Han commented on CASSANDRA-18109:
[~jmckenzie] Thanks for the suggestions! I'll refer to NEWS.txt to do the
upgrade procedure.
> Unknown column cdc during deserialization ERROR when upgrading from 3.0.28 to
> 3.11.14
> -
>
> Key: CASSANDRA-18109
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18109
> Project: Cassandra
> Issue Type: Bug
>Reporter: Ke Han
>Priority: Normal
> Attachments: N0-system.log, N1-system.log, N2-system.log
>
>
> When we performed a rolling upgrade from 3.0.28 to 3.11.14, we encountered
> the following error message during the upgrade process. It doesn't prevent
> the upgrade process, but it's in ERROR log level and causes concerns for the
> upgrade process.
> {code:java}
> ERROR [MessagingService-Incoming-/192.168.107.2] 2022-12-10 04:01:12,449
> CassandraDaemon.java:265 - Exception in thread
> Thread[MessagingService-Incoming-/192.168.107.2,5,main]
> java.lang.RuntimeException: Unknown column cdc during deserialization
> at
> org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:445)
> at
> org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:446)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:190)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:734)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:722)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:337)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:346)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:574)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:557)
> at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:216)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:193)
> at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:96)
> INFO [MigrationStage:1] 2022-12-10 04:01:13,394
> MigrationCoordinator.java:523 - Sending schema pull request to /192.168.107.2
> at 1670644873394 with timeout 1
> ERROR [MessagingService-Incoming-/192.168.107.2] 2022-12-10 04:01:13,427
> CassandraDaemon.java:265 - Exception in thread
> Thread[MessagingService-Incoming-/192.168.107.2,5,main]
> java.lang.RuntimeException: Unknown column cdc during deserialization
> at
> org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:445)
> at
> org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:446)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:190)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:734)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:722)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:337)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:346)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:574)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:557)
> at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:216)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:193)
> at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:96){code}
> h1. Steps to reproduce
> Configure a 3-node Cassandra cluster (N0, N1 and N2) in 3.0.28 using the
> default configuration setting. Configure N0 as the seed node.
> For the new version configuration (3.11.14), set *cdc_enabled: true* in
> cassandra.yaml. All the other configurations use default values.
> Perform a rolling upgrade.
> # Start up the 3-n
[jira] [Commented] (CASSANDRA-18110) Streaming fails during multiple concurrent host replacements
[
https://issues.apache.org/jira/browse/CASSANDRA-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645812#comment-17645812
]
Jon Meredith commented on CASSANDRA-18110:
--
To clarify the workaround, on any new nodes being started, ensure the config is
set with
{code:java}
internode_streaming_tcp_user_timeout: 0s
{code}
and on existing nodes in the cluster, the timeout can be reset with JMX without
restarting
{code:java}
org.apache.cassandra.db/StorageService/InternodeStreamingTcpUserTimeoutInMS{code}
before the bootstrap attempt.
> Streaming fails during multiple concurrent host replacements
>
>
> Key: CASSANDRA-18110
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18110
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Bootstrap and Decommission
>Reporter: Jon Meredith
>Assignee: Jon Meredith
>Priority: Urgent
> Fix For: 4.1
>
>
> Running four concurrent host replacements on a 4.1.0 development cluster has
> repeatably failed to complete bootstrap with all four hosts failing bootsrrap
> and staying in JOINING, logging the message.
> {code:java}
> ERROR 2022-12-07T21:15:48,860 [main]
> org.apache.cassandra.service.StorageService:2019 - Error while waiting on
> bootstrap to complete. Bootstrap will have to be restarted.
> {code}
> Bootstrap fails as the the FileStreamTasks on the streaming followers
> encounter an EOF while transmitting the files.
> {code:java}
> ERROR 2022-12-07T15:49:39,164 [NettyStreaming-Outbound-/1.2.3.4.7000:2]
> org.apache.cassandra.streaming.StreamSession:718 - [Stream
> #8d313690-7674-11ed-813f-95c261b64a82] Streaming error occurred on session
> with peer 1.2.3.4:7000 through 1.2.3.4:40292
> org.apache.cassandra.net.AsyncChannelOutputPlus$FlushException: The channel
> this output stream was writing to has been closed
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.propagateFailedFlush(AsyncChannelOutputPlus.java:200)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.waitUntilFlushed(AsyncChannelOutputPlus.java:158)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.waitForSpace(AsyncChannelOutputPlus.java:140)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.beginFlush(AsyncChannelOutputPlus.java:97)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncStreamingOutputPlus.lambda$writeToChannel$0(AsyncStreamingOutputPlus.java:124)
> ~[cassandra.jar]
>at
> org.apache.cassandra.db.streaming.CassandraCompressedStreamWriter.lambda$write$0(CassandraCompressedStreamWriter.java:89)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncStreamingOutputPlus.writeToChannel(AsyncStreamingOutputPlus.java:120)
> ~[cassandra.jar]
>at
> org.apache.cassandra.db.streaming.CassandraCompressedStreamWriter.write(CassandraCompressedStreamWriter.java:88)
> ~[cassandra.jar]
>at
> org.apache.cassandra.db.streaming.CassandraOutgoingFile.write(CassandraOutgoingFile.java:177)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.messages.OutgoingStreamMessage.serialize(OutgoingStreamMessage.java:87)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.messages.OutgoingStreamMessage$1.serialize(OutgoingStreamMessage.java:45)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.messages.OutgoingStreamMessage$1.serialize(OutgoingStreamMessage.java:34)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.messages.StreamMessage.serialize(StreamMessage.java:39)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel$FileStreamTask.run(StreamingMultiplexedChannel.java:311)
> [cassandra.jar]
>at
> org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> [cassandra.jar]
>at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> [cassandra.jar]
>at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> [cassandra.jar]
>at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
>at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
>at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [netty-all-4.1.58.Final.jar:4.1.58.Final]
>at java.lang.Thread.run(Thread.java:829) [?:?]
>Suppressed: java.nio.channels.ClosedChannelException
>at
> org.apache.cassandra.net.AsyncStreamingOutputPlus.doFlush(AsyncStreamingOutputPlus.java:82)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.flush(Async
[jira] [Commented] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[ https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645774#comment-17645774 ] Erick Ramirez commented on CASSANDRA-18063: --- Noting here – I've replaced "Stable" with "Rock Solid" in the title as per [~mck] 's feedback. Both the homepage + the blog post have been updated. 🍻 > WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, > Cloud-Native, Strongly Consistent, and Scale" > > > Key: CASSANDRA-18063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18063 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18063-01-homepage.png, c18063-02-blog-index.png, > c18063-03-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 homepage update and blog on 4.1. > If this blog cannot be published by the noted publish date on the blog, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[ https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18063: --- +1 (this can't get published until the release is finalised and announced. the dates in the patch must also be updated.) > WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, > Cloud-Native, Strongly Consistent, and Scale" > > > Key: CASSANDRA-18063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18063 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18063-01-homepage.png, c18063-02-blog-index.png, > c18063-03-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 homepage update and blog on 4.1. > If this blog cannot be published by the noted publish date on the blog, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[ https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18063: --- Reviewers: Josh McKenzie, Michael Semb Wever > WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, > Cloud-Native, Strongly Consistent, and Scale" > > > Key: CASSANDRA-18063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18063 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18063-01-homepage.png, c18063-02-blog-index.png, > c18063-03-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 homepage update and blog on 4.1. > If this blog cannot be published by the noted publish date on the blog, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[
https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645772#comment-17645772
]
Erick Ramirez commented on CASSANDRA-18063:
---
(!) Please do NOT commit without updating the publish date in
{{pages/index.adoc}} + {{{}pages/blog/Cassandra-4.1-is-here.adoc{}}}. (!)
/cc [~mck] , [~e.dimitrova]
> WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable,
> Cloud-Native, Strongly Consistent, and Scale"
>
>
> Key: CASSANDRA-18063
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18063
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: NA
>
> Attachments: c18063-01-homepage.png, c18063-02-blog-index.png,
> c18063-03-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the November
> 2022 homepage update and blog on 4.1.
> If this blog cannot be published by the noted publish date on the blog,
> please contact me, suggest changes, or correct the date when possible in the
> pull request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[ https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18063: -- Attachment: (was: c18063-03-blog-post.png) > WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, > Cloud-Native, Strongly Consistent, and Scale" > > > Key: CASSANDRA-18063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18063 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18063-01-homepage.png, c18063-02-blog-index.png, > c18063-03-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 homepage update and blog on 4.1. > If this blog cannot be published by the noted publish date on the blog, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[ https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18063: -- Attachment: c18063-03-blog-post.png > WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, > Cloud-Native, Strongly Consistent, and Scale" > > > Key: CASSANDRA-18063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18063 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18063-01-homepage.png, c18063-02-blog-index.png, > c18063-03-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 homepage update and blog on 4.1. > If this blog cannot be published by the noted publish date on the blog, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[
https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-18063:
--
Status: Patch Available (was: Open)
Patch:
||Branch||PR||
|{{trunk}}|[#201|https://github.com/apache/cassandra-website/pull/201]|
!c18063-01-homepage.png|width=300!
!c18063-02-blog-index.png|width=300!
!c18063-03-blog-post.png|width=300!
> WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable,
> Cloud-Native, Strongly Consistent, and Scale"
>
>
> Key: CASSANDRA-18063
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18063
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: NA
>
> Attachments: c18063-01-homepage.png, c18063-02-blog-index.png,
> c18063-03-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the November
> 2022 homepage update and blog on 4.1.
> If this blog cannot be published by the noted publish date on the blog,
> please contact me, suggest changes, or correct the date when possible in the
> pull request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[ https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18063: -- Attachment: c18063-03-blog-post.png c18063-02-blog-index.png c18063-01-homepage.png > WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, > Cloud-Native, Strongly Consistent, and Scale" > > > Key: CASSANDRA-18063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18063 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18063-01-homepage.png, c18063-02-blog-index.png, > c18063-03-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 homepage update and blog on 4.1. > If this blog cannot be published by the noted publish date on the blog, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[ https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18063: -- Authors: Chris Thornett, Diogenese Topper, Erick Ramirez (was: Erick Ramirez) > WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, > Cloud-Native, Strongly Consistent, and Scale" > > > Key: CASSANDRA-18063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18063 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18063-01-homepage.png, c18063-02-blog-index.png, > c18063-03-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 homepage update and blog on 4.1. > If this blog cannot be published by the noted publish date on the blog, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18063) WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, Cloud-Native, Strongly Consistent, and Scale"
[ https://issues.apache.org/jira/browse/CASSANDRA-18063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18063: -- Fix Version/s: NA Assignee: Erick Ramirez Status: Open (was: Triage Needed) > WEBSITE - 4.1 Homepage update and blog post "Apache Cassandra 4.1: Stable, > Cloud-Native, Strongly Consistent, and Scale" > > > Key: CASSANDRA-18063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18063 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Fix For: NA > > Attachments: c18063-01-homepage.png, c18063-02-blog-index.png, > c18063-03-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 homepage update and blog on 4.1. > If this blog cannot be published by the noted publish date on the blog, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18109) Unknown column cdc during deserialization ERROR when upgrading from 3.0.28 to 3.11.14
[
https://issues.apache.org/jira/browse/CASSANDRA-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645767#comment-17645767
]
Josh McKenzie commented on CASSANDRA-18109:
---
Ah. Yeah, to Brandon's point, we call out in NEWS.txt that you shouldn't enable
the new feature [until the entire cluster is
upgraded|https://github.com/apache/cassandra/blob/cassandra-3.11.14/NEWS.txt#L463-L465].
> Unknown column cdc during deserialization ERROR when upgrading from 3.0.28 to
> 3.11.14
> -
>
> Key: CASSANDRA-18109
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18109
> Project: Cassandra
> Issue Type: Bug
>Reporter: Ke Han
>Priority: Normal
> Attachments: N0-system.log, N1-system.log, N2-system.log
>
>
> When we performed a rolling upgrade from 3.0.28 to 3.11.14, we encountered
> the following error message during the upgrade process. It doesn't prevent
> the upgrade process, but it's in ERROR log level and causes concerns for the
> upgrade process.
> {code:java}
> ERROR [MessagingService-Incoming-/192.168.107.2] 2022-12-10 04:01:12,449
> CassandraDaemon.java:265 - Exception in thread
> Thread[MessagingService-Incoming-/192.168.107.2,5,main]
> java.lang.RuntimeException: Unknown column cdc during deserialization
> at
> org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:445)
> at
> org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:446)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:190)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:734)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:722)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:337)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:346)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:574)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:557)
> at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:216)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:193)
> at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:96)
> INFO [MigrationStage:1] 2022-12-10 04:01:13,394
> MigrationCoordinator.java:523 - Sending schema pull request to /192.168.107.2
> at 1670644873394 with timeout 1
> ERROR [MessagingService-Incoming-/192.168.107.2] 2022-12-10 04:01:13,427
> CassandraDaemon.java:265 - Exception in thread
> Thread[MessagingService-Incoming-/192.168.107.2,5,main]
> java.lang.RuntimeException: Unknown column cdc during deserialization
> at
> org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:445)
> at
> org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:446)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:190)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:734)
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:722)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:337)
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:346)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:574)
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:557)
> at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:216)
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:193)
> at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:96){code}
> h1. Steps to reproduce
> Configure a 3-node Cassandra cluster (N0, N1 and N2) in 3.0.28 using the
> default configuration setting. Configure N0 as the seed node.
> For the new version configuration (3.11.14), set *cdc_e
[jira] [Updated] (CASSANDRA-18110) Streaming fails during multiple concurrent host replacements
[
https://issues.apache.org/jira/browse/CASSANDRA-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18110:
---
Severity: Critical (was: Normal)
> Streaming fails during multiple concurrent host replacements
>
>
> Key: CASSANDRA-18110
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18110
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Bootstrap and Decommission
>Reporter: Jon Meredith
>Assignee: Jon Meredith
>Priority: Urgent
> Fix For: 4.1
>
>
> Running four concurrent host replacements on a 4.1.0 development cluster has
> repeatably failed to complete bootstrap with all four hosts failing bootsrrap
> and staying in JOINING, logging the message.
> {code:java}
> ERROR 2022-12-07T21:15:48,860 [main]
> org.apache.cassandra.service.StorageService:2019 - Error while waiting on
> bootstrap to complete. Bootstrap will have to be restarted.
> {code}
> Bootstrap fails as the the FileStreamTasks on the streaming followers
> encounter an EOF while transmitting the files.
> {code:java}
> ERROR 2022-12-07T15:49:39,164 [NettyStreaming-Outbound-/1.2.3.4.7000:2]
> org.apache.cassandra.streaming.StreamSession:718 - [Stream
> #8d313690-7674-11ed-813f-95c261b64a82] Streaming error occurred on session
> with peer 1.2.3.4:7000 through 1.2.3.4:40292
> org.apache.cassandra.net.AsyncChannelOutputPlus$FlushException: The channel
> this output stream was writing to has been closed
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.propagateFailedFlush(AsyncChannelOutputPlus.java:200)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.waitUntilFlushed(AsyncChannelOutputPlus.java:158)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.waitForSpace(AsyncChannelOutputPlus.java:140)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.beginFlush(AsyncChannelOutputPlus.java:97)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncStreamingOutputPlus.lambda$writeToChannel$0(AsyncStreamingOutputPlus.java:124)
> ~[cassandra.jar]
>at
> org.apache.cassandra.db.streaming.CassandraCompressedStreamWriter.lambda$write$0(CassandraCompressedStreamWriter.java:89)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncStreamingOutputPlus.writeToChannel(AsyncStreamingOutputPlus.java:120)
> ~[cassandra.jar]
>at
> org.apache.cassandra.db.streaming.CassandraCompressedStreamWriter.write(CassandraCompressedStreamWriter.java:88)
> ~[cassandra.jar]
>at
> org.apache.cassandra.db.streaming.CassandraOutgoingFile.write(CassandraOutgoingFile.java:177)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.messages.OutgoingStreamMessage.serialize(OutgoingStreamMessage.java:87)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.messages.OutgoingStreamMessage$1.serialize(OutgoingStreamMessage.java:45)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.messages.OutgoingStreamMessage$1.serialize(OutgoingStreamMessage.java:34)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.messages.StreamMessage.serialize(StreamMessage.java:39)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.async.StreamingMultiplexedChannel$FileStreamTask.run(StreamingMultiplexedChannel.java:311)
> [cassandra.jar]
>at
> org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> [cassandra.jar]
>at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> [cassandra.jar]
>at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> [cassandra.jar]
>at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
>at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
>at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [netty-all-4.1.58.Final.jar:4.1.58.Final]
>at java.lang.Thread.run(Thread.java:829) [?:?]
>Suppressed: java.nio.channels.ClosedChannelException
>at
> org.apache.cassandra.net.AsyncStreamingOutputPlus.doFlush(AsyncStreamingOutputPlus.java:82)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.flush(AsyncChannelOutputPlus.java:229)
> ~[cassandra.jar]
>at
> org.apache.cassandra.net.AsyncChannelOutputPlus.close(AsyncChannelOutputPlus.java:248)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.async.NettyStreamingChannel$1.close(NettyStreamingChannel.java:141)
> ~[cassandra.jar]
>at
> org.apache.cassandra.streaming.as
