NCP-DB-6.10 · Question #261
What happens to the primary member in a MongoDB Server Cluster during the NDB patching process?
The correct answer is D. It is patched first and then becomes a secondary member. NDB identifies the primary member of the MongoDB Server Cluster and patches it first. NDB triggers a failover to elect a new primary member from the remaining secondary members. NDB patches the former primary member, which becomes a secondary member after the failover. NDB…
Question
What happens to the primary member in a MongoDB Server Cluster during the NDB patching process?
Options
- AIt is patched last and is restored to its original state.
- BIt becomes a read-only member during the patching process.
- CIt is skipped during the patching process to ensure no downtime.
- DIt is patched first and then becomes a secondary member.
How the community answered
(65 responses)- A3% (2)
- B3% (2)
- C2% (1)
- D92% (60)
Explanation
NDB identifies the primary member of the MongoDB Server Cluster and patches it first. NDB triggers a failover to elect a new primary member from the remaining secondary members. NDB patches the former primary member, which becomes a secondary member after the failover. NDB patches the remaining secondary members one by one. NDB verifies the patching status and the cluster health. This process ensures that the MongoDB Server Cluster always has a primary member available to handle write operations, while minimizing the downtime and the impact on the cluster performance.
Topics
Community Discussion
No community discussion yet for this question.