[DOCS-12260] Edit to docs page on disabling read concern majority Created: 12/Dec/18 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Arnie Listhaus | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
DescriptionThe docs page for disabling read concern majority (https://docs.mongodb.com/v3.6/reference/read-concern-majority/#disable-read-concern-majority) mentions an impact on change streams. I believe it would be worthwhile to mention that customers should review their apps to see if they have implemented read concern majority. Also, I would add that if they either need to use change streams or RCM in their apps, that they should convert the arbiter to a data bearing node Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |