Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Completed
Categories Atlas
Created by Guest
Created on Apr 9, 2020

"Chaos testing" for Atlas - simulate node(s) down

The current "Test Failover" feature supports testing application/driver resiliency in case of elections. For additional testing, we want to be able to cause a node or nodes to be shut down and started up in a cluster. There should be selectivity allowing the entire node or just the mongod or mongos process to be shut down and started up.
  • Attach files
  • Guest
    May 31, 2023
    Hi Spencer, we have support now for Simulate Regional Outage in MongoDB Atlas! See https://www.mongodb.com/docs/atlas/tutorial/test-resilience/simulate-regional-outage/ for more details.
  • Guest
    May 6, 2022
    We're starting to scope out the ability to test region level outages: expect an update later this year!
  • Guest
    Sep 29, 2021
    Had customer requests for this during POC to test these scenarios.
  • Guest
    Jul 21, 2021
    Have the possibility to test a DR scenario like lost a cloud region.
  • Guest
    Oct 20, 2020
    This may also be useful for 'stuck' secondaries that need rebooting or to trigger the bouncing of a mongod, which can only be done by a Cloud TS at this time.
  • Guest
    Oct 2, 2020
    Along this line of thinking, it would be nice to add functionality to enact, specifically, the standard processes used when deploying maintenance to Atlas clusters to test that applications are resilient to more than just the election process that occurs during Atlas maintenance.