didn’t we learn in Local db part 1 that oplog is capped? …meaning that it is not guaranteed that a node outage - upon return - can get caught up.
i.e. if it has been out too long and the other oplogs have overwritten…
there is no mention of the oplog status in the question about the unhealthy node coming back online…
Hi @James_58604,
If you simulate the environment mentioned in this lab, the oplog is never going to run out of space because of one write operation. All options listed under the question is in reference to this particular case. However, I will talk to the team and see if we can make any changes to the question to make it more clear.
Yes, what you have said is true that if the oplog has been overwritten before any node could replicate the instructions then in that case it would require manual intervention and an initial sync.
Hope it helps!
Please let me know if you have any other question.
Thanks,
Shubham Ranjan
Curriculum Support Engineer
point taken - - I was looking at the quiz questions with an overall view of the mongo technology and not just the specific case… thanks for the clarification…