Hi <#C01HWQ1R0BC|>
Iam using signoz version: v0.9...
# supportt
Talari Dhanunjaya
09/14/2025, 5:44 PMHi #C01HWQ1R0BC
Iam using signoz version: v0.90.1 . We updated the retention period to 4 days, but old trace data is not being deleted. The UI shows this error when trying to change it:
"Your last call to change retention period to 7 days failed. Please try again."
Kindly help us investigate and resolve this issue.Please find the screenshot below.
n
Nagesh Bansal
09/16/2025, 8:47 AM@Ask Inkeep Any suggestions here?
a
Ask Inkeep
09/16/2025, 8:47 AMThanks for tagging me @Nagesh Bansal. I'll look through relevant sources and get back to you shortly.
Ask Inkeep
09/16/2025, 8:47 AMBased on the available information, there's a known issue with changing traces retention settings in SigNoz that causes high CPU usage and errors (1) .
The issue occurs when attempting to modify retention settings - the system maxes out CPU at 100% for extended periods before eventually failing . This happens even when data is recent enough that nothing needs to be sent to cold storage or removed .
This problem was reported with version 0.58.0 on a system with approximately 30GB of data . The user experienced the same error you're encountering - being unable to change retention settings without the system maxing out CPU and failing .
Since this is an open issue from September 2024 , you may want to:
1. Check your system's CPU usage when attempting the retention change
2. Monitor your ClickHouse resource consumption
3. Consider reaching out to SigNoz support for assistance with this known issue
For additional help, visit GitHub .
Ask Inkeep
09/16/2025, 8:47 AMTo learn more, see the sources I considered: [[1] Changing traces retention settings erroring](https://github.com/SigNoz/signoz/issues/5876)
Ask Inkeep
09/16/2025, 8:48 AMAppreciate the feedback! Feel free to ask me again with additional guidance or context.
n
Nagesh Bansal
09/16/2025, 8:48 AMHey @Talari Dhanunjaya can you check the logs of signoz once
t
Talari Dhanunjaya
09/16/2025, 8:56 AM@Nagesh Bansal just now i tried to change retention. TTL is updated at DB tables level but still found below error in signoz logs
{"level":"error","timestamp":"2025-09-16T085308.392Z","caller":"clickhouseReader/reader.go:1517","msg":" ExecutingTTL request: ","request":"ALTER TABLE signoz_traces.traces_v3_resource ON CLUSTER cluster MODIFY TTL toDateTime(seen_at_ts_bucket_start) + toIntervalSecond(1800) + INTERVAL 1296000 SECOND DELETE SETTINGS materialize_ttl_after_modify=0;","stacktrace":"github.com/SigNoz/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).setTTLTraces.func1\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:1517"}
Even after TTL updated why and when old trace data will be deleted ???