Memory Limit Error in MutatePlainMergeTreeTask
TLDR Vishal encountered a MEMORY_LIMIT_EXCEEDED error. Ankit inquired about total memory capacity of instance hosting signoz.
Powered by Struct AI
2
6mo
May 29, 2023 (6 months ago)
Vishal
Vishal
02:13 PMGetting error as per below
2023.05.29 14:07:00.725018 [ 28 ] {3878bf9e-aad5-42f8-827c-eb6b46e61409::20230528_1646_3017_14_13054} <Error> MutatePlainMergeTreeTask: Code: 241. DB::Exception: Memory limit (total) exceeded: would use 3.60 GiB (attempt to allocate chunk of 4220276 bytes), maximum: 3.60 GiB. OvercommitTracker decision: Memory overcommit isn't used. Waiting time or overcommit denominator are set to zero. (MEMORY_LIMIT_EXCEEDED) (version 22.8.8.3 (official build))
2023.05.29 14:07:00.726425 [ 28 ] {3878bf9e-aad5-42f8-827c-eb6b46e61409::20230528_1646_3017_14_13054} <Error> virtual bool DB::MutatePlainMergeTreeTask::executeStep(): Code: 241. DB::Exception: Memory limit (total) exceeded: would use 3.60 GiB (attempt to allocate chunk of 4220276 bytes), maximum: 3.60 GiB. OvercommitTracker decision: Memory overcommit isn't used. Waiting time or overcommit denominator are set to zero. (MEMORY_LIMIT_EXCEEDED), Stack trace
Any idea?
2023.05.29 14:07:00.725018 [ 28 ] {3878bf9e-aad5-42f8-827c-eb6b46e61409::20230528_1646_3017_14_13054} <Error> MutatePlainMergeTreeTask: Code: 241. DB::Exception: Memory limit (total) exceeded: would use 3.60 GiB (attempt to allocate chunk of 4220276 bytes), maximum: 3.60 GiB. OvercommitTracker decision: Memory overcommit isn't used. Waiting time or overcommit denominator are set to zero. (MEMORY_LIMIT_EXCEEDED) (version 22.8.8.3 (official build))
2023.05.29 14:07:00.726425 [ 28 ] {3878bf9e-aad5-42f8-827c-eb6b46e61409::20230528_1646_3017_14_13054} <Error> virtual bool DB::MutatePlainMergeTreeTask::executeStep(): Code: 241. DB::Exception: Memory limit (total) exceeded: would use 3.60 GiB (attempt to allocate chunk of 4220276 bytes), maximum: 3.60 GiB. OvercommitTracker decision: Memory overcommit isn't used. Waiting time or overcommit denominator are set to zero. (MEMORY_LIMIT_EXCEEDED), Stack trace
Any idea?
Ankit
Ankit
06:19 PM4GB might not be sufficient. What is the total memory capacity of the instance where signoz s hosted?
SigNoz Community
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
Indexed 1023 threads (61% resolved)
Similar Threads
Memory Limit Exceeded Error in Production
Vishal encountered a memory limit error, Pranay shared a related link and Vishnu is also experiencing similar issues in production.
4
6mo
SigNoz crashing in k8s due to ClickHouse OOM
Travis reported SigNoz crashing in k8s due to ClickHouse OOM. The team suggested increasing resources for ClickHouse, and other troubleshooting steps, but the issue remains unresolved.
77
8mo
Dashboard Load Issues and Possible Solutions
Al experiences dashboard loading issues since updating to `0.18.1`. Srikanth believes the issue is not version related and suggests examining queries, memory resources, and server distribution for improvements.
15
7mo