## TL;DR

This was a storage-engine bug in InfluxDB 2.x, fixed in v2.7.12.

## Steps

1. This was a storage-engine bug in InfluxDB 2.x, fixed in v2.7.12. If a bucket periodically goes quiet for reads and writes on its own , especially around midnight UTC , upgrade to v2.7.12 or later; a reporter who hit it daily at 00:00 UTC confirmed the behavior stopped after upgrading (an InfluxData team member confirmed 2.7.12 is a stable release). Before upgrading, rule out resource exhaustion, but the signature here is a healthy host with only one index affected. Source: https://github.com/influxdata/influxdb/issues/23956

2. Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.

## When to use

You are seeing this: On InfluxDB 2.x (reported on v2.3.0), a bucket's main index intermittently stopped reading and writing every couple of days , other indexes kept working. Use this skill when you run into "InfluxDB 2.x bucket stops reading/writing every couple of days (00:00 UTC) , fixed in 2.7.12".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: v2.3.0, v2.7.12, confirmed 2.7.12. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://github.com/influxdata/influxdb/issues/23956
