I have a M20-M30 cluster, and it scales up and down often. This time while scaling there was about 30-60min downtime.
Our customers had issues with accessing our service because of this.
Error example
pymongo.errors.ServerSelectionTimeoutError: No replica set members match selector "Primary()", Timeout: 5.0s
This is definitely unexpected, and likely suggests a buggy driver version or connection misconfiguration. Have you opened a support case?
(for context, vertical scaling events require a rolling replacement which does require replica set level elections but your driver should seamlessly handle these elections–and retryable writes ease this burden on the write path)
I can’t seem to be able to open a support ticket, it says support not enabled
Weird, can you see he chat icon in the lower right? that can also be a place to ask for help
Hello,
Did you manage to run autoscale via python, I’m trying it here and I’m having some difficulties, would you mind sharing how you did it.