.hazelcast-client-legacy.3.6-EA3.source-code.hazelcast-client-config-3.1.xsd Maven / Gradle / Ivy
If true, client will route the key based operations to owner of the key at
the best effort.
Note that it uses a cached version of
com.hazelcast.core.PartitionService#getPartitions() and doesn't
guarantee that the operation will always be executed on the
owner. The cached table is updated every
second.
If true, client will redo the operations that were executing on the server
and client lost
the connection. This can be because of network, or simply
because the member died.
However it is not
clear
whether the application is performed or not. For
idempotent operations this is harmless, but for
non
idempotent ones retrying
can cause to undesirable effects. Note that the redo can perform on any
member.
If false, the operation will throw a RuntimeException that is wrapping a
java.io.IOException.
Limit for the Pool size that is used to pool the connections to the members.