[
https://issues.apache.org/jira/browse/IGNITE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-941:
---------------------------------------
Summary: Need to add read-only mode for transactional cache (was: Need to
read-only mode in transactional cache)
> Need to add read-only mode for transactional cache
> --------------------------------------------------
>
> Key: IGNITE-941
> URL: https://issues.apache.org/jira/browse/IGNITE-941
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: sprint-4
> Reporter: Valentin Kulichenko
> Priority: Critical
>
> Transactional cache updates persistence store from client, but reads are done
> from the primary node. So it's valid to use transactional cache on client for
> gets only even if there is no DB access on client (which is often the case).
> This can be especially useful to utilize near cache.
> Currently you can achieve this by removing store from client and disabling
> consistency check, but it's not safe. Moreover, you can't disable the check
> only on client nodes, because in this case you won't be able to start a new
> server node if there is a client in topology.
> I suggest to:
> * Add {{readOnly}} flag on cache configuration (disabled by default).
> * If flag is switched on, updates are not allowed.
> * Consistency check should accept read-only clients w/o store configured.
> I also think that if consistency check is disabled on one of the nodes, other
> nodes should not check it (now they do).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
