influxdata / influxdata/influxdb

Bad performance leads to timeouts when writing to new shards

Open
#22,642 1 comment 0 reactions 0 assignees View on GitHub
area/2.x area/performance area/writes
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

I've seen two community reports of bad write performance in 2.0.8:
* https://community.influxdata.com/t/influx-write-fails-with-internal-error
* https://community.influxdata.com/t/timeouts-severe-loading-data

Both are using `influx write` which should handle chunking large inputs into manageable batches, so I don't think either is sending more data to the server than it should be able to handle. Despite that, both show engine-level timeouts during write requests.

This could be an issue since 2.0 GA, but I'm suspicious of a regression since we're only starting to hear about it now.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the engine-level write timeouts through `influx write`, using the two linked community reports as symptom references and focusing on writes to new shards. Compare behavior with the reported 2.0.8 cases and establish a repeatable test that confirms writes complete without timeouts.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
databases, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.