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

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.5.1
    • Component/s: 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

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

              Created:
              Updated:
              Resolved: