Hello! I also have an issue in progress regarding WAL archive: https://issues.apache.org/jira/browse/IGNITE-12892. In this ticket I tried clarifying WAL archive size configuration, removing usage of the deprecated walHistSize property. Also, IGNITE_PDS_MAX_CHECKPOINT_MEMORY_HISTORY_SIZE is now only used when archive is managed externally and you can set maxWalArchiveSize to -1 so WAL truncation is disabled. PR is already submitted and approved https://github.com/apache/ignite/pull/8550
Regards, Semyon. 09.12.2020, 19:17, "ткаленко кирилл" <tkalkir...@yandex.ru>: > Hi, Andrey! > > Users expect DataStorageConfiguration#maxWalArchiveSize to mean that WAL > archive will not exceed this value, but it is not. > It seems that to reduce the chance of getting into a situation when we exceed > WAL archive, it will be lowed when we clean it when switching to a new > segment than at the end of the checkpoint. > After that, we can think about and make a hard limit on WAL archive, but for > this will need to solve a few more problems. > > 09.12.2020, 17:24, "Andrey Gura" <ag...@apache.org>: >> Kiriill, >> >> Issue description contains the following: >> >>> At the moment, WAL archive is cleared at the end of the checkpoint, which >>> does not seem correct and needs to be moved >> >> Could you please explain why existing behavior is not correct. It >> seems that it is not enough motivation for change. >> >> On Wed, Dec 9, 2020 at 5:05 PM vbm <bmvish...@gmail.com> wrote: >>> Hi Kirill Tkalenko, >>> >>> Is there any relation to rate of ingestion of data to ignite ? >>> >>> We had seen the issue of WAL growing infinitely recently in our K8s >>> cluster. >>> We were ingesting data at around 2Mbps. >>> In other clusters where we did not have such a fast ingestion of data, >>> this >>> issue was not observed. >>> >>> Regards, >>> Vishwas >>> >>> -- >>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
