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

$changeNotification cursor hangs when sent to mongos

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.11
    • Affects Version/s: None
    • Component/s: Aggregation Framework
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Hide

      Run an aggregate with a $changeNotification stage on a mongos (shards must be replica sets)

      Show
      Run an aggregate with a $changeNotification stage on a mongos (shards must be replica sets)
    • Repl 2017-07-31
    • 0

      In order to work correctly, the merging logic on mongos needs to know that a cursor is tailable. An aggregation with a $changeNotification is tailable, but doesn't communicate that information, so the merging logic mistakenly hangs, repeatedly asking for the next document, since the cursor id is never set to 0.

            Assignee:
            charlie.swanson@mongodb.com Charlie Swanson
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: