Uploaded image for project: 'Swift Driver'
  1. Swift Driver
  2. SWIFT-397

Unskip command monitoring tests on sharded topologies

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      The CommandMonitoringTests have a number of issues when tested against sharded topologies.

      The first problem is with this test, which has an unexpected extra observed event:

      Test case: A successful find event with a getmore and the server kills the cursor
      /Users/mbroadst/Development/mongo/mongo-swift-driver/Tests/MongoSwiftTests/CommandMonitoringTests.swift:63: error: -[MongoSwiftTests.CommandMonitoringTests testCommandMonitoring] : failed - Got a notification, but ran out of expected events
      Test Case '-[MongoSwiftTests.CommandMonitoringTests testCommandMonitoring]' failed (3.468 seconds).
      

      The second problem is somewhat more difficult. Before this test we are dropping a database, and recreating the collection. Conversations with Esha Maharishi have revealed that drivers must explicitly run flushRouterConfig against connected mongos when we drop databases. Jeffrey 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.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            matt.broadstone Matt Broadstone
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: