[SERVER-1960] Tagging of mongod Created: 17/Oct/10  Updated: 29/Oct/10  Resolved: 29/Oct/10

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Hans Meiser Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

It would be useful to tag each instance of mongod.
This could be use by mongos or drivers to prefer some nodes in a replica set over others.
For example a tag could be dc1 and dc2 if the slaves of a replica set are distributed in two datacenters.
This is feature is a generalized version of SLAVE_OK with two tags SLAVE and MASTER



 Comments   
Comment by Eliot Horowitz (Inactive) [ 29/Oct/10 ]

SERVER-992

Comment by Markus Gattol [ 18/Oct/10 ]

Sounds like a good counterpart for http://jira.mongodb.org/browse/SERVER-1594 Those two would allow do make drivers less complex (routing moves entirely into mongos, also for replica sets and distributed reads) and if mongods were tagged all kinds of nifty things could be done based on that foundation.

Maybe each mongod could generate some "performance" tag based on bogmips, RAM, disk i/o, etc. and let the mongos know so the cluster would somehow know which machine is the "biggest/fastest" machine(s) in the cluster. Further down the road it might be feasible to semi-automatically spit out some suggestion for how to (re)configure the cluster for optimal performance.

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