You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2020/10/08 08:45:00 UTC

[jira] [Updated] (IGNITE-13557) Logging improvements for PDS memory restore process

     [ https://issues.apache.org/jira/browse/IGNITE-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Chugunov updated IGNITE-13557:
-------------------------------------
    Ignite Flags: Docs Required,Release Notes Required  (was: Release Notes Required)

> 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
>            Priority: Major
>             Fix For: 2.10
>
>
> 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)