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

SetState::drop() doesn't cancel outstanding promises unless the global RSMM is shutdown

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Internal Code
    • Labels:
      None
    • Sprint:
      Service Arch 2019-10-21

      Description

      SetState::drop() reset's the current scan, then calls notify(true), but that doesn't actually do the work of failing promises in _waiters. Or rather, it only does that work assuming the rsm manager is shutdown. Instead it should check for if that particular RSM is removed

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: