ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vyacheslav Koptilin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6767) NearCache#localPeek(key, NEAR) always returns 'null' if the node, which owns the primary partition for the given key, left the cluster.
Date Thu, 26 Oct 2017 16:45:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vyacheslav Koptilin updated IGNITE-6767:
----------------------------------------
    Description: 
{{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 or 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

  was:
{{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 or 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 in the user-list: http://apache-ignite-users.70518.x6.nabble.com/Near-Cache-Topoolgy-change-causes-NearCache-to-always-miss-tt17539.html


> 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
>      Security Level: Public(Viewable by anyone) 
>          Components: cache
>    Affects Versions: 2.1
>            Reporter: Vyacheslav Koptilin
>
> {{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 or 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)

Mime
View raw message