Document pitfalls for test-related ops on various environments

XMLWordPrintableJSON

    • Type: Spec Change
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Component/s: None
    • None
    • Needed

      Create a document in the specifications repo to discuss pitfalls and special requirements for test-related operations on various environments.


      Original description: Before this Command Monitoring Tests we need to drop a database, and recreate a collection. Conversations with esha.maharishi have revealed that drivers must explicitly run flushRouterConfig against connected mongos when we drop databases. jeff.yemin suggests we run against a single mongos (modifying the URI that mongo orchestration provides us to only use a single address), but Esha points out that this just happens work because of an optimization in the mongos that dropDatabase is called on.

            Assignee:
            Unassigned
            Reporter:
            Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: