Feature #10200
session level heap usage tracking
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Greg Shah about 1 year ago
The idea is to use JVM APIs to track overall heap and CPU metrics to determine when the system is overcommitted. After that point, we should start killing sessions that are causing the problem. Of course, this also means that we need some way to measure session level usage to identify which sessions need killing.