influxdata / influxdata/influxdb
`planning_time` cost too much time
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
influxdb version 1.8.0
This is an occasional problem. Who knows how to analyze it
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
The report names InfluxDB 1.8.0 and shows two screenshots, but provides no source file, test, query, or reproducible steps. Start by obtaining the exact query and conditions behind the occasional planning_time delay; done means a repeatable reproduction, identified cause, and a regression test or documented resolution.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100