Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
6.3.1
-
None
-
None
-
SkySQL AWS 32x 128 single node
Description
tools to track memory
Attachments
Issue Links
- blocks
-
MCOL-5285 SkySQL OOM Crash? Memory not being released? testing
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
Currently theres a customer whose memory appears not to be released in skysql.
The current work around is that RDBA/ SRE has to manually mcsShutdown and mcsStart every couple days. However the customer often has to file a ticket saying its crashed and to restart before the scheduled stop/start to clear memory. *Link to Logs & Configs in comment below* |
tools to track memory |
Rank | Ranked higher |
Rank | Ranked higher |
Rank | Ranked lower |
Status | Open [ 1 ] | In Progress [ 3 ] |
Rank | Ranked lower |
Fix Version/s | 23.02.1 [ 28701 ] | |
Fix Version/s | 23.02 [ 28209 ] |
Issue Type | Bug [ 1 ] | Task [ 3 ] |
Rank | Ranked lower |
Rank | Ranked higher |
Rank | Ranked higher |
Fix Version/s | 23.02 [ 28209 ] | |
Fix Version/s | 23.02.1 [ 28701 ] |
Fix Version/s | 23.02.2 [ 28713 ] | |
Fix Version/s | 23.02 [ 28209 ] |
Component/s | advanced tools [ 13515 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Component/s | advanced tools [ 13515 ] |
Labels | mcs_cs_datamesh |
The heap reports are being generated in `/var/run/columnstore/heapprofs/` and will be sent to s3 as well as their svg versions processed by jeprof.