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

Ignore reshardCollection change event after v6.0->v7.0 upgrade in test

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.6
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • QE 2024-01-22
    • 3

      The test 'change_streams_split_event_v1_v2_tokens.js' is broken in v7.0 by BACKPORT-17706 to v6.0 of SERVER-62955 (this is a multiversion test, so changes to v6.0 can break the test in v7.0). The crux is, 'reshardCollection' is not emitted in v6.0 before and after the backport, however, after the backport, if one upgrades the cluster to v7.0 (without issuing any new resharding commands) he might discover a 'new' reshardCollection event in the past.

            Assignee:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Reporter:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: