StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7854540
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-10-21T19:49:33.190
FavoriteCount
0
LastActivityDate
2011-10-21T19:49:33.190
LastEditDate
LastEditorUserId
0
OwnerUserId
192101
ParentId
7853888
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
That's an acceptable way to connect to the replica set. Assuming that the named server is up, the driver connection will discover the remainder of the servers in the cluster and be able to direct queries to them when permitted, and follow the "PRIMARY" designation through failover events. It's a good idea to add other servers to this "seed list", though, so that the connection can still succeed if one of the "seed" servers happens to be down. As for distributing reads ... this behavior is in practice at the discretion of the driver. But the generally accepted semantics is: if a slaveOk read is requested, that read query will go to a SECONDARY server if one is available; only if none are available will it go to the PRIMARY. Write queries, of course, will always go to the PRIMARY. One suggestion for having the PRIMARY share some of the read load, is to randomize when you flag a query as slaveOk -- <a href="http://groups.google.com/group/mongodb-user/browse_thread/thread/458812c7b9781b4e" rel="noreferrer">see the discussion here</a> To flag a query as slaveOk in PHP, you can set this bit at several levels -- connection, database, collection, or cluster -- <a href="http://us2.php.net/manual/en/mongo.queries.php" rel="noreferrer">API details here</a> This affords several possible ways of implementing the aforementioned randomization technique -- e.g., try to make sure half the connections in your connection pool have the slaveOk bit set. Hope that helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhen to Query Replica Sets for Mongo DB
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdampier
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhen to Query Replica Sets for Mongo DB
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CONote that you should not have your arbiter in your seed list, see https://jira.mongodb.org/browse/PHP-392.
 singulars
 PostPostId
 PO
 UserUserId
 USAdam Monsen

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.