You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2026/06/03 09:58:00 UTC
[jira] [Commented] (IGNITE-27232) Fix mixed-clock calculation of possibleJvmPauseDuration in checkpoint logging
[ https://issues.apache.org/jira/browse/IGNITE-27232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18085757#comment-18085757 ]
Ignite TC Bot commented on IGNITE-27232:
----------------------------------------
{panel:title=Branch: [pull/13194/head] Base: [master] : Possible Blockers (3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI (Discovery){color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=9104409]]
* IgniteSpiDiscoverySelfTestSuite: IgniteDiscoveryMassiveNodeFailTest.testMassiveFail - Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 6{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=9104339]]
* IgniteCacheTestSuite6: CacheExchangeMergeMdcTest.testMergeStartStopRandomClientsServers - Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Snapshots 1{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=9104406]]
* IgniteSnapshotTestSuite: IgniteSnapshotRestoreFromRemoteMdcTest.testMdcAwareSnapshotFromCurrentDc[encryption=true, onlyPrimay=true] - Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/13194/head] Base: [master] : New Tests (2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Basic 1{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=9104325]]
* {color:#013220}IgniteBasicTestSuite: LongJVMPauseDetectorTest.testFullCycle - PASSED{color}
{color:#00008b}Cache 13{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=9104334]]
* {color:#013220}IgniteCacheTestSuite13: SystemViewCacheExpiryPolicyTest.testCacheViewExpiryPolicy[factory=javax.cache.configuration.FactoryBuilder$SingletonFactory@f882465, actual=SingletonFactory [expiryPlc=EternalExpiryPolicy [create=ETERNAL]]] - PASSED{color}
{panel}
[TeamCity *--> Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9104452&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9104452 rerunBuildIds=none{color}
> Fix mixed-clock calculation of possibleJvmPauseDuration in checkpoint logging
> -----------------------------------------------------------------------------
>
> Key: IGNITE-27232
> URL: https://issues.apache.org/jira/browse/IGNITE-27232
> Project: Ignite
> Issue Type: Task
> Reporter: Maksim Davydov
> Assignee: Egor Baranov
> Priority: Trivial
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Checkpointer#possibleLongJvmPauseDuration() uses System.currentTimeMillis(), while LongJVMPauseDetector switched to TimeUnit.NANOSECONDS.toMillis(System.nanoTime()) after IGNITE-21475.
> This mixes wall-clock time with monotonic time and results in misleading checkpoint logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)