[DOCS-6286] Make it clear that w:0 does not work sharded since 2.6 Created: 28/Sep/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Osmar Olivo | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
http://docs.mongodb.org/manual/reference/write-concern/ Due to the write API rework in 2.6, mongos does not support or propagate operations with a write concern of 0 (unacknowledged). Naturally, this hurts performance when switching from pre-2.6 or a replica set to a sharded cluster. barriebehackett jeff.yemin sam.weaverThis should probably be clearly documented in the driver documentation if not entirely disallowed.It's really easy to use w:0 against a sharded cluster and not realize it's not the same. |
| Comments |
| Comment by Education Bot [ 01/Nov/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! |
| Comment by Osmar Olivo [ 28/Sep/15 ] |
|
By disallow I meant only in the case of sharded clusters. Documenting it in the function description is probably the best approach for maintaining backwards compatibility I agree. |
| Comment by Jeffrey Yemin [ 28/Sep/15 ] |
|
Disallowing it would be a significant break in backwards compatibility. We shouldn't do that lightly. |