You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/09/19 16:12:00 UTC

[jira] [Created] (IGNITE-6444) Validate that copyOnRead flag is configured with on-heap cache enabled

Alexey Goncharuk created IGNITE-6444:
----------------------------------------

             Summary: 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
             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)