[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:
Documented
documents SERVER-21661 v3.0 mongos and v3.2 cluster explain ... Closed
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:

{
	"ok" : 0,
	"errmsg" : "Failed to parse options: { slaveOk: true }. You may need to update your shell or driver.",
	"code" : 9
}



 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 SERVER-21661. Specifically, readPreference and slaveOk on an explain may not work correctly in mixed 3.0/3.2 sharded clusters. This is a pretty obscure limitation—hence the "Won't Fix" resolution of the SERVER ticket—so it's probably fine to do nothing in the docs. I'll leave that call up to your team. Let me know if I can provide any more technical details about the issue.

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 SERVER-21661 but it is unclear what we need the documentation team to do as the Server ticket appears to have been resolved as "Won't Fix." Can you please provide some direction?

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