From 63addc4f3d45393486cde058202d3aa465544c9e Mon Sep 17 00:00:00 2001 From: Derick Rethans Date: Tue, 11 Feb 2014 12:19:22 +0000 Subject: [PATCH] Make sure that we mention that "NEAREST" is actually random. git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@332831 c90b9560-bf6c-de11-be94-00142212c4b1 --- reference/mongo/readpreferences.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/reference/mongo/readpreferences.xml b/reference/mongo/readpreferences.xml index ea37a1b2f2..f8d38e44f1 100644 --- a/reference/mongo/readpreferences.xml +++ b/reference/mongo/readpreferences.xml @@ -18,7 +18,8 @@ Read preferences are specified with a combination of modes and tag sets. Modes determine how mongod instances are prioritized, while tag sets specify criteria - for eligible mongod instances. + for eligible mongod instances. Mongod instances are only eligible if they + are within a 15ms ping time from the client. Read Preference Modes @@ -111,9 +112,10 @@ MongoClient::RP_NEAREST - The driver reads from the nearest member of the set according to the member - selection process. Reads in the MongoClient::RP_NEAREST - mode do not consider the member's type and may read from both primaries and + The driver reads from a random member of the set + that is within the 15 ms selection treshold. + Reads in the MongoClient::RP_NEAREST mode do not + consider the member's type and may read from both primaries and secondaries.