[
https://issues.apache.org/jira/browse/IGNITE-10044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712436#comment-16712436
]
Semen Boikov commented on IGNITE-10044:
---------------------------------------
[~agoncharuk], I can not reproduce failures, just run them locally and on TC
and tests pass:
[https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ComputeAffinityRun&branch_IgniteTests24Java8=ignite-10044&tab=buildTypeStatusDiv]
Also these tests do not use partition loss policy, so changes made in
ignite-10044 should not impact them at all.
> 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)
