Read and Write access to Master Cluster

70 views
Skip to first unread message

hyndavi Marella

unread,
Jul 26, 2016, 6:14:32 PM7/26/16
to mongodb-user, hmar...@cisco.com

How to make sure that we read and write into the master cluster, what configuration settings need to be done


In order to avoid concurrency ,one possibility is to read and write to the master cluster of our hosted mongo DB .


We are little un aware of the setting s to be done for this issue .


Would be great if you could please  help

William Hagan

unread,
Jul 27, 2016, 11:10:27 AM7/27/16
to mongodb-user, hmar...@cisco.com
Hi. Have you considered tag sets?

hyndavi Marella

unread,
Jul 30, 2016, 1:17:21 AM7/30/16
to mongodb-user, hmar...@cisco.com

No .I am  unaware of the tag sets .Could you please let me know the purpose of the tag sets ?

Please let me know !!

William Hagan

unread,
Jul 30, 2016, 1:11:30 PM7/30/16
to mongodb-user
With tagging, one can direct reads and writes to designated servers.

Check out these URLs:

https://docs.mongodb.com/manual/core/tag-aware-sharding/

https://docs.mongodb.com/manual/tutorial/configure-replica-set-tag-sets/

Cheers.

Pooja Gupta

unread,
Aug 3, 2016, 3:15:11 AM8/3/16
to mongodb-user, hmar...@cisco.com

Hi Hyndavi,

By master cluster, do you mean Master Slave Replication?

As the master-slave replication has been deprecated and replaced by Replica sets since version 3.2.
In a Replica set, the primary node receives all read and write operations by default. However , you can specify the Read Preference to route read operations within members of replica set.

Could you please provide the following information:

  • MongoDB specific version
  • MongoDB deployment topology i.e. standalone, replica set, or sharded cluster

Regards,

Pooja

hyndavi Marella

unread,
Aug 9, 2016, 3:21:44 AM8/9/16
to mongodb-user, hmar...@cisco.com
MongoDB version : 2.1
we are deploying through replica sets within kubernetes open stack environment !!

Pooja Gupta

unread,
Aug 26, 2016, 12:04:26 AM8/26/16
to mongodb-user, hmar...@cisco.com

Hi Hyndavi,

Version 2.1 seems to be a implausible version as MongoDB 2.1 was an unstable server release from 2012. So I am afraid that this may not be a right version.

Please confirm your MongoDB server version by issuing db.version() command on your mongo shell.

we are deploying through replica sets within kubernetes open stack environment !!

It would also be of great help in understanding your exact problem, if you could provide more details about the specific issue you are facing.

Regards,
Pooja

Reply all
Reply to author
Forward
0 new messages