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

Fix SBE bug with replset init where checkCanServeReads fails

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • Query 2021-01-11, Query 2021-01-25
    • 42

      https://github.com/mongodb/mongo/blob/bb3279a62dfc65bdafa5164a7ce85c8322b4757b/src/mongo/db/repl/replication_coordinator_impl.cpp#L2887

      When a ShardingTest is being initialized with sbe_enabled, it looks like the above check to see if a node can serve reads fails in the call to IndexScanStage::open():
      https://github.com/mongodb/mongo/blob/bb3279a62dfc65bdafa5164a7ce85c8322b4757b/src/mongo/db/exec/sbe/stages/ix_scan.cpp#L179
      The failure may be related to SERVER-48489, and should be reproducible by running:

      python buildscripts/resmoke.py run --suite=no_passthrough --mongodSetParameters="{featureFlagSBE: true}" jstests/noPassthrough/currentop_query.js

      This work should make it possible to remove the sbe_incompatible tag from at least these noPassthrough tests (it is worth checking if a few more can have the tag removed as well once this is fixed):

      • jstests/noPassthrough/currentop_query.js
      • jstests/noPassthrough/kill_operations.js
      • jstests/noPassthrough/killop.js

       

            Assignee:
            david.storch@mongodb.com David Storch
            Reporter:
            alya.berciu@mongodb.com Alya Berciu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: