[
https://issues.apache.org/jira/browse/IGNITE-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287686#comment-17287686
]
Kirill Tkalenko commented on IGNITE-13557:
------------------------------------------
[~ibessonov] I made one change, the result is suites:
https://ci.ignite.apache.org/viewLog.html?buildId=5884310&;
> Logging improvements for PDS memory restore process
> ---------------------------------------------------
>
> Key: IGNITE-13557
> URL: https://issues.apache.org/jira/browse/IGNITE-13557
> Project: Ignite
> Issue Type: Task
> Components: persistence
> Reporter: Sergey Chugunov
> Assignee: Kirill Tkalenko
> Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During partition state restore phase of restoring memory state from disk
> Ignite logs a lot of useful information on debug level but very little on
> info.
> In many situations more detailed information can be useful for identification
> of performance issues but printing info about all partitions is impractical
> as it produces too much logs.
> The following improvements are possible though:
> # To identify any imbalance between partitions and find bigger-than-average
> partitions we should gather statistics for each partition during restore
> (part size and time it took to restore it). After restore we'll print
> information about average time and top five partitions that took the most
> time to restore.
> # To make progress of restoring visible we should print short message with
> intermediate progress information periodically. This should be applied when
> restore starts taking too long time (e.g. if restore hasn't finished in 5
> minutes start printing progress each minute).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
