You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Gusakov (Jira)" <ji...@apache.org> on 2022/05/11 14:47:00 UTC

[jira] [Created] (IGNITE-16955) Improve logging of rebalance process

Kirill Gusakov created IGNITE-16955:
---------------------------------------

             Summary: Improve logging of rebalance process
                 Key: IGNITE-16955
                 URL: https://issues.apache.org/jira/browse/IGNITE-16955
             Project: Ignite
          Issue Type: Task
            Reporter: Kirill Gusakov


We must improve logging of rebalance logic with the following points:
 - log triggers of rebalance (change of number of replicas at the moment)
 - log receiving of changes on pending/stable keys
 - log start/stop raft nodes with the info about the reason
 - log the result of multi-invoke call (we can use `yield` to detect which branch was executed)
 - log the call of changePeersAsync on the client side
 - log the real error of the call above, if error occurred (we need to change the error reporting of sendWithRetry method to support this point)
 - check if needed extensions of raft logs for changes in raft group configuration
 - log the progress of raft replication during rebalance (it can be tricky enough, due to the fact, that replicator has no information about the reason of replication)
 - logging for onLeaderElected/onNewPeersConfigurationApplied/onReconfigurationError

All logs should contains the most detailed context:
 * table
 * partition
 * metastorage keys' values (old/new)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)