[ https://issues.apache.org/jira/browse/IGNITE-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180177#comment-16180177 ]
ASF GitHub Bot commented on IGNITE-6444: ---------------------------------------- GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2744 IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache enabled. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-6444 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2744.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2744 ---- commit 6652b70e144cd4627455c69072f5665581f793ca Author: shroman <rsht...@yahoo.com> Date: 2017-09-25T03:56:56Z IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache enabled commit 3ea14c961dacf9277d23a2e72304043ed8eb2f70 Author: shroman <rsht...@yahoo.com> Date: 2017-09-26T01:58:51Z IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache enabled. commit cd5ee5b367a80d0c780eb5782eb82c85c98e2fb5 Author: shroman <rsht...@yahoo.com> Date: 2017-09-26T03:31:32Z IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache enabled. ---- > 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 > Labels: usability > Fix For: 2.3 > > > 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 (v6.4.14#64029)