ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Kasnacheev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10760) Confusing message about system worker blocking
Date Wed, 26 Dec 2018 12:37:00 GMT

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

Ilya Kasnacheev commented on IGNITE-10760:
------------------------------------------

[~agura] I expect there is no user code inside of partition-exchanger, therefore blockingSectionBegin/blockingSectionEnd
should probably be introduced by Apache Ignite, either in this ticket or a new one.

> Confusing message about system worker blocking 
> -----------------------------------------------
>
>                 Key: IGNITE-10760
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10760
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.7
>            Reporter: Andrey Gura
>            Priority: Major
>              Labels: newbie
>             Fix For: 2.8
>
>
> System workers blocking monitoring message can confuse because print out worker's name
while references to this name as {{threadName}}:
> {noformat}
> [ERROR] 2018-12-18 14:58:06.811 [tcp-disco-msg-worker-#2%hermesCacheInstance%] G - Blocked
system-critical thread has been detected. This can lead to cluster-wide undefined behaviour
[threadName=partition-exchanger, blockedFor=5s]
> {noformat}
> It should be fixed in the following manner:
> - print out {{GridWorker.runner().getName()}} for {{threadName}}
> - add {{workerName}} field to the message that should contain {{GridWorker.name()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message