Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-96077

Investigate ReplSetTest API consolidation

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Repl 2024-10-28

      Currently, there are several ways to do something in ReplSetTest. We should investigate what methods provide duplicated behavior and consolidate where possible.

      For example, we have both ReplSetTest.waitForState and ReplSetTest.awaitSecondaryNodes that can be used wait for a node to become secondary. However, there's a subtle difference in reporting from the primary vs the actual node, so this behavior ends up becoming nuanced in practice. In this case, maybe we should error if a user tries to use waitForState as a means of waiting for the secondary state. The comment at the function signature says something to this effect, but we should start enforcing this behavior.

      We should file individual tickets from this investigation for specific functions.

            Assignee:
            m.maher@mongodb.com Moustafa Maher
            Reporter:
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: