[
https://issues.apache.org/jira/browse/IGNITE-12485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005404#comment-17005404
]
Andrey N. Gura commented on IGNITE-12485:
-----------------------------------------
[~ibessonov] [~sergey-chugunov] It seems we can just do not add
{{clusterNode.toString()}} to the event's message because event itself already
contains information about node. Reopened.
> DiscoveryEvent make event message lazy initialization
> -----------------------------------------------------
>
> Key: IGNITE-12485
> URL: https://issues.apache.org/jira/browse/IGNITE-12485
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In GridDiscoveryManager$DiscoveryWorker#recordEvent() we set to each event
> message: "msg " + clusterNode
> Invocation toString() on ClusterNode's inheritor could be expensive.
> I think event message could be lazy generated from event type and cluster
> node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
