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.
We’ve upgraded our feedback system to better capture, track, and act on your feedback. Here’s what you need to know:
|
What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. |
To prevent an outage |
|
What would you like to see happen? Describe the desired outcome or enhancement. |
Ops-manager should not allow or should throw error stating that you cannot shutdown two replica set members of same shard. |
|
Why is this important to you or your team? Explain how the request adds value or solves a business need. |
Many people who knows basic knowledge on Mongodb should be able to manage cluster if this feature is enabled . |
What steps, if any, are you taking today to manage this problem? |
Preparing confluence pages , giving technical sessions. |
Hi Manjunath Thanks we do acknowledge the need for a guardrails at the Replica set level to avoid production outages !!
Here are few clarifying questions !!
1. DO you expect this guardrail only in the UI, or also when calling the Ops Manager API.
2. Is the assumption correct this guardrails should be bypassed during mass cluster updates ??