ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Identify and fix InfluxDB disk bloat and query lag caused by infinite retention policies or oversized shard groups with a step‑by‑step diagnostic guide.
When data disappears or queries fail, a common culprit is an incorrectly set bucket retention policy. This guide walks through the symptoms, diagnostic steps, and fixes for retention‑policy misconfigurations in InfluxDB 2.x.
Learn how to combine InfluxDB retention policies with continuous queries to keep high‑resolution recent data while automatically downsampling older points for efficient long‑term storage.
When InfluxDB deletes data it removes entire shards, not individual points. Aligning shard group duration with retention policies lets you age data efficiently while keeping I/O low and disk usage predictable.
JetStream Stream Retention Policy Precedence When configuring a JetStream stream with multiple retention limits— MaxBytes , MaxMsgs , and MaxAge —the NATS server accepts the settings without error but does not document a clear rule for which limit is evaluated first during message ingestion. This ambiguity can lead to unexpected eviction behavior, especially
Determine how NetBeans Local History enforces its retention policy when both a maximum number of revisions per file and a maximum age are configured. The documentation cites independent limits but does not specify whether purging is triggered by exceeding either limit, both limits, or a combined condition, nor whether the check occurs on each save or at IDE
influxdb
nats