shizy818 opened a new pull request, #16932: URL: https://github.com/apache/iotdb/pull/16932
## Description Steps to reproduce the issue: 1. During flushing, the TVList is accessed by Query 1. FragmentInstanceContext of Query 1 calls `reserveMemoryCumulatively` to reserve memory. Query 1 is added into TVList's query set and be set as owner. 2. Query 2 access the TVList as well and is added into TVList's query set. 3. When Query 1 terminates, it should transfers the ownership of the TVList to Query 2. FragmentInstanceContext of Query 1 calls `releaseMemoryReservationManager` to release memory. 4. When Query 2 terminates, FragmentInstanceContext calls `reserveMemoryCumulatively` to release memory because Query 2 is the last query and be the owner. Release operation is invoked twice. This PR is to transfer momery virtually from MemoryReservationManager of Query 1 to that of Query 2 without actually allocating/freeing the memory. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
