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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 4.5.1
    • Fix Version/s: None
    • Component/s: Sharding
    • Operating System:
      ALL
    • Steps To Reproduce:
      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

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

              Dates

              Created:
              Updated:
              Resolved: