[jira] [Commented] (IGNITE-10067) Tracking progress of index building

["Stanislav Lukyanov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-10067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136347#comment-17136347 ] 

Stanislav Lukyanov commented on IGNITE-10067:
---------------------------------------------

This seems to be at least partially solved by IGNITE-11512. I assume the "getIndexBuildCountPartitionsLeft" metric added there is a good enough MVP. I'm closing this issue as duplicate, will create new ones if we need to enhance the metrics.

> Tracking progress of index building
> -----------------------------------
>
>                 Key: IGNITE-10067
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10067
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Stanislav Lukyanov
>            Priority: Major
>
> When a new index is being created or indexes are being rebuilt in case a node is restarted without index.bin, the performance of queries is low until the index is ready. It would be good to track the process of indexing to have an approximate completion time.
> Currently we only have "started" and "finished" messages in the logs for each index.
> It would be good to also know
> - All indexes to be built
> - Number (+ percentage?) of processed entries (or pages, if it's hard to update progress for each entry)
> - Number (+ percentage?) of entries left 
> It seems reasonable to start collecting this data and just print it in the logs for now. `metricsLogFrequency` could be reused as the frequency of logging. After community has some experience with using this, this metrics could be exposed via Java API/JMX/etc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)