[
https://issues.apache.org/jira/browse/CASSANDRA-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346504#comment-16346504
]
Sam Tunnicliffe commented on CASSANDRA-14092:
---------------------------------------------
{quote}Would you have an easy repro for this?
{quote}
Sure:
* On an unpatched version (I used 3.0), insert a row with a big enough TTL
* Query & see that the data is not returned.
* Apply the patch & restart
* Query & see that the row now appears
* Run nodetool compact on the table
* Query & the row has gone again
If you do *only* these steps on a clean node, then the compaction will result
in 0 SSTables for the table. A more normal workflow of inserting rows then
flushing until an automatic compaction is triggered also has the same effect,
but of course doesn't remove any data without the overflowed expiry.
> Max ttl of 20 years will overflow localDeletionTime
> ---------------------------------------------------
>
> Key: CASSANDRA-14092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14092
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Priority: Blocker
> Fix For: 2.1.20, 2.2.12, 3.0.16, 3.11.2
>
>
> CASSANDRA-4771 added a max value of 20 years for ttl to protect against [year
> 2038 overflow bug|https://en.wikipedia.org/wiki/Year_2038_problem] for
> {{localDeletionTime}}.
> It turns out that next year the {{localDeletionTime}} will start overflowing
> with the maximum ttl of 20 years ({{System.currentTimeMillis() + ttl(20
> years) > Integer.MAX_VALUE}}), so we should remove this limitation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
