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

Andrey Mashenkov commented on IGNITE-17945:
-------------------------------------------

My point is "bulk loading" meaning is ambiguous without referencing to Ignite.
As you wrote, user may see the message during "bulk loading", but it is not a 
real reason. 

In general, 
before the fix some users may mistakenly think 'JVM pause'='GC pause' e.g. 
because they are far from Java world.
after the fix the same users may get confused with useless terms, which can't 
be even googled.

> 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)

Reply via email to