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 2019/03/15 17:13:00 UTC
[jira] [Commented] (IGNITE-11536) Add information about possible
long GC pause to checkpoint started message.
[ https://issues.apache.org/jira/browse/IGNITE-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793782#comment-16793782 ]
Ignite TC Bot commented on IGNITE-11536:
----------------------------------------
{panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC PDS 2{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3323523]]
{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3322280&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: 10m
> 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 threshhold was passed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)