-
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 after upgrade from 0.12 to 0.13.0 #6760
Comments
Panic will happen sooner or later. Maybe not immediately after server starts listening. |
https://golang.org/doc/go1.6#runtime The runtime has added lightweight, best-effort detection of concurrent misuse of maps. As always, if one goroutine is writing to a map, no other goroutine should be reading or writing the map concurrently. If the runtime detects this condition, it prints a diagnosis and crashes the program. The best way to find out more about the problem is to run the program under the race detector, which will more reliably identify the race and give more detail. |
https://github.com/influxdata/influxdb/blob/master/services/meta/client.go#L603 authCache map is changed without calling Lock first, rather RLock was called. |
I fixed it. I'll submit patch this evening. |
Fixed via #6769 |
Bug report
System info: influxdb 0.13, 64-bit debian wheezy, prebuilt package
Steps to reproduce:
Expected behavior: should work same as previous version
Actual behavior: panic
Additional info:
It happens sometimes only, sometimes it starts without problems.
The text was updated successfully, but these errors were encountered: