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:24:00 UTC
[jira] [Updated] (CASSANDRA-21111) Cassandra sstable generation ID's are a signed int which might overflow
[ https://issues.apache.org/jira/browse/CASSANDRA-21111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Miklosovic updated CASSANDRA-21111:
------------------------------------------
Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear Impact(13164)
Complexity: Normal
Component/s: Local/SSTable
Discovered By: User Report
Fix Version/s: 4.0.x
4.1.x
5.0.x
5.x
Severity: Normal
Status: Open (was: Triage Needed)
> 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
> Components: Local/SSTable
> Reporter: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> 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