You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/02 13:49:00 UTC
[jira] [Commented] (IGNITE-7832) Ignite.resetLostPartitions()
resets state under race.
[ https://issues.apache.org/jira/browse/IGNITE-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942829#comment-16942829 ]
Maxim Muzafarov commented on IGNITE-7832:
-----------------------------------------
[~amashenkov]
Can we move this issue to the next release?
> Ignite.resetLostPartitions() resets state under race.
> -----------------------------------------------------
>
> Key: IGNITE-7832
> URL: https://issues.apache.org/jira/browse/IGNITE-7832
> Project: Ignite
> Issue Type: Task
> Components: cache
> Reporter: Andrey Mashenkov
> Assignee: Vitaliy Biryukov
> Priority: Critical
> Fix For: 2.8
>
>
> Assume, we have event listener that detects partition loss events and apply some actions to recover lost data.
> After recovery process finished an Ignite.resetLostPartitions() method should be called to mark all lost cache partitions as healthy.
> It is possible Ignite.resetLostPartitions() will be called during exchange, but right before a new partition loss event will be fired.
> E.g. exchange thread own GridDhtPartitionTopologyImpl write lock in detectLostPartitions() method, while user thread will wait for the lock inside Ignite.resetLostPartitions().
> So, after a new partition loss will be detected, is will be not possible to abort user action and state of just lost partition will be reset.
> For that case, we should either abort resetLostPartitions() or reset partitions state regarding topology version provided by user some how.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)