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

Investigate if GetMoreRequest must include readConcern for tailable cursors

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Querying, Sharding
    • None
    • Query
    • ALL
    • 0

    Description

      The scenario that fails is described in BF-6485,
      the core symptom is that the getMore sent to a secondary returns operation time that is less than the afterClusterTime set in the client request.
      The reason of this is mongos parses the getMore cmdObj into the GetMoreRequest which does not include readConcern and therefore can not satisfy the request to wait.

      the cursors are consistent because because the cursor is the find and getMore is an implementation detail. However the tailable cursors may need the support of readConcern

      Attachments

        Activity

          People

            backlog-server-query Backlog - Query Team (Inactive)
            misha.tyulenev@mongodb.com Misha Tyulenev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: