You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2022/12/14 12:33:00 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17647073#comment-17647073 ]
Evgeny Stanilovsky edited comment on IGNITE-17945 at 12/14/22 12:32 PM:
------------------------------------------------------------------------
[~timonin.maksim] i think that logs are the part of API because they can be parsed using regexps and so on ...
1. what additional information you will give for customer if *or other JVM internal* *pauses* will be additionally appended ?
2. bulk loading, also if it present in docs, is just a non informative words, i don`t know who approves such a doc, but just think as a customer - what this words mean ???
3. I also don`t know about hardware freezes, i think you talking about virtualization pauses, if it so - they also can`t be mention in this context without additional environment check.
was (Author: zstan):
[~timonin.maksim] i think that logs are the part of API because they can be parsed using regexps and so on ...
1. what additional information you will give for customer if *or other JVM internal* *pauses* will be additionally appended ?
2. bulk loading, also if it present in docs, is just a non informative words, i don`t kwon who approves such a doc, but just think as a customer - what this words mean ???
3. I also don`t know about hardware freezes, i think you talking about virtualization pauses, if it so - they also can`t be mention in this context without additional environment check.
> 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: 40m
> 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)