Awaitable isMaster returns an error on reconfigs that change the SplitHorizon

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.4
    • Affects Version/s: 4.3 Required
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2020-01-27, Repl 2020-02-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Consider the scenario:
      1. A client sends an isMaster request to the server over a specific horizon h.
      2. A reconfig happens, making horizon h no longer valid.
      3a. In the non-exhaust case, the next isMaster request will fail to find the host.
      3b. In the exhaust case, the connection will still be live because the connection is still open.

      We will respond with an error to all waiting isMasters for reconfigs that change the horizon. This terminates the exhaust stream, when exhaust is used.

            Assignee:
            Jason Chan
            Reporter:
            Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: