[
https://issues.apache.org/jira/browse/IGNITE-10044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711164#comment-16711164
]
Alexey Goncharuk commented on IGNITE-10044:
-------------------------------------------
[~sboikov], I see that {{IgniteBaselineLockPartitionOnAffinityRunTxCacheTest}}
is failing consistently in the ignite-10044 branch for some reason, while it
passes successfully in master. Can you take a look?
> LOST partition is marked as OWNING after the owner rejoins with existing
> persistent data
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-10044
> URL: https://issues.apache.org/jira/browse/IGNITE-10044
> Project: Ignite
> Issue Type: Bug
> Reporter: Stanislav Lukyanov
> Assignee: Semen Boikov
> Priority: Major
>
> When persistence is enabled LOST partition may become OWNING without a call
> to resetLostPartitions.
> If a partition is marked as LOST, and a node with that partition in
> persistence joins, the partition becomes OWNING. IgniteCache::lostPartitions
> doesn't return that partition anymore.
> Apparently, it only affects the lost partitions list, while needsRecovery
> flag stays set until resetLostPartitions is called.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
