[
https://issues.apache.org/jira/browse/OAK-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877356#comment-13877356
]
Thomas Mueller commented on OAK-759:
------------------------------------
Revision 1559951: now, the read preference and write concern of all cluster
nodes can be changed at runtime, by updating the "clusterNodes" collection. To
do that, set the property "readWriteMode" to the new mode, for example
"read:nearest, write:majority". Changed to this field are picked up by the
cluster nodes every minute (as part of the cluster id lease renewal).
This should allow testing with reading from a secondary, but also help to find
out what is the impact of using more strict write concerns. At production, it
should allow to change the read/write mode without having to restart the
process.
> MongoMK: read from a secondary member when possible
> ---------------------------------------------------
>
> Key: OAK-759
> URL: https://issues.apache.org/jira/browse/OAK-759
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 0.15
>
>
> Currently, the MongoMK needs to always read from the MongoDB primary in a
> replica set. To improve read performance, reads should be distributed to all
> members in a replica set.
> One possible solution is: if old data is read, then reading from any member
> is allowed (see also MongoDB ReadPreference).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
