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

Lock free read using linearizable read concern fasserts when issued to primary not yet accepting writes

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2021-04-05
    • 19

      A lock free read using linearizable read concern that runs concurrently with replication step up causes an fassert here: https://github.com/mongodb/mongo/blob/06a96bad7c0c5413b785776b5d0e51d436ecc958/src/mongo/db/db_raii.cpp#L300-L303

       

      The read source will be left unchanged as it is not modified for linearizable read concern but the flag that indicates that an update is needed it set because the node is not accepting writes yet. 

      https://github.com/mongodb/mongo/blob/06a96bad7c0c5413b785776b5d0e51d436ecc958/src/mongo/db/db_raii.cpp#L257-L264

       

            Assignee:
            henrik.edin@mongodb.com Henrik Edin
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: