[
https://issues.apache.org/jira/browse/IGNITE-10207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16683044#comment-16683044
]
ASF GitHub Bot commented on IGNITE-10207:
-----------------------------------------
GitHub user dgovorukhin opened a pull request:
https://github.com/apache/ignite/pull/5360
IGNITE-10207 Fix missed loss policy checks
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10207
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5360.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5360
----
commit 162e57381f1edd3f3b3a252894fe40231c332474
Author: Dmitriy Govorukhin <dmitriy.govorukhin@...>
Date: 2018-11-09T22:09:12Z
IGNITE-10207 rework lossPolicy tests
Signed-off-by: Dmitriy Govorukhin <[email protected]>
commit 19d8d902f6ee2fb77244549a1a891a901ea2386d
Author: Dmitriy Govorukhin <dmitriy.govorukhin@...>
Date: 2018-11-11T22:16:18Z
IGNITE-10207 fix checking lost partition for many cases
Signed-off-by: Dmitriy Govorukhin <[email protected]>
----
> Missed loss policy checks
> -------------------------
>
> Key: IGNITE-10207
> URL: https://issues.apache.org/jira/browse/IGNITE-10207
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Dmitriy Govorukhin
> Assignee: Dmitriy Govorukhin
> Priority: Critical
> Fix For: 2.8
>
>
> In some cases (client reconnect, new client join, etc) PartitionLossPolicy
> may incorrectly validate operation. Return null for READ_ONLY_SAFE for loss
> partition.
> To reproduce run CacheResultIsNotNullOnPartitionLossTest (1000 times) with
> random node stop.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
