[SERVER-69403] Behavioral change creating capped collection in sharded cluster Created: 02/Sep/22  Updated: 05/Sep/22  Resolved: 05/Sep/22

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

Type: Bug Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Enrico Golfieri
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Operating System: ALL
Participants:
Linked BF Score: 44

 Description   

The Java driver has a regression test for its create collection helper that is failing against a sharded cluster. The test runs the following command:

{
   create: <collection>,
   capped: true
   size: 40960
   max: 100
}

Followed by

{
    collStats: <collection>
}

and expects that the value of the storageSize field in the reply is equal to 40960.
But the actual value of the field is 4096.

The test first failed against MongoDB 6.2.0-alpha-209-g8de369e. The test last succeeded against v6.2.0-alpha-187-gbd8a8d4. The same test still passes against replica set and standalone topologies.



 Comments   
Comment by Kaloian Manassiev [ 05/Sep/22 ]

This Github link contains the commits that went in between these two hashes.

This is the same as BF-26272 and the offending commit (SERVER-66297) has been reverted. enrico.golfieri@mongodb.com is working on a fix to bring it back, but in the mean time it should not be impacting the drivers tests anymore, so I am closing it as duplicate.

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