Fatal error: concurrent map writes about dockbeat HOT 8 CLOSED

Hi,

can you be more precise? Context, env, etc.

Did it work fine before the update?

Thanks

from dockbeat.

CentOS 7, Docker 1.10.3, Go 1.6. I've built binary from development branch. And it is my first usage of dockerbeat :)

from dockbeat.

Ok thank I'll have a look.

You can try the beta2 version, waiting for the bug resolution.

from dockbeat.

I've updated libbeat for beta 2 and got the same error. Any ideas?

from dockbeat.

No idea.. We will work on it as soon as possible.

Thanks for the feedback

from dockbeat.

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 sync.RWMutex.

I think we should try that instead of a new structure for concurrent map.

from dockbeat.

@erwanncloarec I'm a total newbie in Go, so it was first working solution for this problem :)

from dockbeat.

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...

from dockbeat.