Kirill,
thanks for adding motivation to the issue description.
On Wed, Dec 9, 2020 at 5:24 PM Andrey Gura wrote:
>
> 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 m
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
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
t
Hi, Vishwas!
Speed of uploading data directly associated with the growth of WAL archive.
09.12.2020, 17:05, "vbm" :
> 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 i
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 W
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 observ
And this property IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE
09.12.2020, 16:28, "ткаленко кирилл" :
> And this property IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE
>
> 09.12.2020, 16:25, "ткаленко кирилл" :
>> Hi, Shiva!
>>
>> I am not aware of such tickets yet. Later I think I can deal with t
Hi, Shiva!
I am not aware of such tickets yet. Later I think I can deal with this issue.
Now you can try to increase the frequency of checkpoints, the maximum WAL
archive size and try to change the system property
IGNITE_CHECKPOINT_TRIGGER_ARCHIVE_SIZE_PERCENTAGE.
This will not solve the proble
Hi Kirill Tkalenko,
Thanks for your reply!
Do you know any known issue related to problem I'm facing ? or any ticket
related to infinite WAL growing issue which can be correlated to my issue?
Regards,
Shiva
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi, Shiva!
Yes, this ticket will only be about moving WAL archive cleanup.
I think further it is possible to solve the problem of WAL archive overflow,
but before that we need to solve several problems and deal with heuristics.
09.12.2020, 15:02, "shm" :
> Hi Kirill Tkalenko
>
> Is this ticket i
Hi Kirill Tkalenko
Is this ticket is just for moving WAL archive clean-up logic from "post
checkpoint" to FileWriteAheadLogManager#rollOver ? Or is there any plan to
change the logic which considers Archived WAL segments for clean-up ?
I'm facing a Major issue related to WAL usage and WAL usage
Hello to all!
At the moment, the archive is cleared at the end of the checkpoint, it seems it
should happen in FileWriteAheadLogManager.
I suggest moving it into the FileWriteAheadLogManager#rollOver when the
DataStorageConfiguration#maxWalArchiveSize is reached.
To do this, I created a ticket
Kirill Tkalenko created IGNITE-13831:
Summary: Move WAL archive cleanup from checkpoint to rollover
Key: IGNITE-13831
URL: https://issues.apache.org/jira/browse/IGNITE-13831
Project: Ignite
13 matches
Mail list logo
