[
https://issues.apache.org/jira/browse/IGNITE-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948523#comment-16948523
]
Maxim Muzafarov commented on IGNITE-10760:
------------------------------------------
Moved to the next release due to inactivity. Please, feel free to move it back
if you will be able to complete the ticket by 2.8 code freeze date, December 2,
2019.
> 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 N. Gura
> Assignee: Rodion
> 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
(v8.3.4#803005)
