You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Antonov (JIRA)" <ji...@apache.org> on 2019/03/20 12:03:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Sergey Antonov updated IGNITE-11536:
------------------------------------
    Description: 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.  (was: 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.)

> 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)