vrajat opened a new issue, #16110:
URL: https://github.com/apache/pinot/issues/16110
During high heap usage, the accountant tries to terminate the same query
multiple times. It does not track that a query has been interrupted or take
into account that heap usage by query will be released soon.
Example:
```
2025/05/31 12:07:07.768 WARN
[PerQueryCPUMemAccountantFactory$PerQueryCPUMemResourceUsageAccountant]
[CPUMemThreadAccountant] Heap used bytes 25300041728 exceeds critical level
25286619390
2025/05/31 12:07:07.770 ERROR
[PerQueryCPUMemAccountantFactory$PerQueryCPUMemResourceUsageAccountant]
[CPUMemThreadAccountant] Query 1137703336000046268 got picked because using
40934977096 bytes of memory, actual kill committed true}
2025/05/31 12:07:08.127 WARN
[PerQueryCPUMemAccountantFactory$PerQueryCPUMemResourceUsageAccountant]
[CPUMemThreadAccountant] Heap used bytes 25786580992 exceeds critical level
25286619390
2025/05/31 12:07:08.128 ERROR
[PerQueryCPUMemAccountantFactory$PerQueryCPUMemResourceUsageAccountant]
[CPUMemThreadAccountant] Query 1137703336000046268 got picked because using
41289535696 bytes of memory, actual kill committed true}
```
--
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: commits-unsubscr...@pinot.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org
