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

RSM refreshes cache but unknown metadata is needed on change_streams_primary_shard_unaware.js test

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • 4.5.1
    • Sharding
    • ALL
      1. Start a sharded cluster
      2. Shard a collection and move a chunk
      3. Restart a shard
      4. Cause an execution of the RSM
      5. Check that the sharded state of the collection is not unknown

    Description

      In order to check the correct behavior of the change streams on recently restarted shards, it is needed to have a shard without initialized metadata. However, in some cases the restart can be seen as a topology change, which triggers the RSM thread, and this might lead to a refresh of the metadata. This generally causes failures when testing, because the exact scenario (a recently restarted shard) cannot be set. There should be a way to prevent this refresh, or, the way the change streams is tested should be changed.

      Attachments

        Activity

          People

            cheahuychou.mao@mongodb.com Cheahuychou Mao
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: