[jira] [Comment Edited] (IGNITE-13265) Historical iterator for atomic group should transfer few more rows than required

["Alexey Scherbakov (Jira)" <ji...@apache.org>]

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

Alexey Scherbakov edited comment on IGNITE-13265 at 8/24/20, 11:11 AM:
-----------------------------------------------------------------------

[~v.pyatkov]

Added a new comment.
1. What will happen if you try to rebalance from non reserved segment ? It can be deleted by archiver I assume causing node failure.
2. I don't understand second sentence.


was (Author: ascherbakov):
[~v.pyatkov]

Added a new comment.
1. What will happen if you try to rebalance from non reserved segment ? It can be deleted by archiver I assume causing node failure.
2. I don't understand second part.

> Historical iterator for atomic group should transfer few more rows than required
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-13265
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13265
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> On a historical rebalance some updates move from one node to another wherein this update may have various order in nodes. Reordering can happen in smell interval, but it cannot avoid at all in current implementation atomic protocol.
> This mean we will reduce a probably of loosing update if we make a margin from initial counter for the historical iterator on atomic cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)