-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Fatal error: concurrent map iteration and map write #8989
Comments
I think I have a similar error occuring in a crash today. Again it's in the inmem code but with SeriesPointIterator. Thanks
|
@choffee I think this might be a related issue. Were you using 1.3.6, and has it reoccured? |
@anatolijd @choffee I have managed to reproduce both of these races. Working on a fix now. |
e-dard
added a commit
that referenced
this issue
Oct 25, 2017
Fixes #8989 and #8633. Previously when issuing commands involving a regex check, walking through the tags keys/values on a measurement, using the measurement's index, would be racy. This commit adds a new `TagKeyValue` type that abstracts away the multi-layer map we were using as an inverted index from tag keys and values to series ids. With this abstraction we can also make concurrent access to this inverted index goroutine safe. Finally, this commit fixes a very old bug in the index which will affect any query using a regex. Previously we would always check _every_ tag against a regex for a measurement, even when we had found a match.
ghost
removed
the
review
label
Oct 25, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Directions
I've the same as described in #8633
Sympthoms are very similar -
POST /write?db=telegraf
from newly scaled out instances (and new tag values),SHOW TAG VALUES ON telegraf WITH KEY
queries (from Grafana dashboard),This is very worrying, because it means it will happen even more often as more people in our company start using Grafana dashboard for influxdb data.
Is it a bug ? Is there a way to prevent this to happen ?
Please help us to solve it.
Our setup:
Influxdb cluster with 2 data nodes (8 cores, 64GB each).
telegraf database stats:
short log:
log stack trace attached.
influxd.log.fatal.gz
The text was updated successfully, but these errors were encountered: