[SERVER-3358] sharding - tagging - use for reading from secondaries Created: 01/Jul/11  Updated: 28/Sep/16  Resolved: 05/Jul/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Randolph Tan
Resolution: Done Votes: 13
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-992 replciation should be rack and data c... Closed
Documented
is documented by DOCS-9043 sharding - tagging - use for reading ... Closed
Duplicate
duplicates SERVER-4464 drivers and mongos should support 5 r... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Comments   
Comment by Randolph Tan [ 05/Jul/12 ]

Code commit:

https://github.com/mongodb/mongo/commit/83551169374ded2a86838c6b72c8415adb76b1a4

Comment by Randolph Tan [ 13/Jun/12 ]

SERVER-4464 will also implement tagging.

Comment by Grégoire Seux [ 23/Jan/12 ]

This feature is really important for me, we use a mongodb cluster in two datacenters : all 4 masters are in dc A whereas all 4 slaves are in dc B.
Reads are done from both dcs but it is, for now, impossible to specify "read from the nearest" servers.

It slows down what we can do with mongodb in production.
Is there any way to help with this feature ?

Comment by Jimmy Zhang [ 18/Oct/11 ]

This is pretty much necessary if you're running a sharded production environment and you want to segregate your reads from your primary application from other use cases (e.g. async jobs, cron jobs, manual querying, etc.). Would really appreciate it if we bump this up. Thanks!

Comment by Dattas Moonchaser [ 21/Sep/11 ]

This would be great in addition with SERVER-3329 so you could write to the primary and be able to reliably read from slaves that have the changes.

Generated at Thu Feb 08 03:02:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.