[SERVER-84806] Ignore reshardCollection change event after v6.0->v7.0 upgrade in test Created: 12/Jan/24  Updated: 12/Jan/24  Resolved: 12/Jan/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.6

Type: Task Priority: Major - P3
Reporter: Romans Kasperovics Assignee: Romans Kasperovics
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: QE 2024-01-22
Participants:
Linked BF Score: 16

 Description   

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.



 Comments   
Comment by Githook User [ 12/Jan/24 ]

Author:

{'name': 'romanskas', 'email': '30618745+romanskas@users.noreply.github.com', 'username': 'romanskas'}

Message: SERVER-84806 Ignore reshardCollection event in test (#18015)

SERVER-84806 Ignore reshardCollection event in test

BACKPORT-17706 introduces reshardCollection backlog entry in v6.0.
Although it is not emitted as a change event in v6.0, it is emitted
after the upgrade to v7.0, which breaks the
change_streams_split_event_v1_v2_tokens.js test. This change relaxes the
test by ignoring reshardCollection events.

GitOrigin-RevId: 57b25e0965db0eb7c7c8d9119bd048e51d78b8b3
Branch: v7.0
https://github.com/mongodb/mongo/commit/8b07a796e2ec0f24f9d20735b466749a17198f82

Generated at Thu Feb 08 06:56:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.