[
https://issues.apache.org/jira/browse/CASSANDRA-19448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876884#comment-17876884
]
Maxwell Guo commented on CASSANDRA-19448:
-----------------------------------------
Looking into the latest updated test results:
In addition to the errors I mentioned above, for the trunk branch，there some
failures:
* 4.0
** (j8) org.apache.cassandra.tools.TopPartitionsTest #
testServiceTopPartitionsSingleTable , BUT it seems that the failure has been
fixed [CASSANDRA-17455|https://issues.apache.org/jira/browse/CASSANDRA-17455]
* 4.1
** (j11) org.apache.cassandra.distributed.test.GossipTest #
nodeDownDuringMove: see
[CASSANDRA-15239|https://issues.apache.org/jira/browse/CASSANDRA-15239]
* trunk :
**
(j11)org.apache.cassandra.simulator.test.ShortPaxosSimulationTes#simulationTest,seems
to be fixed in CASSANDRA-17769
**
(j17)org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest#testEndpointVerificationEnabledIpNotInSAN-cassandra.testtag_IS_UNDEFINED
see [CASSANDRA-19281|https://issues.apache.org/jira/browse/CASSANDRA-19281]
** (j17) for in-jvm-dtest , there are many ": java.lang.OutOfMemoryError" but
seems has no relation to my patch
** (j17) org.apache.cassandra.io.sstable.VerifyTest-oa_jdk17 #
testMutateRepair see
[CASSANDRA-18919|https://issues.apache.org/jira/browse/CASSANDRA-18919]but it
is for java11
it seems that these failures has nothing to do with my patch.
> CommitlogArchiver only has granularity to seconds for restore_point_in_time
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-19448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19448
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Commit Log
> Reporter: Jeremy Hanna
> Assignee: Maxwell Guo
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Commitlog archiver allows users to backup commitlog files for the purpose of
> doing point in time restores. The [configuration
> file|https://github.com/apache/cassandra/blob/trunk/conf/commitlog_archiving.properties]
> gives an example of down to the seconds granularity but then asks what
> whether the timestamps are microseconds or milliseconds - defaulting to
> microseconds. Because the [CommitLogArchiver uses a second based date
> format|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/commitlog/CommitLogArchiver.java#L52],
> if a user specifies to restore at something at a lower granularity like
> milliseconds or microseconds, that means that the it will truncate everything
> after the second and restore to that second. So say you specify a
> restore_point_in_time like this:
> restore_point_in_time=2024:01:18 17:01:01.623392
> it will silently truncate everything after the 01 seconds. So effectively to
> the user, it is missing updates between 01 and 01.623392.
> This appears to be a bug in the intent. We should allow users to specify
> down to the millisecond or even microsecond level. If we allow them to
> specify down to microseconds for the restore point in time, then it may
> internally need to change from a long.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
