[
https://issues.apache.org/jira/browse/IGNITE-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-7086:
-------------------------------------
Description:
Ignite Replicated cache with CacheStore and ReadThrough=true and
ReadFromBackup=true works in unexpected way from user perspective.
On backup node, get operation will always go to the primary node regardless of
ReadFromBackup=true and ReadThrough=true when entry doesn't exists in local map.
So, Replicated cache works like a Partitioned with no backups.
was:
Ignite Replicated cache with CacheStore and Read-through=true and
ReadFromBackup=true works in unexpected way from user perspective.
Get operation on backup will go to the primary node regardless of
ReadFromBackup=true and Read-through=true when entry doesn't exists in local
map.
So, Replicated cache works like a Partitioned with no backups.
> Backups are not updated when ReadFromBackup=true and ReadThrough happens.
> -------------------------------------------------------------------------
>
> Key: IGNITE-7086
> URL: https://issues.apache.org/jira/browse/IGNITE-7086
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Andrew Mashenkov
> Fix For: 2.4
>
>
> Ignite Replicated cache with CacheStore and ReadThrough=true and
> ReadFromBackup=true works in unexpected way from user perspective.
> On backup node, get operation will always go to the primary node regardless
> of ReadFromBackup=true and ReadThrough=true when entry doesn't exists in
> local map.
> So, Replicated cache works like a Partitioned with no backups.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
