-
Notifications
You must be signed in to change notification settings - Fork 24.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
Cluster crash for case insensitive grok query #49304
Comments
Pinging @elastic/es-core-features (:Core/Features/Ingest) |
Hi @dosera, I just tested this with the latest of the 7.4 branch which already includes #48899 and the grok pattern doesn't take down the cluster anymore. Maybe @henningandersen can confirm that the fix has been forward-ported to 7.5 and master (I couldn't find the patch upon quick search but maybe it wasn't needed on those branches). After that I think we can close this. |
Hi @cbuescher , so with the latest you refer to 7.4.3 I guess aka 0a07043 ? |
I used 7023df0 which should include that commit, yes. I just want to wait to hear about the situation on the newer 7.x branches and master before closing here. The "jcodings" dependencies there are at version "1.0.44", but the test added in #48899 seems to be on those branches (e.g. 8835142), so the version might be okay there. |
@cbuescher , yes, this was already fixed in 7.5 by #47374, so no changes were necessary in 7.5+. Will add a note to #48899 too. |
Great, closing then. |
Elasticsearch version:
Version: 7.4.0, Build: default/rpm/22e1767283e61a198cb4db791ea66e3f11ab9910/2019-09-27T08:36:48.569419Z, JVM: 13
Plugins installed:
/
JVM version:
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
OS version:
Linux 3.10.0-862.2.3.el7.x86_64 #1 SMP Wed May 9 18:05:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Description of the problem including expected versus actual behavior:
When using the grok debugger with a case insensitive pattern (?i) in Kibana a request is sent to elasticsearch that crashes all nodes involved.
This is most likely related to #48899 but I would not expect the whole cluster to crash just because of a query.
Steps to reproduce:
^%{DATA:before}(?<value>(?i)authorization[:=]\s?)(%{DATA:pass})([,]%{GREEDYDATA:after})?$
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: