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

Add test that FCV 4.4 config server expects commitChunkMigration to contain a ChunkVersion

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc0, 4.7.0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • v4.4
    • Sharding 2020-03-09

      This ticket is to add test coverage for this assertion in ShardingCatalogManager::checkChunkMatchesRequest.

      It could be done through a unit test or integration test. We have unit these two related unit test files:

      https://github.com/mongodb/mongo/blob/master/src/mongo/db/s/config/sharding_catalog_manager_split_chunk_test.cpp

      https://github.com/mongodb/mongo/blob/master/src/mongo/db/s/config/sharding_catalog_manager_merge_chunks_test.cpp

      that call methods on ShardingCatalogManager, so it might make sense to create an analogous sharding_catalog_manager_move_chunks_test.cpp.

      Alternatively, it could be tested in an integration test by directly sending commitChunkMigration to the config server without a ChunkVersion when the config server is in FCV 4.4. SeeĀ this class that represents a commiitChunkMigration request.

            Assignee:
            alex.taskov@mongodb.com Alexander Taskov (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: