-
Notifications
You must be signed in to change notification settings - Fork 70
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 writes #90
Comments
Hi, can you be more precise? Context, env, etc. Did it work fine before the update? Thanks |
CentOS 7, Docker 1.10.3, Go 1.6. I've built binary from development branch. And it is my first usage of dockerbeat :) |
Ok thank I'll have a look. You can try the beta2 version, waiting for the bug resolution. |
I've updated libbeat for beta 2 and got the same error. Any ideas? |
No idea.. We will work on it as soon as possible. Thanks for the feedback |
We have a concurrent map read/write problem here because we use a goroutine on exportContainerStats function. Golang has made the choice to not define map operations as atomic. Therefore they provide a solution, using I think we should try that instead of a new structure for concurrent map. |
@erwanncloarec I'm a total newbie in Go, so it was first working solution for this problem :) |
I think problem comes from this line: https://github.com/Ingensi/dockerbeat/blob/develop/beat/EventGenerator.go#L227 I'll try a mutex based solution soon... |
I've just launched your last development version and in a few minutes it threw following exception:
The text was updated successfully, but these errors were encountered: