KOstas
Reputation: 109
I'm seeking assistance in configuring the WAL rotation to address an issue with memory exhausted in TimescaleDB
I am utilizing the official single-node Helm chart for TimescaleDB 1.7.0 in my operations. We recently implemented a data pipeline involving a substantial influx of write operations per second. Unfortunately, after running the pipeline for two and a half days, I encountered a problem whereby my 12 GB Write-Ahead Log (WAL) memory became depleted. To resolve this issue, I need assistance with configuring the WAL rotation. Despite examining the values.yml file, I could not locate the relevant configuration option.
Upvotes: 0
Views: 174
Answers (1)
Related Questions
- Issue with query performance after enabling compression in TimescaleDB
- Timescaledb drizzle connection - FATAL: remaining connection slots are reserved for roles with the SUPERUSER attribute
- What could be the problem with a Continuous Aggregate from multiple TimescaleDB Hypertables?
- wal2json with the existing WAL (Postgres)
- Does turning off fsync in PostgreSQL can corrupt all the database or only the specific table I'm working with
- PostgreSQL/TimescaleDB: How to save only rows with a delta relative to the last similar row?
- How to plan the Timescaledb for huge price data with simple table column
- Is there a technique with timescaledb to delete rows to reduce the frequency of older timescale data?
- Select the right time chunk with TimescaleDB