ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11536) Add information about possible long GC pause to checkpoint started message.
Date Tue, 19 Mar 2019 09:17:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795853#comment-16795853
] 

Ignite TC Bot commented on IGNITE-11536:
----------------------------------------

{panel:title=--&gt; Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=3344464]]
* IgniteCacheWithIndexingTestSuite: CacheTtlAtomicPartitionedSelfTest.testTimeToLiveTtl -
0,0% fails in last 397 master runs.

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3342464&amp;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)

Mime
View raw message