-
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 read and map write #6235
Comments
Are you compiling with go1.6? There is a chance that this symptom doesn't occur in builds built with go1.4.3 (even though the issue is still latent in such builds). I say this because I had another program that had a latent map concurrency issue but I wasn't aware of it until I started compiling with 1.6. Of course, the underlying concurrency issue should be addressed, irrespective of which version you are using. |
@jonseymour Thanks for the info, I will rebuild InfluxDB with Go1.4.3 and see if it resolve this issue. |
My take on the issue is that that the map dereference at line 374 (https://github.com/influxdata/influxdb/blob/master/tsdb/shard.go#L374) used to be protected by use of the DatabaseIndex lock, but since 03ced4c this protection has been removed. /cc @jwilder |
@syepes thanks for the detailed report. The issue should be fixed in the next release. |
fixed via #6190. |
this isn't fixed. I'm running the nightly (5/16/2016) and still see the crash.
|
@duccyberfend will be fixed in |
Bug report
Has anyone else been experiencing this issue?
System info:
InfluxDB Master (2f6340b, e22f098, c2ac8c8)
FreeBSD 10.3 / 16GB / ZFS
Steps to reproduce:
Just run InfluxDB (2f6340b, e22f098, c2ac8c8) for 1 or 2 days and it will crash.
Actual behavior:
Since the version 2f6340b I have been getting this fatal error: concurrent map read and map write
Additional info: Crash logs from version (2f6340b, e22f098, c2ac8c8)
Carsh_1.txt
Carsh_1a.txt
Carsh_2.txt
Carsh_3.txt
The text was updated successfully, but these errors were encountered: