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

AsyncRequestsSender may fail if shard is removed concurrently

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Networking
    • Labels:
      None
    • Sharding
    • ALL
    • Hide

      We were able to repro this bug consistently using the merge_with_drop_shard.js test and the attached diff to force the shard to reload before we create the MultiStatementTransactionRequestsSender object here: https://github.com/mongodb/mongo/blob/0f16c5fc452d16c5a92e43e9fdd96f3822f05271/src/mongo/s/query/establish_cursors.cpp#L64

      Show
      We were able to repro this bug consistently using the merge_with_drop_shard.js test and the attached diff to force the shard to reload before we create the MultiStatementTransactionRequestsSender object here: https://github.com/mongodb/mongo/blob/0f16c5fc452d16c5a92e43e9fdd96f3822f05271/src/mongo/s/query/establish_cursors.cpp#L64
    • 21

      In merge_with_drop_shard.js the test may fail due to the ARS calling GetShard when the resposne is returned. This failure occurs for currentOp in this case, but could potentially happen for any aggregation command that comes through this path.

        1. diff.txt
          0.7 kB

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            lamont.nelson@mongodb.com Lamont Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: