[
https://issues.apache.org/jira/browse/IGNITE-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647079#comment-17647079
]
Maksim Timonin commented on IGNITE-17945:
-----------------------------------------
[~zstan] [~amashenkov]
Thanks for your comments! I've reverted the commit.
The idea was to notify user that there are more options than only GC pauses.
Maybe it's better to change the base message "Possible too long JVM pause",
because it might be misleading due to options could be outside the JVM.
Let's then discuss this message more carefully on devlist.
> 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)
