-
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 Elasticsearch module pipeline causing regex error on Elasticsearch cluster node #15840
Comments
Pinging @elastic/stack-monitoring (Stack monitoring) |
I'm able to reproduce this with Elasticsearch 8.0.0 and Filebeat 8.0.0. Investigating and fixing... |
While this isn't a bug in that it's causing incorrect results, I'm going to label it a bug anyway as it leads to a flood of warning messages in the ES log which is a bad user experience. |
I just finished dealing with this myself ("filebeat-7.5.1-elasticsearch-gc-pipeline") The flood of error messages can easily fill up the log partition, which then can crash the node |
We're using FileBeat 7.6 (ELK 7.6) and seeing this issue. What is the fix?? |
So I need to delete "Pipelines" (never heard of them) which Elastic creates but doesn't remove at upgrade. Okay... irm http://localhost:9200/_ingest/pipeline/filebeat-6* -Method DELETE
irm http://localhost:9200/_ingest/pipeline/filebeat-7.6* -Method DELETE
etc... curl http://localhost:9200/_ingest/pipeline/filebeat-6* -X DELETE
curl http://localhost:9200/_ingest/pipeline/filebeat-7.6* -X DELETE |
Not fixed. Still present in |
This regex error is being produced during Elasticsearch 7.5.1 startup with Filebeat Elasticsearch module ingest node pipelines resident in the cluster.
It looks like the error is caused by change elastic/elasticsearch#47374.
I am not sure why, I can only get it to reproduce with a multi-node ES cluster. It seems to not reproduce on the elected master node.
node
json-clu-2b
:node
json-clu-2a
:Filebeat setup:
journalctl -u elasticsearch --no-pager
.@ycombinator
The text was updated successfully, but these errors were encountered: