You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2026/01/09 13:19:00 UTC
[jira] [Created] (CASSANDRA-21111) Cassandra sstable generation ID's are a signed int which might overflow
Stefan Miklosovic created CASSANDRA-21111:
---------------------------------------------
Summary: Cassandra sstable generation ID's are a signed int which might overflow
Key: CASSANDRA-21111
URL: https://issues.apache.org/jira/browse/CASSANDRA-21111
Project: Apache Cassandra
Issue Type: Bug
Reporter: Stefan Miklosovic
We need to triage this but this seems to be legit:
We have hit an issue with a cluster that where sstable generation ID’s for a peer has incremented so high that it has overflowed, which has introduced a 2nd dash into the file name. For example:
nb--2146021117-big-data.db
This caused an issue with our solution which is aimed to consolidate partition statistics in the data set. The current version of the solution does not recognise the possibility of sstable generation ID’s being a negative value - which causes it to fail.
Workaround:
Rename all sstables in the table to “reset” the generation ID.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org