[ https://issues.apache.org/jira/browse/IGNITE-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802208#comment-16802208 ]
Ignite TC Bot commented on IGNITE-11536: ---------------------------------------- {panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3411091&buildTypeId=IgniteTests24Java8_RunAll] > Add information about possible long GC pause to checkpoint started message. > --------------------------------------------------------------------------- > > Key: IGNITE-11536 > URL: https://issues.apache.org/jira/browse/IGNITE-11536 > Project: Ignite > Issue Type: Improvement > Reporter: Sergey Antonov > Assignee: Sergey Antonov > Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > One of possible reasons long hold of write lock on checkpoint is GC pause. > Now you must check logs around on {{Possible too long JVM pause}} message. We > should print possible long GC pause time in {{Checkpoint started}} message, > if threshold was passed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)