[SERVER-67017] Account for one more chunk in shard_existing_coll_chunk_count.js (v4.4) Created: 03/Jun/22  Updated: 29/Oct/23  Resolved: 07/Jun/22

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

Type: Improvement Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
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: Sharding EMEA 2022-06-13
Participants:
Linked BF Score: 20

 Description   

According to the logs of a failure, a refresh from a stale CSRS node did not allow the shard to acknowledge 2 splits. As a result, the shard auto-splitted more than needed.

Make this check more loose, allowing the presence of an additional chunk.

The failure has only been observed on v4.4 branch, probably because in v5.0 the commit of the chunk split happens with majority, while in v4.4 the default write concern was 1.



 Comments   
Comment by Githook User [ 07/Jun/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-67017 Account for one more chunk in shard_existing_coll_chunk_count.js
Branch: v4.4
https://github.com/mongodb/mongo/commit/88e695b37b5abe9eb17009f42afef014cf596a87

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