influxdata / influxdata/influxdb
Report not enough space even though there are 100GB space
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
1. 3 days ago,the disk is out of space
2. Clean up the disk and free up space
3. And I found Influxdb Can't write new data ,since 3 days ago
__Expected behavior:__
After clean up the disk,InfluxDB can write new data
__Actual behavior:__
I get an error: There is not enough space on the disk.
But there is actually 100GB of space.
Finally,I restart infludb,and it can write new data.
__Environment info:__
OS - Windows Server 2016
InfluxDB v1.8.1
Why I need to restart InfluxDB? Is there anyway ,which it can run normally instead of restarting?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior on Windows Server 2016 with InfluxDB v1.8.1: fill the disk, free space, and try writing without restarting. Investigate how disk-space state is handled after cleanup; done means writes resume without requiring an InfluxDB restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100