[
https://issues.apache.org/jira/browse/IGNITE-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264086#comment-17264086
]
Vyacheslav Koptilin commented on IGNITE-13818:
----------------------------------------------
Hello [~makedonskaya],
In general, the patch looks good to me. However, it seems to me, the log
message can be excessive in case a cluster contains a big number of alive
nodes. Perhaps, we can stick with the following attributes only: id,
consistentId, clientMode, ignite version.
Please correct Jira summary - extended log messages are printed for NODE_LEFT
events too.
> Add extended logging topology for node start
> --------------------------------------------
>
> Key: IGNITE-13818
> URL: https://issues.apache.org/jira/browse/IGNITE-13818
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maria Makedonskaya
> Assignee: Maria Makedonskaya
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> At start of the node write topology - the number of server and client nodes,
> I would like to expand the list of nodes (information about each node: order,
> id, host, ip), this will help in the case when the logs are only from one
> node, and when there are logs from all nodes it will speed up the search for
> coordinator or find the problem node id which was in the transaction
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
