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

Posted to issues@ignite.apache.org by "Roman Shtykh (JIRA)" <ji...@apache.org> on 2017/09/23 05:04:02 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16177565#comment-16177565 ] 

Roman Shtykh commented on IGNITE-6444:
--------------------------------------

[~agoncharuk] Alex, I was looking at the issue, and I have a question.
As I see, system caches such as _ignite-sys-cache_ are set to _copyOnRead == false_. Is it safe, considering they are off-heap?

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