[CASSANDRA-16050] Handle difference in timestamp precision between java8 and java11 in LogFIle.java

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.22, 3.11.8, 4.0, 4.0-beta2
• Component/s: Local/SSTable, Local/Startup and Shutdown
• Bug Category: Degradation - Other Exception
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: Code Inspection
• Platform: All
• Since Version: 3.0.0

Source Control Link

https://github.com/apache/cassandra/commit/c89f3df91139deee6fe78cc73a2ff0514c8af721

Test and Documentation Plan

new test, cci runs

• Assignee: Marcus Eriksson
• Reporter: Marcus Eriksson

Authors

Marcus Eriksson

Reviewers

David Capwell

• Created: 14/Aug/20 15:02
• Updated: 03/Jan/21 17:02
• Resolved: 19/Aug/20 22:28

Description

https://bugs.openjdk.java.net/browse/JDK-8177809 made File.lastModified include milliseconds while java8 always has them as 000.

This causes problems in LogFile.java where we compare the timestamps with what we have in the logfile: LogFile.java. This means that we can throw errors when changing between java11 and 8