Catalog Cache is not cleaned on ShardingTestFixture

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Hide

      1. Executes a test that extends ShardingTestFixture
      2. Make a catalog cache request that takes too long
      3. Finish the test before the request at 2 finish

      Show
      1. Executes a test that extends ShardingTestFixture 2. Make a catalog cache request that takes too long 3. Finish the test before the request at 2 finish
    • Sharding 2020-09-07
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      After the changes on SERVER-49975 a new executor pool is being created within the catalog cache. Additionally the destructor on ShardingTestFixture is not cleaning up the catalog cache previously created on the constructor.

      If the service context is destroyed and there is a pending refresh, this invariant will be hit on the service context destructor, because all operations should be finished by that point. We could cleanup the grid like ShardingMongodTestFixture or simply make sure the catalog cache executor is shutdown and joined on the ShardingTestFixture destructor.

            Assignee:
            Tommaso Tocci
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: