Ability to schedule "Hedged read" Turn on/off
Customer experienced read latency during maintenance after sharding.
Our guidance is to turn on "Hedged read" option.
So the customer need to turn on/off "Hedged read" before/after maintenance, because turning on "hedged read" increase CPU usage that means server cost increasing.
Currently "hedged read" on/off can be done by technical support from MongoDB but this feature is needed for operational efficiency and reducing human error.
Minyoung, I appreciate your posting on this.
This idea is very useful and important feature to ensure our service availability.
I hope that this feature will be applied to MongoDB Atals.