[
https://issues.apache.org/jira/browse/IGNITE-27008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-27008:
-----------------------------------
Description:
* Replace debug "{{{}Index build error:{}}}" log message with info message that
will also explain the reason.
* Explicitly state if index build action has been started as an attempt of a
disaster recovery of an AVAILABLE index. Such a situation shouldn't normally
occur. Add as much info as possible.
* When operation is completed we need to print the stats:
** Time it took.
** Maybe time of individual phases.
** Number of rows we indexed.
** Number of raft service calls.
** Number of resolved write intents.
** etc. Let's be creative.
was:
* Replace debug "{{{}Index build error:{}}}" log message with info message that
will also explain the reason.
* Explicitly state if index build action has been started as an attempt of a
disaster recovery of an AVAILABLE index. Such a situation shouldn't normally
occur. Add as much info as possible.
> Improve index build log
> -----------------------
>
> Key: IGNITE-27008
> URL: https://issues.apache.org/jira/browse/IGNITE-27008
> Project: Ignite
> Issue Type: Improvement
> Components: secondary indexes ai3
> Reporter: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
>
> * Replace debug "{{{}Index build error:{}}}" log message with info message
> that will also explain the reason.
> * Explicitly state if index build action has been started as an attempt of a
> disaster recovery of an AVAILABLE index. Such a situation shouldn't normally
> occur. Add as much info as possible.
> * When operation is completed we need to print the stats:
> ** Time it took.
> ** Maybe time of individual phases.
> ** Number of rows we indexed.
> ** Number of raft service calls.
> ** Number of resolved write intents.
> ** etc. Let's be creative.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
