Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
4.4.26
-
None
-
None
-
Cluster Scalability
Description
while the documentation for setting the balancer window does explicitly instruct the operator to use 2 digit hours, since making a balancer window change is performed via an updateOne() op to the config.settings namespace, accidentally using a single digit hour for the window start can result in the balancer window being set to an undefined state.
Example, when balancer window is:
Atlas [direct: mongos] config> db.settings.find()
|
[
|
{
|
_id: 'balancer',
|
mode: 'full',
|
stopped: false,
|
activeWindow: { start: '1:00', end: '10:00' }
|
},
|
{ _id: 'chunksize', value: 64 },
|
{ _id: 'autosplit', enabled: true }
|
]
|
sh.status() shows the following:
...
|
balancer
|
{
|
'Currently enabled': 'yes',
|
'Currently running': 'no',
|
'Balancer active window is set between': '1:00 and undefined server local time',
|
'Failed balancer rounds in last 5 attempts': 0,
|
'Migration Results for the last 24 hours': 'No recent migrations'
|
}
|
...
|
somewhat related: SERVER-81311
Attachments
Issue Links
- related to
-
SERVER-81311 Setting a Balancing Window Should Not Require Customers to Write to the Config Database
-
- Backlog
-