[SERVER-71805] Display Cluster Default Values for Configurable Sharding Options Created: 02/Dec/22 Updated: 26/May/23 Resolved: 26/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Matt Panton | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Assigned Teams: |
Sharding EMEA
|
| Participants: | |
| Story Points: | 3 |
| Description |
|
Currently in MongoDB if a customer has not explicitly set a value for a configurable option it's possible that they are unable to view the cluster's (MongoDB's) default value. For example when a customer is attempting to find the cluster maxChunkSize setting and runs the following commands via mongosh and the customer has not explicitly set a default maxChunkSize for the cluster the findOne query will return null as shown in the attached image. Requested Improvement: Provide a method to display the cluster's default values for sharding options so that customers do not have to find the default value for the given option in the documentation.
|
| Comments |
| Comment by Matt Panton [ 22/Dec/22 ] |
|
sergi.mateo-bellido@mongodb.com & tommaso.tocci@mongodb.com - updated the description and ticket name |
| Comment by Sergi Mateo Bellido [ 22/Dec/22 ] |
|
The original proposal is not feasible. However, we can implement a new command to retrieve current global balancing settings. |