[
https://issues.apache.org/jira/browse/IGNITE-16956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin resolved IGNITE-16956.
------------------------------------------
Resolution: Won't Fix
The approach based on unique tags (light weight tracing) does not cover all
cases. I think we need to introduce common tracing framework instead.
> Tracing for rebalance logs
> --------------------------
>
> Key: IGNITE-16956
> URL: https://issues.apache.org/jira/browse/IGNITE-16956
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Gusakov
> Priority: Major
> Labels: ignite-3
>
> We need to implement a tracing of the rebalance process by the one trace id
> to simplify issues' debugging in future. For this purposes we need to:
> * create unique trace id, when rebalance triggered (update of replicas'
> number, baseline changes)
> * attach this trace id to all logs, connected with rebalance process
> (https://issues.apache.org/jira/browse/IGNITE-16955).
> The spreading of this trace id to the raft logs can be the most complex part
> of the implementation.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
