I cannot make head or tail of this error, and its happening pretty randomly
to where I don't even know where to start looking.
This is what the full error looks like
Tire::Search::SearchRequestFailed: 500 :
{"error":"SearchPhaseExecutionException[Failed to execute phase
[query_fetch], total failure; shardFailures
{[7McitJnjQkqLkViqUpZUyw][content][4]:
FetchPhaseExecutionException[[content][4]: query[+_all:account +_all:set
+_all:up],from[0],size[20]: Fetch Failed [Failed to highlight field
[post_content]]]; nested: StringIndexOutOfBoundsException[String index out
of range: -5]; }]","status":500}
A query like
"relationship learning"
will run fine, but running
"relationship centered learning"
will throw the error, actually any of these letters c, d, j, q, x, z used
with "relationship learning" .. like "d relationship learning" will throw
the error.
Its truly maddening.
I'm running elasticsearch 19.2 with Tire
I just want to know where to start looking, any ideas will help.
can you see any errors in the log files that give more information about
what happens here? or can you make this reproducible with a selfcontained
gist?
simon
On Monday, April 1, 2013 8:07:32 AM UTC+2, concept47 wrote:
I cannot make head or tail of this error, and its happening pretty
randomly to where I don't even know where to start looking.
This is what the full error looks like
Tire::Search::SearchRequestFailed: 500 :
{"error":"SearchPhaseExecutionException[Failed to execute phase
[query_fetch], total failure; shardFailures
{[7McitJnjQkqLkViqUpZUyw][content][4]:
FetchPhaseExecutionException[[content][4]: query[+_all:account +_all:set
+_all:up],from[0],size[20]: Fetch Failed [Failed to highlight field
[post_content]]]; nested: StringIndexOutOfBoundsException[String index out
of range: -5]; }]","status":500}
A query like
"relationship learning"
will run fine, but running
"relationship centered learning"
will throw the error, actually any of these letters c, d, j, q, x, z used
with "relationship learning" .. like "d relationship learning" will throw
the error.
Its truly maddening.
I'm running elasticsearch 19.2 with Tire
I just want to know where to start looking, any ideas will help.
Its too random to reproduce, and I'm trying to track down what could be
wrong.
The error occurs on random queries, but once those queries error out, they always error out.
Nothing in Elasticsearch logs. In fact this is all thats in there.
On Monday, April 1, 2013 4:19:00 AM UTC-5, simonw wrote:
can you see any errors in the log files that give more information about
what happens here? or can you make this reproducible with a selfcontained
gist?
We can't, because specific ux interactions in our app depend on that
particular restriction.
What we will do drop the use of fast vector highlighter, then watch that
lucene ticket to see when it gets resolved and eventually makes its way
into elasticsearch, before turning it back on.
thank you so very much for all your help Simon.
This was driving me absolutely crazy.
so I can try to put this into a lucene test but I guess this is rather an
ngram issue than a highlighter issue.
Can you open an issue on github (elasticsearch) and I take it from there?
simon
On Thursday, April 4, 2013 7:13:40 AM UTC+2, concept47 wrote:
Hey Simon,
I just discovered that term_vector takes the following as arguments, yes,
with_offsets, with_positions in addition to with_position_offsets.
Could using one of the other arguments (not with_positions_offsets) avoid
this exceptions?
On Wednesday, April 3, 2013 4:27:00 AM UTC-5, simonw wrote:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.