Colisan
(NV)
2
I caught the db mid-scaling this afternoon and managed to quickly test an hypothesis :
When calling the Admin API route to check
https://cloud.mongodb.com/api/atlas/v2/groups/{groupId}/clusters/{clusterName}/status
it returns
{"changeStatus":"APPLIED"}
despite the Atlas UI displaying, at the exact same time
“We are deploying your changes: 4 of 6 servers complete (current action: waiting for 2 servers to be healthy)”
…
This was very promising, but a(t)las does not seems like an option 