[SERVER-62794] Fix BucketCatalog memory threshold initialization Created: 20/Jan/22  Updated: 29/Oct/23  Resolved: 21/Jan/22

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

Type: Bug Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Dan Larkin-York
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.2
Sprint: Execution Team 2022-01-24, Execution Team 2022-02-07
Participants:
Linked BF Score: 50

 Description   

It looks like we were relying on undefined behavior in initializing the memory threshold, and the that the Apple silicon builder uses a different initialization order. We should avoid checking the ProcessInfo until runtime.



 Comments   
Comment by Githook User [ 22/Jan/22 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-62794 Fix BucketCatalog memory threshold initialization
Branch: v5.2
https://github.com/mongodb/mongo/commit/565edb2589ec3a1f59a0808618a45a0384ffc9c8

Comment by Githook User [ 21/Jan/22 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-62794 Fix BucketCatalog memory threshold initialization
Branch: master
https://github.com/mongodb/mongo/commit/4cc29a126f01c7ca94aa6c5b0a3c7a84da785a76

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