You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Kovalenko (JIRA)" <ji...@apache.org> on 2018/03/02 16:16:00 UTC
[jira] [Created] (IGNITE-7873) Partition update counters and sizes
may be different if cache is using readThrough
Pavel Kovalenko created IGNITE-7873:
---------------------------------------
Summary: Partition update counters and sizes may be different if cache is using readThrough
Key: IGNITE-7873
URL: https://issues.apache.org/jira/browse/IGNITE-7873
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko
Tracking partition update counters and cache sizes may not properly work if cache is using readThrough behavior.
Read requests to such cache can increment update counters or cache sizes not on all nodes serving such cache in case if data in underlying storage is changed.
It means that update counter or cache size will be incremented only on partition where we followed such request (primary or any random node).
BackupPostProcessingClosure should use preload=false for entry. In other case it can increment update counter for read request while data is not changed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)