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

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/04 08:37: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 ]

Maxim Muzafarov updated IGNITE-6444:
------------------------------------
    Fix Version/s:     (was: 2.8)
                   2.9

> 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
>            Priority: Major
>              Labels: usability
>             Fix For: 2.9
>
>
> 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
(v8.3.4#803005)