You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Julia Bakulina (Jira)" <ji...@apache.org> on 2022/12/13 09:14:00 UTC

[jira] [Updated] (IGNITE-17945) Change message in case watchdog thread observes freeze

     [ https://issues.apache.org/jira/browse/IGNITE-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julia Bakulina updated IGNITE-17945:
------------------------------------
    Description: 
In Long JVM pause detector we warn user that the thread wasn't alive for a threshold

Possible too long JVM pause: 500+ milliseconds.

But it is often treated as a GC pause.

We can change that warning to 
Possible too long JVM pause: 500+ milliseconds. (GC pause or hardware temporary freeze)

To enlist possible reasons behind that behaviour

  was:
In Long JVM pause detector we warn user that the thread wasn't alive for a treshold

Possible too long JVM pause: 500+ milliseconds.

But it is often threated as a GC pause.

We can change that warning to  
Possible too long JVM pause: 500+ milliseconds. (GC pause or hardware temporary freeze)

to enlist possible reasons behind that behaivour


> Change message in case watchdog thread observes freeze
> ------------------------------------------------------
>
>                 Key: IGNITE-17945
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17945
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Dmitry Pavlov
>            Assignee: Julia Bakulina
>            Priority: Minor
>              Labels: ise, newbie
>             Fix For: 2.15
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In Long JVM pause detector we warn user that the thread wasn't alive for a threshold
> Possible too long JVM pause: 500+ milliseconds.
> But it is often treated as a GC pause.
> We can change that warning to 
> Possible too long JVM pause: 500+ milliseconds. (GC pause or hardware temporary freeze)
> To enlist possible reasons behind that behaviour



--
This message was sent by Atlassian Jira
(v8.20.10#820010)