You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Denis Magda <dm...@apache.org> on 2017/10/21 06:00:52 UTC
Fwd: Client Near Cache Configuration Lost after Cluster Node Removed
Ignite caching experts please chime in.
> Begin forwarded message:
>
> From: torjt <je...@gmail.com>
> Subject: Client Near Cache Configuration Lost after Cluster Node Removed
> Date: October 16, 2017 at 2:54:08 PM PDT
> To: user@ignite.apache.org
> Reply-To: user@ignite.apache.org
>
> Hello All,
>
> We are having an issue with Ignite client near caches being "lost" upon a
> cluster node being removed from the Ignite cluster. Furthermore, using
> version 2.1.0, we are seeing this issue when another client joins the
> topology. I built Ignite from GIT today, 10/16/17, with the latest changes,
> ver. 2.3.0-SNAPSHOT. As of version 2.3.0-SNAPSHOT, bringing clients up/down
> does not cause an active client to lose its near cache and performance is
> good. However, when we remove a node from the cluster, the client
> immediately communicates with the cluster and disregards its near cache.
> Restarting the client remedies the issue.
>
> The following is the steps to reproduce the issue:
> Apache Ignite Version:
> *SNAPSHOT#20171016-sha1:ca6662bcb4eecc62493e2e25a572ed0b982c046c*
> 1. Start 2 Ignite servers
> 2. Start client with caches configured as near-cache
> 3. Access caches
> 4. Stop node client is connected to
> 4a. Client immediately bypasses near cache and access "cluster" for cache
> miss
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Client Near Cache Configuration Lost after Cluster Node Removed
Posted by Denis Magda <dm...@apache.org>.
+ user list
> On Oct 20, 2017, at 11:00 PM, Denis Magda <dm...@apache.org> wrote:
>
> Ignite caching experts please chime in.
>
>> Begin forwarded message:
>>
>> From: torjt <je...@gmail.com>
>> Subject: Client Near Cache Configuration Lost after Cluster Node Removed
>> Date: October 16, 2017 at 2:54:08 PM PDT
>> To: user@ignite.apache.org
>> Reply-To: user@ignite.apache.org
>>
>> Hello All,
>>
>> We are having an issue with Ignite client near caches being "lost" upon a
>> cluster node being removed from the Ignite cluster. Furthermore, using
>> version 2.1.0, we are seeing this issue when another client joins the
>> topology. I built Ignite from GIT today, 10/16/17, with the latest changes,
>> ver. 2.3.0-SNAPSHOT. As of version 2.3.0-SNAPSHOT, bringing clients up/down
>> does not cause an active client to lose its near cache and performance is
>> good. However, when we remove a node from the cluster, the client
>> immediately communicates with the cluster and disregards its near cache.
>> Restarting the client remedies the issue.
>>
>> The following is the steps to reproduce the issue:
>> Apache Ignite Version:
>> *SNAPSHOT#20171016-sha1:ca6662bcb4eecc62493e2e25a572ed0b982c046c*
>> 1. Start 2 Ignite servers
>> 2. Start client with caches configured as near-cache
>> 3. Access caches
>> 4. Stop node client is connected to
>> 4a. Client immediately bypasses near cache and access "cluster" for cache
>> miss
>>
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: Client Near Cache Configuration Lost after Cluster Node Removed
Posted by Denis Magda <dm...@apache.org>.
+ user list
> On Oct 20, 2017, at 11:00 PM, Denis Magda <dm...@apache.org> wrote:
>
> Ignite caching experts please chime in.
>
>> Begin forwarded message:
>>
>> From: torjt <je...@gmail.com>
>> Subject: Client Near Cache Configuration Lost after Cluster Node Removed
>> Date: October 16, 2017 at 2:54:08 PM PDT
>> To: user@ignite.apache.org
>> Reply-To: user@ignite.apache.org
>>
>> Hello All,
>>
>> We are having an issue with Ignite client near caches being "lost" upon a
>> cluster node being removed from the Ignite cluster. Furthermore, using
>> version 2.1.0, we are seeing this issue when another client joins the
>> topology. I built Ignite from GIT today, 10/16/17, with the latest changes,
>> ver. 2.3.0-SNAPSHOT. As of version 2.3.0-SNAPSHOT, bringing clients up/down
>> does not cause an active client to lose its near cache and performance is
>> good. However, when we remove a node from the cluster, the client
>> immediately communicates with the cluster and disregards its near cache.
>> Restarting the client remedies the issue.
>>
>> The following is the steps to reproduce the issue:
>> Apache Ignite Version:
>> *SNAPSHOT#20171016-sha1:ca6662bcb4eecc62493e2e25a572ed0b982c046c*
>> 1. Start 2 Ignite servers
>> 2. Start client with caches configured as near-cache
>> 3. Access caches
>> 4. Stop node client is connected to
>> 4a. Client immediately bypasses near cache and access "cluster" for cache
>> miss
>>
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>