[DOCS-8943] v3.0 mongos and v3.2 cluster explain command are not compatible Created: 28/Sep/16 Updated: 07/Aug/17 Resolved: 28/Sep/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 19 weeks, 6 days ago | ||||||||
| Description |
|
Some incompatibility observed include: 1. Using v3.2 shell on v3.0 mongos can cause the mongos to ignore the read preference setting. This is because the read preference setting used to be inside the explain subdocument in v3.0 and is now moved to the top level in v3.2. 2. Using v3.0 shell and v3.0 mongos with v3.2 shards to run an explain with slaveOk will result in:
|
| Comments |
| Comment by David Storch [ 29/Sep/16 ] |
|
emily.hall, if we were to do anything, it would be document the limitations in the product which result from not fixing |
| Comment by Emily Hall [ 28/Sep/16 ] |
|
Closing issue because linked Server ticket was resolved as "Won't Fix" |
| Comment by Emily Hall [ 28/Sep/16 ] |
|
Emily is taking care of the first pass on grooming this. |
| Comment by Emily Hall [ 28/Sep/16 ] |
|
david.storch - this ticket was opened to document |