ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11704) Write tombstones during rebalance to get rid of deferred delete buffer
Date Fri, 04 Oct 2019 09:30:00 GMT

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

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

{panel:title=Branch: [pull/6931/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4657057&amp;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: Pavel Kovalenko
>            Priority: Major
>              Labels: rebalance
>             Fix For: 2.8
>
>          Time Spent: 10m
>  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)

Mime
View raw message