influxdata / influxdata/influxdb
influxdb data loss
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
InfluxDB version=1.8.1
kubernetes version=1.14.2
When I deployed the influxdb service in kubernets, I also created the PV and PVC persistent storage, and then created the Prometheus table. However, when infixdb was restarted, the internal Prometheus table was lost. Why?
This is the deployment file
This is the data in the NFS file system
This is the kubernetes dashboard panel. The service has been restarted
This is the query table operation performed inside the container after the service restart, and the Prometheus table is lost
Contributor guide
Research direction
Start with the deployment file, PV/PVC configuration, and the NFS filesystem evidence attached to the issue. Reproduce the Kubernetes service restart and verify whether InfluxDB is using the expected persistent mount and data path. Done means the Prometheus table remains available after restart, or the persistence misconfiguration is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100