You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/04/09 14:07:00 UTC
[jira] [Updated] (IGNITE-6444) Validate that copyOnRead flag is
configured with on-heap cache enabled
[ https://issues.apache.org/jira/browse/IGNITE-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk updated IGNITE-6444:
-------------------------------------
Fix Version/s: (was: 2.5)
2.6
> Validate that copyOnRead flag is configured with on-heap cache enabled
> ----------------------------------------------------------------------
>
> Key: IGNITE-6444
> URL: https://issues.apache.org/jira/browse/IGNITE-6444
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.0
> Reporter: Alexey Goncharuk
> Assignee: Roman Shtykh
> Priority: Major
> Labels: usability
> Fix For: 2.6
>
>
> Link to the user-list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-1-0-CopyOnRead-Problem-td17009.html
> It makes sense to validate the flag and print out a warning if on-heap cache is disabled. I do not think that we should prevent node from startup because this may break existing deployments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)