[SERVER-48095] RSM refreshes cache but unknown metadata is needed on change_streams_primary_shard_unaware.js test Created: 11/May/20  Updated: 26/Jun/20  Resolved: 26/Jun/20

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

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Cheahuychou Mao
Resolution: Won't Fix Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Participants:

 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.


Generated at Thu Feb 08 05:16:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.