[RELEASE] Apache Cassandra 4.1.0 GA released

[Mick Semb Wever]

The Cassandra team is pleased to announce the GA release of Apache
Cassandra version 4.1.0.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is the first GA release of the 4.1 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/41x/ .

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.1.0
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.1.0
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: Failed service startup

[Marcus Eriksson]

This looks like https://issues.apache.org/jira/browse/CASSANDRA-17273

iirc you can merge the two files - making sure all ADD and REMOVE records are 
in both files, I think you would need to add 
`ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67417-big-,0,8][3940068469]`
 to the data02 transaction log file

Make sure you back up all involved sstables before trying this

/Marcus


On Mon, Dec 12, 2022 at 02:40:25PM +, Marc Hoppins wrote:
> Hi, all,
> 
> We had a failed HDD on one node. The node was shut down pending repair.  
> There are now 4 other nodes with Cassandra not running and unable to startup 
> due to the following kinds of error.  Is this kind of thing due to the 
> original stopped node?
> 
> ERROR [main] 2022-12-12 14:58:10,838 LogReplicaSet.java:145 - Mismatched line 
> in file 
> nb_txn_anticompactionafterrepair_5865e530-7a18-11ed-950f-954f6819a607.log: 
> got 
> 'ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67417-big-,0,8][3940068469]'
>  expected 
> 'ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67418-big-,0,8][2798461787]',
>  giving up
> ERROR [main] 2022-12-12 14:58:10,838 LogFile.java:161 - Failed to read 
> records for transaction log 
> [nb_txn_anticompactionafterrepair_5865e530-7a18-11ed-950f-954f6819a607.log in 
> /mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c,
>  
> /mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c]
> ERROR [main] 2022-12-12 14:58:10,840 LogTransaction.java:551 - Unexpected 
> disk state: failed to read transaction log 
> [nb_txn_anticompactionafterrepair_5865e530-7a18-11ed-950f-954f6819a607.log in 
> /mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c,
>  
> /mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c]
> Files and contents follow:
> /mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb_txn_anticompactionafterrepair_5865e530-7a18-11ed-950f-954f6819a607.log
> 
> ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67416-big-,0,8][1963077611]
> 
> ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67418-big-,0,8][2798461787]
> 
> REMOVE:[/mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67405-big-,1665045804823,8][1428695358]
> 
> REMOVE:[/mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67402-big-,1665050002894,8][2407633150]
> COMMIT:[,0,0][2613697770]
> /mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb_txn_anticompactionafterrepair_5865e530-7a18-11ed-950f-954f6819a607.log
> 
> ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67416-big-,0,8][1963077611]
> 
> ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67417-big-,0,8][3940068469]
> ***Does not match 
> 
>  in first replica file
> 
> ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67418-big-,0,8][2798461787]
> 
> REMOVE:[/mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67405-big-,1665045804823,8][1428695358]
> 
> REMOVE:[/mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67402-big-,1665050002894,8][2407633150]
> COMMIT:[,0,0][2613697770]
> 
> ERROR [main] 2022-12-12 14:58:10,841 CassandraDaemon.java:911 - Cannot remove 
> temporary or obsoleted files for hades.prod_md5_sha1 due to a problem with 
> transaction log files. Please check records with problems in the log messages 
> above and fix them. Refer to the 3.0 upgrading instructions in NEWS.txt for a 
> description of transaction log files.
> 
> Sstableutil only returned
> 
> ERROR 15:35:52,217 Mismatched line in file 
> nb_txn_anticompactionafterrepair_5865e530-7a18-11ed-950f-954f6819a607.log: 
> got 
> 'ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67417-big-,0,8][3940068469]'
>  expected 
> 'ADD:[/mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c/nb-67418-big-,0,8][2798461787]',
>  giving up
> ERROR 15:35:52,219 Failed to read records for transaction log 
> [nb_txn_anticompactionafterrepair_5865e530-7a18-11ed-950f-954f6819a607.log in 
> /mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c,
>  
> /mnt/data01/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c]
> ERROR 15:35:52,220 Unexpected disk state: failed to read transaction log 
> [nb_txn_anticompactionafterrepair_5865e530-7a18-11ed-950f-954f6819a607.log in 
> /mnt/data02/cassandra/data/hades/prod_md5_sha1-bb5bdca002b111edb9761fc3bb7c847c,
>  
> 

System.log

[Marc Hoppins]

HI all,

Is there a config setting to only log INFO line itself and omit the remaining 
java/netty items?  These are repeated every 30 seconds which creates 
un-necessary spam in the system log.  Despite having logback configured at INFO 
level, these extra items keep appearing.

INFO  [Messaging-EventLoop-3-1] 2022-12-13 09:29:34,743 NoSpamLogger.java:92 - 
/10.x.x.x:7000->/10.x.x.y:7000-URGENT_MESSAGES-[no-channel] failed to connect
io.netty.channel.ConnectTimeoutException: connection timed out: /10..x.x.y:7000
at 
io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at 
io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at 
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at 
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at 
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at 
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)

Thanks

M