You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by "Lo, Marcus " <ma...@citi.com> on 2021/09/28 07:32:54 UTC

WAL archive size is larger than max archive size, even after cleaning WAL archive

Hi,

We are encountering an interesting scenario, where the total WAL archive size is larger than max archive size, even after cleaning WAL archive. It happens often when we need to do a full rebalancing (e.g. removing a node from baseline). Can someone please shed some lights on it?

2021-09-23 09:06:34.062+0800 INFO [wal-file-cleaner%Prism-#87%Prism%] o.a.i.i.p.c.p.w.FileWriteAheadLogManager : Finish clean WAL archive [cleanCnt=21, currSize=54.0 GB, maxSize=20.0 GB]

We are using Ignite version: 2.10.0, with WAL segment size slighter smaller than 2GB.

Regards,
Marcus

Re: WAL archive size is larger than max archive size, even after cleaning WAL archive

Posted by ткаленко кирилл <tk...@yandex.ru>.

Hi, the problem has already been fixed, but it was not included in the latest release.
https://issues.apache.org/jira/browse/IGNITE-14952


28.09.2021, 10:33, "Lo, Marcus" <ma...@citi.com>:
> Hi,
>
> We are encountering an interesting scenario, where the total WAL archive size is larger than max archive size, even after cleaning WAL archive. It happens often when we need to do a full rebalancing (e.g. removing a node from baseline). Can someone please shed some lights on it?
>
> 2021-09-23 09:06:34.062+0800 INFO [wal-file-cleaner%Prism-#87%Prism%] o.a.i.i.p.c.p.w.FileWriteAheadLogManager : Finish clean WAL archive [cleanCnt=21, currSize=54.0 GB, maxSize=20.0 GB]
>
> We are using Ignite version: 2.10.0, with WAL segment size slighter smaller than 2GB.
>
> Regards,
>
> Marcus