influxdata / influxdata/influxdb
TSI deadlock when `DROP MEASUREMENT` and `DROP DATABASE` run concurrently
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
This can be reproduced easily with v1.7.x. It doesn't seem to exist in inmem index.
Assuming a measurement `m1` in database `db1` has many time series, run `DROP MEASUREMENT m1` in one influx session and then run `DROP DATABASE db1` in a new session, deadlock happens and both queries block.
The stack dump is attached. It's captured with v1.7.9.
[stackdump.txt](https://github.com/influxdata/influxdb/files/4191595/stackdump.txt)
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 v1.7.x scenario with many time series in measurement m1: run DROP MEASUREMENT m1 and DROP DATABASE db1 concurrently in separate sessions. Review the attached stackdump.txt while both queries block; done means the concurrent operations no longer deadlock. No source file or test is identified in the report.
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
- 25/100