[
https://issues.apache.org/jira/browse/IGNITE-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647094#comment-17647094
]
Andrey Mashenkov edited comment on IGNITE-17945 at 12/14/22 1:05 PM:
---------------------------------------------------------------------
Maxim, I'd just say
"Possible too long JVM pause (this can happens due to long GC or internal JVM
reasons or external reasons, like OS or other)",
if you want to be more precise.
was (Author: amashenkov):
Maxim, I'd just say
"Possible too long JVM pause (this can happens due to long GC or internal JVM
reasons or external reasons, like OS or other)"
> 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: 1h
> 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)
