[
https://issues.apache.org/jira/browse/IGNITE-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277330#comment-16277330
]
ASF GitHub Bot commented on IGNITE-6767:
----------------------------------------
Github user tonyschak closed the pull request at:
https://github.com/apache/ignite/pull/2939
> NearCache#localPeek(key, NEAR) always returns 'null' if the node, which owns
> the primary partition for the given key, left the cluster.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-6767
> URL: https://issues.apache.org/jira/browse/IGNITE-6767
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.1
> Reporter: Vyacheslav Koptilin
> Fix For: 2.4
>
> Attachments: GridCacheNearClientHitTest.java
>
>
> {{IgniteCache.localPeek(key, PeekMode.NEAR)}} always returns 'null' if the
> node, which owns the primary partition for the given key, left the cluster,
> even if {{IgniteCache.get(key)}} was called.
> How to reproduce:
> # start two server nodes.
> # create partitioned, atomic cache and populate data.
> # start client node with near cache configured.
> # perform {{IgniteCache.get(key)}} and check that
> {{IgniteCache.localPeek(key, PeekMode.NEAR)}} returns not null value.
> # stop server node which owns primary partition for the given {{key}}.
> # perform {{IgniteCache.get(key)}}.
> # after that {{IgniteCache.localPeek(key, PeekMode.NEAR)}} always returns
> null value.
> This issue was reported on the user-list:
> http://apache-ignite-users.70518.x6.nabble.com/Near-Cache-Topoolgy-change-causes-NearCache-to-always-miss-tt17539.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
