Nathan
My feedback
3 results found
-
124 votes
An error occurred while saving the comment Nathan supported this idea ·
-
20 votes
Nathan supported this idea ·
-
11 votes
Nathan supported this idea ·
We've been waiting 18 hours for support (which we are paying good money for) to reboot our cluster after a large operation caused the dirty cache fill ratio to jump to over 20% which completely CPU locked a secondary node evicting pages.
We can't scale it up ourselves, we tried and it is simply stuck and the operation failed.
It's completely ridiculous that the best they can suggest for self service is to "Test Resilience" which causes a primary failover which their UI blocks you from doing in many cases (such as the one we currently find ourselves in).
I will never recommend Atlas again until this is resolved. This suggestion has been open for nearly 5 years so I wouldn't hold my breath.