[SERVER-74806] Write size estimation logic does not account for runtime/let constants Created: 13/Mar/23  Updated: 29/Oct/23  Resolved: 11/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.0.14, 6.3.0-rc0, 6.0.5
Fix Version/s: 7.1.0-rc0, 6.0.7, 5.0.19, 4.4.23, 7.0.0-rc2

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

Issue Links:
Backports
Problem/Incident
Related
is related to SERVER-77653 Batch write size estimation logic on ... Open
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0, v6.3, v6.0, v5.0, v4.4
Sprint: QE 2023-05-15
Participants:
Case:
Linked BF Score: 164

 Description   

See comment for repro



 Comments   
Comment by Githook User [ 28/Jun/23 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com', 'username': 'mtandrei'}

Message: SERVER-74806 Account for header size when computing initial size of batch write

(cherry picked from commit 2f96310f29d6c5f377b12b981747021e23e685da)
Branch: v4.4
https://github.com/mongodb/mongo/commit/4119d815b0246904bc5b98986c7de4092020b180

Comment by Githook User [ 30/May/23 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com', 'username': 'mtandrei'}

Message: SERVER-74806 Account for header size when computing initial size of batch write

(cherry picked from commit 1e233afdb0def2aed7521ae087b575c95245e257)
(cherry picked from commit a1f0cfdcbcc632133a7e65665c84b9344f4d8153)
(cherry picked from commit 1007eac377c0d8582e2a5d7a8f1a8a790f69471b)
(cherry picked from commit e92e961a2df3b3b83f524a9b90e93404584418d0)
Branch: v5.0
https://github.com/mongodb/mongo/commit/2f96310f29d6c5f377b12b981747021e23e685da

Comment by Githook User [ 25/May/23 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com', 'username': 'mtandrei'}

Message: SERVER-74806 Account for header size when computing initial size of batch write

(cherry picked from commit 1e233afdb0def2aed7521ae087b575c95245e257)
(cherry picked from commit a1f0cfdcbcc632133a7e65665c84b9344f4d8153)
(cherry picked from commit 1007eac377c0d8582e2a5d7a8f1a8a790f69471b)
Branch: v6.0
https://github.com/mongodb/mongo/commit/e92e961a2df3b3b83f524a9b90e93404584418d0

Comment by Githook User [ 18/May/23 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com', 'username': 'mtandrei'}

Message: SERVER-74806 Account for header size when computing initial size of batch write

(cherry picked from commit 1e233afdb0def2aed7521ae087b575c95245e257)
(cherry picked from commit a1f0cfdcbcc632133a7e65665c84b9344f4d8153)
Branch: v7.0
https://github.com/mongodb/mongo/commit/1007eac377c0d8582e2a5d7a8f1a8a790f69471b

Comment by Githook User [ 11/May/23 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com', 'username': 'mtandrei'}

Message: SERVER-74806 Account for header size when computing initial size of batch write
Branch: master
https://github.com/mongodb/mongo/commit/1e233afdb0def2aed7521ae087b575c95245e257

Comment by Mihai Andrei [ 13/Mar/23 ]

kyle.suarez@mongodb.com  yes, that sounds right to me

Comment by Kyle Suarez [ 13/Mar/23 ]

mihai.andrei@mongodb.com, since you mentioned that this affects master (as of commit 31b639c5f4cf66744a2b4cf6d6c6932c15d32373), I am going to go out on a limb and mark this ticket as affecting the v6.0 and v6.3 branches as well. I assume we will first fix on master and then backport?

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