[
https://issues.apache.org/jira/browse/IGNITE-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379945#comment-17379945
]
Pavel Tupitsyn edited comment on IGNITE-11704 at 7/13/21, 2:59 PM:
-------------------------------------------------------------------
TC run above is for https://github.com/apache/ignite/pull/9249: "IGNITE-11704
Add PARTITION_META_PAGE_DELTA_RECORD_V4 WALRecord type placeholder"
Merged to master: 97edc893d5c6bcd458364746c5624a0bf9d1ae81
was (Author: ptupitsyn):
TC run above is for https://github.com/apache/ignite/pull/9249: "IGNITE-11704
Add PARTITION_META_PAGE_DELTA_RECORD_V4 WALRecord type placeholder"
> Write tombstones during rebalance to get rid of deferred delete buffer
> ----------------------------------------------------------------------
>
> Key: IGNITE-11704
> URL: https://issues.apache.org/jira/browse/IGNITE-11704
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Assignee: Alexey Scherbakov
> Priority: Major
> Labels: rebalance
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently Ignite relies on deferred delete buffer in order to handle
> write-remove conflicts during rebalance. Given the limit size of the buffer,
> this approach is fundamentally flawed, especially in case when persistence is
> enabled.
> I suggest to extend the logic of data storage to be able to store key
> tombstones - to keep version for deleted entries. The tombstones will be
> stored when rebalance is in progress and should be cleaned up when rebalance
> is completed.
> Later this approach may be used to implement fast partition rebalance based
> on merkle trees (in this case, tombstones should be written on an incomplete
> baseline).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
