I don't there is an issue. You start two nodes with one backup, therefore
eviction never happens. You basically have a fully replicated dataset at
this point. Try to start a third node, you should start getting remove()
callbacks then.

Indexes on backups are needed for failover. If primary node fails, you
still have the data in cache as well as indexes for this data.


On Fri, Feb 2, 2018 at 4:08 AM, zbyszek <zbab...@yahoo.com> wrote:

> Hello Andrew,
> Thank you for your explanation.
> Where do you propose to use the affinity check - during query processing or
> in the store() method? If in store() - how this would solve the issue where
> first node starts long before second one and there is no callback on the
> first node  to get informed about keys migration?
> In addition, what would be the use case that would  require calling store()
> for backup keys?
> Thank you again,
> Zbyszek
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to