[SERVER-36586] shard_existing_coll_chunk_count.js should restart both mongod and mongos after changing max chunk size Created: 10/Aug/18  Updated: 29/Oct/23  Resolved: 10/Aug/18

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

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
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
Participants:
Linked BF Score: 0

 Description   

In the last stable suite, with a last-stable mongos it's necessary to add back this line.



 Comments   
Comment by Githook User [ 10/Aug/18 ]

Author:

{'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com', 'username': 'saltzm'}

Message: SERVER-36586 The test shard_existing_coll_chunk_count.js should restart both mongod and mongos after changing max chunk size
Branch: master
https://github.com/mongodb/mongo/commit/6f45215828d8489d095781c8ab2b5ff358ee50af

Generated at Thu Feb 08 04:43:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.