-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Flush jemalloc profile on MEMORY_LIMIT_EXCEEDED on CI #82035
Copy link
Copy link
Closed
Labels
comp-ci-infrastructureCI/CD pipelines (GitHub Actions, CI scripts, runners).CI/CD pipelines (GitHub Actions, CI scripts, runners).memoryWhen memory usage is higher than expectedWhen memory usage is higher than expected
Description
Usually on such errors we have huge difference between RSS and MemoryTracking metric, i.e. 1
2025-06-16 20:21:19 Code: 241. DB::Exception: Received from localhost:9000. DB::Exception: (total) memory limit exceeded: would use 10.45 GiB (attempt to allocate chunk of 1.08 MiB bytes), current RSS: 56.33 GiB, maximum: 55.60 GiB. OvercommitTracker decision: Memory overcommit has not freed enough memory. (MEMORY_LIMIT_EXCEEDED)
2025-06-16 20:21:19 (query: create table test_table engine MergeTree order by sum as select 100 as sum union all select 200 as sum;)
By having jemalloc profile (text and flamegraph version) we can tell where it comes from
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
comp-ci-infrastructureCI/CD pipelines (GitHub Actions, CI scripts, runners).CI/CD pipelines (GitHub Actions, CI scripts, runners).memoryWhen memory usage is higher than expectedWhen memory usage is higher than expected