-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Filebeat kubernetes fatal error: concurrent map writes #17968
Comments
Pinging @elastic/integrations-platforms (Team:Platforms) |
Hey @brummelbaer, Thanks for your report! |
Hi @jsoriano, Thank you for looking into this.
I was using extra fields and this might be the reason why you were not able to reproduce the error. I am sorry that I left these out in my previous post. I just ran a quick test and it failed as soon as I added the extra field.
No I am not providing any additional configuration. |
@brummelbaer ok, it makes more sense now 🙂, the trace you reported contained references to the I think that the problem is going to be that both Thanks! |
An update, I could reproduce this issue, also after starting an ES cluster with ECK:
These pods have a hint to use the elasticsearch module to parse the logs, so it must be some interaction between these processors, and something used in the elasticsearch module.
Still investigating what can be the issue. |
Pinging @elastic/integrations-services (Team:Services) |
@jsoriano I'm glad that your are looking into this issue and also were able to reproduce the error. If you need some more information don't hesitate to contact me |
I think I have found the issue, and I have also found that it is already fixed on master 😄 with this change: #13808. Using an image with this fix I am not able to reproduce the issue. I am closing this issue and opening backports for 7.6 and 6.8, it is already backported to 7.7, so it will be available in 7.7.0. |
Thank you for working on this topic. Do you know when 7.7 will be released? |
It will probably be released soon. If you want to try in the meantime, the |
Hi,
Created this issue after posting to: https://discuss.elastic.co/t/filebeat-kubernetes-fatal-error-concurrent-map-writes/229660
I have run into a problem with the autodiscovery module on kubernetes. Filebeat is being deployed as suggested in the documentation with the addition that I wanted to have additional cloud and host metadata. Therefore I enabled the
add_cloud_metadata
and theadd_host_metadata
processor. As soon as theadd_cloud_metadata
processor is activated and the beat is being deployed to the cluster it crashes on some on the nodes (see log below). If theadd_cloud_metadata
processor is disabled everything works fine. It might have something to do with elasticsearch itself, because the beat and elasticsearch are deployed in the same cluster.Does anybody have any suggestions regarding this error?
Greetings
Samuel
Setup information
elastic kubernetes operator: 1.0.1
elastic version: 7.6.2
filebeat version: 7.6.2
master nodes: 3
data nodes: 2
kibana nodes: 1
Filebeat configuration
Debug log
The text was updated successfully, but these errors were encountered: