[jira] [Commented] (IGNITE-11704) Write tombstones during rebalance to get rid of deferred delete buffer

["Ignite TC Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379825#comment-17379825 ] 

Ignite TC Bot commented on IGNITE-11704:
----------------------------------------

{panel:title=Branch: [pull/9249/head] Base: [master] : Possible Blockers (9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility (Zookeeper){color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6084190]]

{color:#d04437}Platform .NET (Long Running){color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6084174]]
* exe: CacheTest.TestCacheWithExpiryPolicyOnAccess - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Basic 1{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=6084136]]
* IgniteBasicTestSuite: WALRecordTest.testAllTestWalRecordBuilderConfigured - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: WALRecordSerializationTest.testAllWalRecordsSerializedAndDeserializedSuccessfully - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6084172]]

{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6084115]]

{color:#d04437}Cache (Failover) 1{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6084144]]

{color:#d04437}Platform .NET{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6084171]]
* exe: DataStorageMetricsTest.TestDataStorageMetrics - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Thin client: PHP{color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6084193]]

{panel}
{panel:title=Branch: [pull/9249/head] Base: [master] : New Tests (3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}PDS (Indexing){color} [[tests 3|https://ci.ignite.apache.org/viewLog.html?buildId=6084165]]
* {color:#013220}IgnitePdsWithIndexingTestSuite: RenameIndexTreeTest.testNotPersistRenamingIndexRootPage - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite: RenameIndexTreeTest.testPersistRenamingIndexRootPage - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite: RenameIndexTreeTest.testRenamingIndexRootPage - PASSED{color}

{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6084197&buildTypeId=IgniteTests24Java8_RunAll]

> 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: 40m
>  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)