Evaluate router ddl command response checks so they all parse writeConcern errors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 6.0.0, 7.0.0, 8.0.0, 8.2.0
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • 2
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-102024 added some extra code to ensure all DDL commands wait for the last write to be majority committed. This means that now it is more likely to receive writeConcernTimeout errors in the router. movePrimary is an example of a command that is not checking for write concern errors in the response. The purpose of this ticket is to first investigate if there are other DDL commands at the router level that are not checking for this, and then add the proper checks, like dropCollection does.

            Assignee:
            Unassigned
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: