av9ash/GitBugs huggingface dataset:
Bug: Broken "help" command on cqlsh 6.0.0
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 06/May/21 15:45
Resolved: 14/May/21 22:16

On cqlsh 5.0.1, "help select" command prints this:
{noformat}
cqlsh> help select
*** No browser to display CQL help. URL for help topic select : https://cassandra.apache.org/doc/cql3/CQL-3.2.html#selectStmt
{noformat}
However, on cqlsh 6.0.0, "help select" command prints this:
{noformat}
cqlsh> help select
object of type 'NoneType' has no len()
{noformat}
Steps to reproduce:
 # Create and start a Cassandra 4 docker container
{noformat}
~ $ docker create --name cassandra4 cassandra:4.0
~ $ docker start cassandra4{noformat}
 # Get a shell inside the docker container
{noformat}
 docker exec -ti CONTAINER_NAME bash{noformat}
 # Start a cqlsh and run the "help" command inside it (you have to wait for the Cassandra server starting, I had to run "nodetool enablebinary" too, not sure why)
{noformat}
root@b03a20987964:/# cqlsh
Connected to Test Cluster at 127.0.0.1:9042
[cqlsh 6.0.0 | Cassandra 4.0-rc1 | CQL spec 3.4.5 | Native protocol v5]
Use HELP for help.
cqlsh> help select
object of type 'NoneType' has no len()
cqlsh> 
{noformat}
Bug: Fix org.apache.cassandra.net.ConnectionTest.testMessageDeliveryOnReconnect
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 07/Jun/21 23:07
Resolved: 07/Jun/21 23:40

Failed here:

[https://jenkins-cm4.apache.org/job/Cassandra-4.0.0/13/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_cdc/]

Not reproducible locally but consistently reproducible in CircleCI multiplexer. 

https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/934/workflows/1e8eaf97-a528-4e05-9f95-a8ba1bf7a34a/jobs/5575
Bug: DOC - Refactor /quickstart guide
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 11/Jun/21 07:46
Resolved: 11/Jun/21 08:09

ON BEHALF OF https://github.com/polymetric:

It looks like whoever wrote this quickstart guide wrote it without actually testing. Nothing wrong with that, though! I did something like that just the other day. But it should probably be fixed. Cassandra sounds awesome to me but this didn't seem like the best way to give a first impression, so I tried my hand at improving it.

list of changes:
 * removed the authentication part as the test works fine without that and is probably a bit out of the scope of this document
 * replaced {{#}} comments in the CQL script with the proper {{--}}
 * is now {{$(pwd)}} as the former did not work on my system (Pop_OS 20.10, zsh) one of the invocations also had a missing right angle bracket
 * the functions {{toTimeStamp(toDate(now))}} threw an error. Apparently, the function {{toDate()}} is deprecated? I replaced it with the recommended {{toTimeStamp(now())}} ({{now}} was also missing its {{()}}) and ran into a second error - {{1234}} is not a valid value for type "text." so I added single quotes and voila.
 * used a network to connect the database and shell containers because host.docker.internal does not work on Linux
 * added another step with a docker command to use cqlsh interactively (there wasn't one before, all the previous command in step 4 did was load data.cql, it did not start an interactive session, which was very confusing)
 * rewrote and reorganized some of the text due to the new step

This should be tested on something other than Linux, because I haven't had a chance to do that.
 of course all these changes are subject to evaluation! I probably should've split it out into multiple commits. Hopefully the diff isn't too hard to read. Let me know if I forgot to mention something or you need anything clarified.
Bug: test_tombstone_failure_threshold_message assert checking if array == string, should check for array truthiness
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 09/Jun/21 22:59
Resolved: 10/Jun/21 00:13

The test pushed_notifications_test.py::TestVariousNotifications::test_tombstone_failure_threshold_message checks for the log message "Scanned over.* tombstones.* query aborted”, but this can happen on any node, so it will timeout checking node1 then check the other nodes; when this happens it checks that the returned result equals "Cannot find tombstone failure threshold error in log after failed query”, which isn’t possible as the return is matching log lines, this should be replaced by checking for failure truthiness.
Bug: WEBSITE - May 2021 updates
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 11/May/21 21:54
Resolved: 21/May/21 11:04

Sharing a batch of HTML updates to be made to the website that include:
 * Homepage – update banner to include playlist for World Party (replacing World Party registration promo)
 * Ecosystem – adding two new items and updating a name based on request from user list.
 * Update blog URL to fix 404
 * Update Black Rock logo naming to fix broken image
Bug: DROP COMPACT STORAGE does not invalidate prepared statements as it should 
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 04/Jun/21 09:00
Resolved: 04/Jun/21 11:29

{{DROP COMPACT STORAGE}} might change the number of columns of a table but as the prepared statement cache is not invalidate the query will not return the correct set of columns until the statement as been invalidate. That can lead to a surprising behavior where the resultset change at un expected point in time.

This problem only affect 3.0 and 3.11
Bug: Failure to execute queries should emit a KPI other than read timeout/unavailable so it can be alerted/tracked
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 08/Apr/21 22:15
Resolved: 02/Jun/21 03:56

When we are unable to parse a message we do not have a way to detect this from a monitoring point of view so can get into situations where we believe the database is fine but the clients are on-fire.  This case popped up in the 2.1 to 3.0 upgrade as paging state wasn’t mixed-mode safe.
Bug: LongLeveledCompactionStrategyCQLTest.stressTestCompactionStrategyManager fails
Status: In Progress
Priority: Normal
Created: 27/Apr/21 17:21

Test is failing occasionally as follows:

{noformat}
Caused by: java.lang.AssertionError: Got unexpected overlap in level 3
	at org.apache.cassandra.db.compaction.LeveledGenerations.addAll(LeveledGenerations.java:161)
	at org.apache.cassandra.db.compaction.LeveledManifest.addSSTables(LeveledManifest.java:131)
	at org.apache.cassandra.db.compaction.LeveledCompactionStrategy.addSSTable(LeveledCompactionStrategy.java:365)
	at org.apache.cassandra.db.compaction.CompactionStrategyManager.startup(CompactionStrategyManager.java:312)
	at org.apache.cassandra.db.compaction.CompactionStrategyManager.reload(CompactionStrategyManager.java:532)
	at org.apache.cassandra.db.compaction.CompactionStrategyManager.maybeReloadDiskBoundaries(CompactionStrategyManager.java:495)
	at org.apache.cassandra.db.compaction.CompactionStrategyManager.handleNotification(CompactionStrategyManager.java:743)
	at org.apache.cassandra.db.lifecycle.Tracker.notify(Tracker.java:508)
	at org.apache.cassandra.db.lifecycle.Tracker.notifyDiscarded(Tracker.java:502)
	at org.apache.cassandra.db.lifecycle.Tracker.replaceFlushed(Tracker.java:373)
	at org.apache.cassandra.db.ColumnFamilyStore.replaceFlushed(ColumnFamilyStore.java:1592)
	at org.apache.cassandra.db.ColumnFamilyStore$Flush.flushMemtable(ColumnFamilyStore.java:1194)
	at org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1075)
	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)
{noformat}

[Recent ci|https://ci-cassandra.apache.org/job/Cassandra-trunk/476/testReport/junit/org.apache.cassandra.db.compaction/LongLeveledCompactionStrategyCQLTest/stressTestCompactionStrategyManager/]
Bug: Fix flaky test testRequestResponse – org.apache.cassandra.net.MockMessagingServiceTest
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 15/Apr/21 19:00
Resolved: 20/Apr/21 17:59

https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/659/tests/

{code}
Error
expected:<1> but was:<0>
Stacktrace
junit.framework.AssertionFailedError: expected:<1> but was:<0>
	at org.apache.cassandra.net.MockMessagingServiceTest.testRequestResponse(MockMessagingServiceTest.java:81)
	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] 2021-04-15 08:22:46,838 YamlConfigurationLoader.java:93 - Configuration location: file:/home/cassandra/cassandra/test/conf/cassandra.yaml
DEBUG [main] 2021-04-15 08:22:46,840 YamlConfigurationLoader.java:112 - Loading settings from file:/home/cassandra/cassandra/test/conf/cassandra.yaml
DEBUG [main] 2021-04-15 08:22:46,899 InternalLoggerFactory.java:63 - Using SLF4J as the default logging framework
DEBUG [main] 2021-04-15 08:22:46,911 PlatformDependent0.java:417 - -Dio.netty.noUnsaf
...[truncated 61235 chars]...
te NORMAL, token [a57d4b7f61f49471614b7ac41f16477e]
DEBUG [main] 2021-04-15 08:22:49,840 StorageService.java:2674 - New node /127.0.0.1:7069 at token a57d4b7f61f49471614b7ac41f16477e
DEBUG [main] 2021-04-15 08:22:49,848 StorageService.java:2727 - Node /127.0.0.1:7069 state NORMAL, token [a57d4b7f61f49471614b7ac41f16477e]
INFO  [main] 2021-04-15 08:22:49,848 StorageService.java:2730 - Node /127.0.0.1:7069 state jump to NORMAL
DEBUG [main] 2021-04-15 08:22:49,849 StorageService.java:1619 - NORMAL
{code}
Bug: Security vulnerability  CVE-2020-7238 for Netty
Status: Resolved
Priority: Normal
Resolution: Not A Problem
Created: 26/May/21 06:17
Resolved: 26/May/21 15:06

*Cassandra Version: 3.11.10*

*Description :*
*Severity:* NVD CVSS:3.1 7.5 High

*Affecting Package*: netty-all 4.0.44.Final

*Source:* National Vulnerability Database

*Explanation from NVD:* Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869.

*Recommendation:* Upgrade package io.netty#netty-all to version 4.1.44.Final or above.
Bug: Security vulnerability CVE-2019-9518 for Netty
Status: Resolved
Priority: Normal
Resolution: Not A Problem
Created: 26/May/21 06:12
Resolved: 26/May/21 15:06

*Cassandra Version: 3.11.10*

*Description :* 
*Severity:* NVD CVSS:3.1 7.5 High

*Affecting Package*: netty-all 4.0.44.Final

*Source:* National Vulnerability Database

*Explanation from NVD:* Some HTTP/2 implementations are vulnerable to a flood of empty frames, potentially leading to a denial of service. The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. The peer spends time processing each frame disproportionate to attack bandwidth. This can consume excess CPU.

*Recommendation:* Upgrade package io.netty#netty-all to version 4.1.39.Final or above.
Bug: Unable to set TTL for existing cassandra cluster 3.11.5/8
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 25/May/21 16:16
Resolved: 26/May/21 15:03

We are unable to set TTL for system_distributed keyspace and getting following error.

Version 3.11.5/8

cassandra@cqlsh> ALTER TABLE system_distributed.repair_history WITH default_time_to_live = 604800;

*Unauthorized: Error from server: code=2100 [Unauthorized] message="Cannot ALTER <table system_distributed.repair_history>"*

 

tried with Cassandra and cassandraops user with no luck.

Any suggestions/fixes?
Bug: Error instantiating class com.datastax.spark.connector.cql.LocalNodeFirstLoadBalancingPolicy
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 24/May/21 15:42
Resolved: 24/May/21 15:55

Hi,

I updated java drive for version 4.11.1 and the spark connector stoped. 

The enviroment is Cassandra 4.0, java-drive 4.11.1, native-protocol 1.5.0, spark-connector 3.0.0, JDK 8, Ubuntu 16. Attached the pom.xlm for more informations.

Observations:

- The nodetool is running ok.

- The cqlsh is running ok. 

- Tomcat can load the .war.

- The keyspace is SimpleStrategy, only one node and DC. Standard configuration. 

- The spark failed.

 

*This is the error in the console log :*  java.io.IOException: Failed to open native connection to Cassandra at \{127.0.0.1:9042} :: Error instantiating class com.datastax.spark.connector.cql.LocalNodeFirstLoadBalancingPolicy (specified by basic.load-balancing-policy.class): com.datastax.oss.driver.internal.core.context.InternalDriverContext.getNodeFilter(Ljava/lang/String;)Ljava/util/function/Predicate;

 

*Caused by:* java.lang.IllegalArgumentException: Error instantiating class com.datastax.spark.connector.cql.LocalNodeFirstLoadBalancingPolicy (specified by basic.load-balancing-policy.class): com.datastax.oss.driver.internal.core.context.InternalDriverContext.getNodeFilter(Ljava/lang/String;)Ljava/util/function/Predicate;

*Caused by:* java.lang.NoSuchMethodError: com.datastax.oss.driver.internal.core.context.InternalDriverContext.getNodeFilter

I openned a issue  SPARKC-652 ([[https://datastax-oss.atlassian.net/browse/SPARKC-652])]

Best,
Bug: Gossip is not populated with tokens/host_ids
Status: Open
Priority: Normal
Created: 05/Apr/21 16:36

Originally when we began persisting host information such a tokens/host_id, we would populate gossip with this information.  At some point we began only populating TokenMetadata, which gives us most of the same benefit, but in a full ring restart where the gossip ether is empty, it populates useless info such as :

{quote}
/10.101.32.212
  generation:0
  heartbeat:0
  TOKENS: not present
{quote}

which is the minimum required for a state to exist.  Instead we should keep gossip in sync with TMD when populating this information like we used to do.
Bug: ConnectionTest is flaky
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 19/May/21 13:43
Resolved: 19/May/21 13:44

Failure observed: 

[https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_compression/]

 

3/100 failures in {{ConnectionTest observed in the new multiplexer, Java 8}}: [https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/cf7dcec6-612c-45d1-8471-623bde481dca/jobs/4069]

And 2/100 with Java 11: [https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/b750cd38-0263-4b5e-9bb8-a8be98214378/jobs/4065]
Bug: Move CASSANDRA-14559s bootstrap_test.py::TestBootstrap::test_node_cannot_join_as_hibernating_node_without_replace_address into a jvm-dtest
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 08/May/21 00:09
Resolved: 13/May/21 20:21

In debugging an issue I ended up porting bootstrap_test.py::TestBootstrap::test_node_cannot_join_as_hibernating_node_without_replace_address into a jvm-dtest, it would be good to move away from the python dtest in favor of a jvm-dtest
Bug: Multinode counters don't get updated
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/May/21 06:21
Resolved: 12/May/21 19:51

A multi node setup with counters doesn't update counters value. Works as expected on a single node though. Comes from [this|https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/cql_tests.py#L460] test. Repro:


{noformat}
ccm create counters40
ccm populate -n 2
ccm start
ccm node1 cqlsh
  CREATE KEYSPACE foo WITH REPLICATION = { 'class' : 'NetworkTopologyStrategy', 'datacenter1' : 1 } ;
  use foo;
  CREATE TABLE clicks ( userid int, url text, total counter, PRIMARY KEY (userid, url) ) WITH COMPACT STORAGE;
  ALTER TABLE clicks DROP COMPACT STORAGE;
  TRUNCATE clicks;
  UPDATE clicks SET total = total + 1 WHERE userid = 1 AND url = 'http://foo.com';
  SELECT total FROM clicks WHERE userid = 1 AND url = 'http://foo.com';

     total
    -------
         1
  UPDATE clicks SET total = total - 4 WHERE userid = 1 AND url = 'http://foo.com';
  SELECT total FROM clicks WHERE userid = 1 AND url = 'http://foo.com';

     total
    -------
         1 *********** Should be '-3'
{noformat}
Bug: Flaky test_pending_range
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 19/Apr/21 07:57
Resolved: 26/Apr/21 11:29

Flaky [test_pending_range|https://ci-cassandra.apache.org/job/Cassandra-trunk/445/testReport/junit/dtest-large-novnode.pending_range_test/TestPendingRangeMovements/test_pending_range/]

{noformat}
Error Message

AssertionError: assert None is not None  +  where None = <function search at 0x7f29dfa83b80>('127\\.0\\.0\\.1.*?Down.*?Moving', '\nDatacenter: datacenter1\n==========\nAddress         Rack        Status State   Load            Owns               ...   rack1       Up     Normal  90.86 KiB       40.00%              5534023222112865484                         \n\n\n  ')  +    where <function search at 0x7f29dfa83b80> = re.search
{noformat}
Bug: python test failures caused by error checks not filtering JAVA_TOOL_OPTIONS
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 06/May/21 20:44
Resolved: 07/May/21 16:37

In order to test some code paths in Cassandra we need to set system properties, which can be done using JAVA_TOOL_OPTIONS, when we do this some tests fail as it expects stderr to be empty; we have a function assert_stderr_clean which does the same check but filters out stuff like JAVA_TOOL_OPTIONS
Bug: ALTER TABLE: mixing counter and non-counter columns in one table 
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 29/Apr/21 21:48
Resolved: 06/May/21 12:52

{{CREATE TABLE}} does not allow mixing counter and non-counter columns in the same table. However, this can be done with {{ALTER TABLE}}:
* {{ALTER TABLE}} can add non-counter columns to a table with counter columns; 
* {{ALTER TABLE}} can add counter columns to a table with non-counter columns.

Tested in cassandra-4.0-rc1 (also in cassandra-4.0-beta2):

{code:sql}
CREATE TABLE test1 (
  id UUID,
  my_counter COUNTER,
  PRIMARY KEY ((id))
);

ALTER TABLE test1 ADD my_text TEXT;

UPDATE test1 
SET my_counter = my_counter + 10,
    my_text = 'Test 1' 
WHERE id = 5069cc15-4300-4595-ae77-381c3af5dc5e;

SELECT * FROM test1;

 id                                   | my_counter | my_text
--------------------------------------+------------+---------
 5069cc15-4300-4595-ae77-381c3af5dc5e |         10 |  Test 1
{code}
 
{code:sql}
CREATE TABLE test2 (
  id UUID,
  my_text TEXT,
  PRIMARY KEY ((id))
);

ALTER TABLE test2 ADD my_counter COUNTER;

UPDATE test2 
SET my_counter = my_counter + 20,
    my_text = 'Test 2' 
WHERE id = 5069cc15-4300-4595-ae77-381c3af5dc5e;

SELECT * FROM test2;

 id                                   | my_counter | my_text
--------------------------------------+------------+---------
 5069cc15-4300-4595-ae77-381c3af5dc5e |         20 |  Test 2
{code}
 
{code:sql}
CREATE TABLE test3 (
  id UUID,
  my_counter COUNTER,
  my_text TEXT,
  PRIMARY KEY ((id))
);

InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot mix counter and non counter columns in the same table"
{code}
Bug: Add gossip tests from CASSANDRA-16588
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 26/Apr/21 12:12
Resolved: 03/May/21 17:48

While working on CASSANDRA-16588 I had some tests that were very useful for getting the cluster gossip state into particular configurations and they even caught some oversights in the original suggestion for CASSANDRA-16588's fix.

Patch here: https://github.com/mfleming/cassandra-dtest/commit/f3eb50f33444da3ea599f2d51129b54f2024ead4
Bug: compactions/repairs hangs (backport CASSANDRA-16552)
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 28/Apr/21 15:51
Resolved: 30/Apr/21 05:37

Hi

We meet an issue during repairs (but more probably compaction issue in fact) since we upgraded from 3.11.1 to 3.11.10.

We are using reaper, but the issue doesn't seem to come from it (according to [~adejanovski@hotmail.com] ). When the problem happens, repairs driven by reaper are blocked.

Basically reaper hangs with the message "All nodes are busy or have too many pending compactions for the remaining candidate segments." and indeed one node has a lot of compaction pending tasks :

 
{code:java}
$ nodetool compactionstats
pending tasks: 95
- mt_metrics.metric_32: 95 
{code}
Errors in log are :

 
{code:java}
WARN [CompactionExecutor:12909] 2021-04-28 08:59:51,241 LeveledCompactionStrategy.java:144 - Could not acquire references for compacting SSTables [BigTableReader(path='/var/lib/cassandra/d
....
WARN [CompactionExecutor:12909] 2021-04-28 09:00:19,484 LeveledCompactionStrategy.java:144 - Could not acquire references for compacting SSTables [BigTableReader(path='/var/lib/cassandra/d
....
WARN [CompactionExecutor:12908] 2021-04-28 09:00:51,241 LeveledCompactionStrategy.java:144 - Could not acquire references for compacting SSTables [BigTableReader(path='/var/lib/cassandra/d
....
WARN [CompactionExecutor:12907] 2021-04-28 08:58:51,097 LeveledCompactionStrategy.java:144 - Could not acquire references for compacting SSTables [BigTableReader(path='/var/lib/cassandra/data/mt_metrics/metric_32-23300de089c311e882a61bd0fd209f48/md-350757-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/mt_metrics/metric_32-23300de089c311e882a61bd0fd209f48/md-350755-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/mt_metrics/metric_32-23300de089c311e882a61bd0fd209f48/md-350738-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/mt_metrics/metric_32-23300de089c311e882a61bd0fd209f48/md-350759-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/mt_metrics/metric_32-23300de089c311e882a61bd0fd209f48/md-350761-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/mt_metrics/metric_32-23300de089c311e882a61bd0fd209f48/md-350740-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/mt_metrics/metric_32-23300de089c311e882a61bd0fd209f48/md-350751-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/mt_metrics/
.... 
{code}

The error happened several times in few weeks and up to now always concerns LCS tables.

a.dejanoski mentioned me https://issues.apache.org/jira/browse/CASSANDRA-15242 but I have no trace of messages like "disk boundaries are out of date for keyspacename.tablename" or "Refreshing disk boundary cache for keyspacename.tablename".

The workaround is simple : just restart the node once it is identified. Pending compactions tasks rerun well.

We have the issue on 2 of our clusters on 3.11.10.
Does someone else met the issue ?