You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Shishkov (Jira)" <ji...@apache.org> on 2022/12/15 16:56:00 UTC

[jira] [Updated] (IGNITE-18424) WAL segment rollover does not happen after walForceArchiveTimeout

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

Ilya Shishkov updated IGNITE-18424:
-----------------------------------
    Summary: WAL segment rollover does not happen after walForceArchiveTimeout  (was: Ignite does not rollover WAL segment after walForceArchiveTimeout)

> WAL segment rollover does not happen after walForceArchiveTimeout
> -----------------------------------------------------------------
>
>                 Key: IGNITE-18424
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18424
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ilya Shishkov
>            Priority: Major
>              Labels: IEP-59, ise
>
> How to reproduce:
> # Start and activate persistent cluster with such properties:
> ## {{DataStorageConfiguration#walForceArchiveTimeout > 0}}, eg. 10000 millis.
> ## {{DataRegion#cdcEnabled=true}}.
> ## {{DataStorageConfiguration#walSegmentSize=1Gb}}.
> ## {{DataStorageConfiguration#maxWalArchiveSize=20Gb}}.
> # Start data changing (put some entries continuously).
> # Rollover of WAL is not happening. You can wait some period exceeding {{walForceArchiveTimeout}} to ensure.
> # Stop loading the data.
> # Rollover happens.
> If you does not stop to load the data, rollover _will not happen until WAL segment will beсome full, i.e until to rollover by a segment size_. 
> Under low loads, filling of 1Gb segment can occur after a dozen of minutes or even after several hours, which causes a large lag of a CDC replication.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)