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

Use predicates in waitForConditionOrInterruptUntil instead of while loop for writeConcern waiting [v4.2]

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Replication

      After SERVER-43987 is backported, predicates are required with OperationContext::waitForConditionOrInterrupt(). Master currently uses a future-based API but 4.2 still uses condVar and waitForConditionOrInterrupt for writeConcern waiting. The backport of SERVER-43987 was done in a way that tried to minimize code changes. But that made the code less readable. We should make better use of the required predicates for better readability.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: