[SERVER-69840] Complete TODO listed in SERVER-61281 Created: 20/Sep/22  Updated: 08/Aug/23  Resolved: 08/Aug/23

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

Type: Task Priority: Major - P3
Reporter: PM Bot Assignee: Ivan Fefer
Resolution: Duplicate Votes: 0
Labels: autogen-todo
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-69821 Fix underflow error in query memory t... Closed
Related
is related to SERVER-61281 Fix underflow when accounting for Doc... Closed
Sprint: QE 2023-05-15, QE 2023-05-29, QE 2023-06-12
Participants:

 Description   

There is a TODO in the codebase referencing a resolved ticket which is assigned to you.

Please follow this link to see the lines of code referencing this resolved ticket:
https://github.com/mongodb/mongo/search?q=SERVER-61281&type=Code

The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of this ticket to represent the work you're actually doing.



 Comments   
Comment by Ivan Fefer [ 08/Aug/23 ]

We discussed that this is a part of SERVER-69821, so I am closing it as duplicate

 

Comment by Rushan Chen [ 10/Jan/23 ]

Memory tracking has been improved by SERVER-61281, but reporting of underflow is not entirely eliminated.

As indicated by the comment above, the followup investigation should attempt to (1) resolve the remaining underflow accounting cases; SERVER-69821 (2) restore the underflow test indicated by the comments here.

One attempt could be to temporarily enable the original test(ie reporting the underflow), and analyze the regressions by running the test indicated in BF-25993

 

 

Comment by Nikita Lapkov (Inactive) [ 21/Sep/22 ]

That happened because we could not reopen the original ticket. Marking this as dependent on SERVER-69821, where the actual work to fix underflow error will happen.

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