ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: copyOnRead
Date Wed, 05 Oct 2016 06:08:05 GMT

On client you will always get the copy, because it's going through network.
Obviously, you can't get a reference for an object which is stored on
another node.

On server the behavior depends on copyOnRead configuration parameter. If
it's true (default), you will still get a copy. If it's false, you'll get a
reference. However, it's a VERY bad practice to mutate this instance. First
of all, it will update it on only one node which will make your replicated
cache inconsistent. Second of all, this instance can be accessed by some
other thread at the same time (e.g., for serialization), which can cause
unexpected results and heavy to debug bugs.

Basically, setting copyOnRead=true is useful mainly for read-only scenarios.


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/copyOnRead-tp8097p8098.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message