Skip to content
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.

Sign up for GitHub

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

Jump to bottom

FVH can result in massive CPU & RAM usage if MultPhraseQuery is large #3142

Closed
s1monw opened this issue Jun 6, 2013 · 0 comments
Closed

FVH can result in massive CPU & RAM usage if MultPhraseQuery is large #3142

s1monw opened this issue Jun 6, 2013 · 0 comments
Assignees
@s1monw
Labels
>bug v0.90.2 v1.0.0.Beta1

Comments

@s1monw
Copy link
Contributor

s1monw commented Jun 6, 2013

in the case of a MultiPhraseQuery (multiple terms on the same position) the highlighter can result in a very big cpu and memory cosumption. We should cut off if there are too many terms and just highlight term by term instead which might result in slightly different highlights but doesn't potentially kill a node.
@ghost ghost assigned s1monw Jun 6, 2013
@s1monw s1monw closed this as completed in 1c513bc Jun 6, 2013
s1monw added a commit that referenced this issue Jun 6, 2013
@s1monw
Fallback to extract terms if MultiPhraseQuery is large
6e73bde 
Currently if MPQ is very large highlighing can take down a node
or cause high CPU / RAM consumption. If the query grows > 16 terms
we just extract the terms and do term by term highlighting.

Closes  #3142 #3128
synhershko pushed a commit to synhershko/elasticsearch that referenced this issue Sep 2, 2013
@s1monw @synhershko
Fallback to extract terms if MultiPhraseQuery is large
c8f637a 
Currently if MPQ is very large highlighing can take down a node
or cause high CPU / RAM consumption. If the query grows > 16 terms
we just extract the terms and do term by term highlighting.

Closes  elastic#3142 elastic#3128

Conflicts:
	src/test/java/org/elasticsearch/test/integration/search/highlight/HighlighterSearchTests.java
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@s1monw
Fallback to extract terms if MultiPhraseQuery is large
be25323 
Currently if MPQ is very large highlighing can take down a node
or cause high CPU / RAM consumption. If the query grows > 16 terms
we just extract the terms and do term by term highlighting.

Closes  elastic#3142 elastic#3128
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@s1monw s1monw

Labels
>bug v0.90.2 v1.0.0.Beta1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@s1monw