influxdata / influxdata/influxdb
buildtsi: truncate input/output error during database defragmentation
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Steps to reproduce:
Executing command :
su - influxdb -s /bin/bash -c "influx_inspect buildtsi -compact-series-file -datadir /var/lib/influxdb/data -waldir /var/lib/influxdb/wal "
Expected behavior:
database compaction according to https://docs.influxdata.com/influxdb/v1.8/administration/compact-series-file/
Actual behavior:
The system issues the following messages and stops :
processing partition for "/var/lib/influxdb/data/pskreporter/_series/00"
processing partition for "/var/lib/influxdb/data/pskreporter/_series/02"
processing partition for "/var/lib/influxdb/data/pskreporter/_series/01"
processing partition for "/var/lib/influxdb/data/pskreporter/_series/03"
processing segment "/var/lib/influxdb/data/pskreporter/_series/01/0000" 0
processing segment "/var/lib/influxdb/data/pskreporter/_series/00/0000" 0
processing segment "/var/lib/influxdb/data/pskreporter/_series/02/0000" 0
processing segment "/var/lib/influxdb/data/pskreporter/_series/01/0001" 1
processing segment "/var/lib/influxdb/data/pskreporter/_series/03/0000" 0
>>>> buildtsi: truncate /var/lib/influxdb/data/pskreporter/_series/00/0000.tmp: input/output error
Environment info:
System info : Linux 6.1.21-v8+ aarch64 (but the same happens on Linux 5.10 arm32)
InfluxDV version : InfluxDB v1.8.10 (git: 1.8 688e697c51fd)
The database in very simple : only one table currently containing 9746700 KBytes
Best regarrds
UP
Contributor guide
Research direction
Start by reproducing the reported `influx_inspect buildtsi -compact-series-file` command on the Linux ARM environment described, focusing on the `buildtsi` entry point and the failing `truncate` operation for the temporary series file. Done means database defragmentation completes without the reported input/output error, with coverage for the failing condition if the relevant test location is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- databases, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100