You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by 7p...@guerrillamail.com on 2017/05/08 13:43:37 UTC

Eviction and Failover

Hi, 

I'm evaluating a failover scenario with Ignite 2.0, so far it works good. But i need to be sure about the exact behaviour. My questions are related to primary and backup evictions. 

1. If primary evicts an entry, how will backups be informed from it? In a sync or async manner? 
2. Or are primary and backup evictions happen independently from each other? If yes, can data sets on primary and backup become different in time? Since this can affect cache performance when primary dies.

Thanks in advance,





----
Sent using Guerrillamail.com
Block or report abuse: https://www.guerrillamail.com//abuse/?a=VFJxFy0JRLocnAv68W4ecRzCA8WC1Q%3D%3D



Re: Eviction and Failover

Posted by Nikolai Tikhonov <nt...@apache.org>.
Hi,

1. Ignite doesn't notify backups about evection entries.
2. Yes, you're right. Evictions happen independently on backups and primary
nodes. Data might be different but eventually they will be consistency. And
if you set CacheConfiguration.setReadFromBackup to false you won't get
different values. To be honest I don't understand your point about
perfomance. Could you clarify this?

On Mon, May 8, 2017 at 4:43 PM, <7p...@guerrillamail.com>
wrote:

> Hi,
>
> I'm evaluating a failover scenario with Ignite 2.0, so far it works good.
> But i need to be sure about the exact behaviour. My questions are related
> to primary and backup evictions.
>
> 1. If primary evicts an entry, how will backups be informed from it? In a
> sync or async manner?
> 2. Or are primary and backup evictions happen independently from each
> other? If yes, can data sets on primary and backup become different in
> time? Since this can affect cache performance when primary dies.
>
> Thanks in advance,
>
>
>
>
>
> ----
> Sent using Guerrillamail.com
> Block or report abuse: https://www.guerrillamail.com//abuse/?a=
> VFJxFy0JRLocnAv68W4ecRzCA8WC1Q%3D%3D
>
>
>