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

Semyon Danilov updated IGNITE-19417:
------------------------------------
    Description: 
We should implement a process of increasing a low watermark for the metastorage 
compaction. I believe it should be a scheduled task in the top component 
(IgniteImpl) because it will needed information about open cursors and 
partitions.

MetaStorage compaction low watermark should be a subject to the following rules:
1. It cannot be higher than the Partition LWM.
2. It cannot be higher than any cursor's timestamp.
3. It cannot be higher than the timestamp of any schema version for which a 
tuple exists that is serialized using this schema.
4. It may be increased as soon as new LWM doesn't contradict all of the 3 
points above.


  was:
MetaStorage compaction low watermark should be a subject to the following rules:
1. It cannot be higher than the Partition LWM.
2. It cannot be higher than any cursor's timestamp.
3. It cannot be higher than the timestamp of any schema version for which a 
tuple exists that is serialized using this schema.
4. It may be increased as soon as new LWM doesn't contradict all of the 3 
points above.



> Provide low watermark for metastorage compaction
> ------------------------------------------------
>
>                 Key: IGNITE-19417
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19417
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Semyon Danilov
>            Priority: Major
>              Labels: ignite-3
>
> We should implement a process of increasing a low watermark for the 
> metastorage compaction. I believe it should be a scheduled task in the top 
> component (IgniteImpl) because it will needed information about open cursors 
> and partitions.
> MetaStorage compaction low watermark should be a subject to the following 
> rules:
> 1. It cannot be higher than the Partition LWM.
> 2. It cannot be higher than any cursor's timestamp.
> 3. It cannot be higher than the timestamp of any schema version for which a 
> tuple exists that is serialized using this schema.
> 4. It may be increased as soon as new LWM doesn't contradict all of the 3 
> points above.



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

Reply via email to