You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "shivakumar (Jira)" <ji...@apache.org> on 2021/03/05 10:46:00 UTC

[jira] [Comment Edited] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive

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

shivakumar edited comment on IGNITE-13912 at 3/5/21, 10:45 AM:
---------------------------------------------------------------

Hi [~ktkalenko@gridgain.com]

I do not have much idea on Ignite source code, I am new to Ignite code, I will try to understand the code to debug the issue from my side, could you please give any reference to the unit test scenario of reserving a WAL segment by PME or releasing an unwanted WAL segment.

If you can share any links which explain the design of WAL segment cleanup and WAL segment reservation for PME would be helpful in understanding the code.

Is it ok, If the reproducer launches 3 instances of Ignite nodes on a windows machine and starts ingesting data to reproduce the issue? 

Thanks,

Shiva

 


was (Author: shm):
Hi [~ktkalenko@gridgain.com]

I do not have much idea on Ignite source code, I am new to Ignite code, I will try to understand the code, could you please give any reference to the unit test scenario of reserving a WAL segment by PME or releasing an unwanted WAL segment.

If you can share any links which explain the design of WAL segment cleanup and WAL segment reservation for PME would be helpful in understanding the code.

Is it ok, If the reproducer launches 3 instances of Ignite nodes on a windows machine and starts ingesting data to reproduce the issue? 

Thanks,

Shiva

 

> Incorrect calculation of WAL segments that should be deleted from WAL archive
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-13912
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13912
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Critical
>             Fix For: 2.10
>
>         Attachments: config.properties, ignite-config, reproducer.zip, server1-full-wal-checkpoint.log, wal-checkpoint-logs, wal_dir_contents, wal_grows_from_peak.PNG, wal_issue_reproduced.PNG, wal_usage.PNG, wal_usage_dec12.PNG, wal_usage_dec22nd_binary.PNG
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Now there is an incorrect calculation of WAL segments that should be deleted from WAL archive. Since we delete only those segments whose total size should not exceed *DataStorageConfiguration#maxWalArchiveSize * IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to  DataStorageConfiguration#maxWalArchiveSize * IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of *DataStorageConfiguration#maxWalArchiveSize* occurs.



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