[SERVER-79929] Test to validate cluster parameter after restart requires persistence but is not flagged Created: 11/Aug/23  Updated: 29/Oct/23  Resolved: 11/Aug/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
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
Operating System: ALL
Steps To Reproduce:

1. Run change_streams_cluster_parameters_standalone.js with the inMemory storage engine

Sprint: Sharding EMEA 2023-08-21
Participants:
Linked BF Score: 67

 Description   

SERVER-79236 added a test to ensure that after starting up a standalone node that previously was a replica set with a cluster parameter, it will not fail. However, this test requires persistence, but it is not flagged as such, which would cause the test to fail when checking for the parameter after starting a node as standalone.

This test should be blacklisted from the inMemory suites.



 Comments   
Comment by Githook User [ 11/Aug/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-79929 Add requires_persistence tag in jstest to check standalone start up with change stream cluster parameters
Branch: master
https://github.com/mongodb/mongo/commit/06b21efd381cee3e1904fb8447f03d04a2cfbb8d

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