[DOCS-9157] Circular reference in replSet tags examples Created: 18/Oct/16  Updated: 30/Oct/23  Resolved: 08/Jul/19

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Luke Prochazka Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-6211 Read preference tag sets documentatio... Closed
Participants:
Days since reply: 4 years, 31 weeks, 2 days ago

 Description   

If you follow the tutorial on configure replicas set tag sets, the examples refer you to read preferences for implementation of using tags with read preferences. However, this page then makes a circular reference back to the tags tutorial (above).

There are no cited examples on either of those pages of using tags (as a string) to read preference options.

In addition, the connection string docs do appear to have an example, however the example given appears to violate the spec for the URI. For example, if multiple tags are specified of the same type, the last value is usually taken, which is exactly what is cited for multiple values.



 Comments   
Comment by Githook User [ 08/Jul/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-6211,DOCS-9157: Backport to 3.6 rs tags - read pref and write concern
Branch: v3.6
https://github.com/mongodb/docs/commit/a9f4d50599fc1a95b930fd4fd3f6e3463ce8a6aa

Comment by Githook User [ 08/Jul/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-6211,DOCS-9157: Backport to 4.0 rs tags - read pref and write concern
Branch: v4.0
https://github.com/mongodb/docs/commit/e59ed7547b891d3ce0cf812aa8af3f7801751dc2

Comment by Githook User [ 08/Jul/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-6211,DOCS-9157: rs tags - read pref and write concern
Branch: master
https://github.com/mongodb/docs/commit/467b1298a4cd1766e93f4470a16995213d2856b6

Comment by Kay Kim (Inactive) [ 24/Jun/19 ]

 per current spec

If the tag_sets list is not empty, then tag sets are tried in order until a tag set matches at least one candidate server. All candidate servers matching that tag set are eligible servers. Subsequent tag sets in the list are ignored.

 

Generated at Thu Feb 08 07:57:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.