[SERVER-53182] [v3.6] Omit "versions" from {shardingState: 1} command when not running as a --shardsvr Created: 02/Dec/20  Updated: 29/Oct/23  Resolved: 02/Dec/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.6.22

Type: Improvement Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-29908 Libraries db/s/sharding and db/query/... Closed
Backwards Compatibility: Minor Change
Sprint: Sharding 2020-12-14
Participants:

 Description   

This behavior was already changed on the 4.0 and later branches with https://github.com/mongodb/mongo/commit/24e411d5cd7f64c5b4da25a351529cd1873284b8#diff-35082d6dcfe629e5c519b3883801b8cd2d7d2fa57db997ad1566e0e35c93dc99 from SERVER-29908. We'd like to do the same on the 3.6 branch to avoid having the {shardingState: 1} command response exceed the maximum BSONObj size (16MB) when sharding isn't even enabled.



 Comments   
Comment by Max Hirschhorn [ 02/Dec/20 ]

Not marking docs changes needed because https://docs.mongodb.com/v3.6/reference/command/shardingState/#behavior already describes the now-implemented behavior.

Comment by Githook User [ 02/Dec/20 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-53182 Omit "versions" from shardingState cmd when not --shardsvr.
Branch: v3.6
https://github.com/mongodb/mongo/commit/d8319b3775e9b6952c32a9c0599fce8ebb0d18c5

Generated at Thu Feb 08 05:30:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.