-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic with unread show series iterators during drop database #7334
Comments
Has this been fixed @mark-rushakoff? The script doesn't seem to panic on |
It still panics, although in my experience today, it either fails on the first couple runs from a fresh start of influxdb, or it succeeds forever. I tried to write a shorter repro with only the standard library, but I had less luck reproducing the issue with that approach. Here's the stack trace on master at b385dec. I had to use the repro script in the gist, with influx-stress at commit 96012d6c5d72fdcc61bdafc029214d0b786e5e0b.
|
Calling this function with a series ID that does not exist in the measurement causes a panic. Fixes #7334
Bug report
System info:
OSX, built from 7e515cf
Steps to reproduce:
Run repro script here:
https://gist.github.com/desa/1d43052f99b44f8957b3194d69c0588f
Expected behavior:
Database is dropped correctly.
Actual behavior:
This panic:
Additional info:
The repro script opens an HTTP request for
SHOW SERIES
, but does not read or close the response body. Then a separate HTTP request runsDROP DATABASE
. Eventually the iterator for show series advances, but it tries to read a shard that was removed when the database was dropped, and it panics there.cc @jsternberg
The text was updated successfully, but these errors were encountered: