ES Timeout issues?

This is what I'm doing in the Java API for search;

And even if I put a 2 sec timeout, I have often requests that take more
than 5 and even 10 seconds that does not time out. But sometime, I have
some query that take under 2 sec and says timed out.

On the documentation it says;
timeout A search timeout, bounding the search request to be executed within
the specified time value and bail with the hits accumulated up to that
point when expired. Defaults to no timeout.

With that I'm expecting every query to be under (or roughly) around 2
second, but not 5 or 10 seconds.

Am I doing something wrong, or is it really and ES issue ?

--

I have seen this issue pop up on the mailing list every now and then. The
timeout value is used only by the TimeLimitingCollector, so it only limits
the time used by Lucene in collecting documents. The parsing/gather/reduce
phases all lie outside of this time interval. However, I would find it
strange that something like the reduce phase would take so long.

For the record, I have the same issue.

--
Ivan

On Thu, Jan 3, 2013 at 8:47 AM, Jérôme Gagnon jerome.gagnon.1@gmail.comwrote:

This is what I'm doing in the Java API for search;
https://gist.github.com/4444788

And even if I put a 2 sec timeout, I have often requests that take more
than 5 and even 10 seconds that does not time out. But sometime, I have
some query that take under 2 sec and says timed out.

On the documentation it says;
timeout A search timeout, bounding the search request to be executed
within the specified time value and bail with the hits accumulated up to
that point when expired. Defaults to no timeout.

With that I'm expecting every query to be under (or roughly) around 2
second, but not 5 or 10 seconds.

Am I doing something wrong, or is it really and ES issue ?

--

--

Possibly because I use a lot of facetting on the same query ? Facetting and
sorting is done on the reduce phase if I'm not wrong ?

On Thursday, January 3, 2013 12:28:40 PM UTC-5, Ivan Brusic wrote:

I have seen this issue pop up on the mailing list every now and then. The
timeout value is used only by the TimeLimitingCollector, so it only limits
the time used by Lucene in collecting documents. The parsing/gather/reduce
phases all lie outside of this time interval. However, I would find it
strange that something like the reduce phase would take so long.

For the record, I have the same issue.

--
Ivan

On Thu, Jan 3, 2013 at 8:47 AM, Jérôme Gagnon <jerome....@gmail.com<javascript:>

wrote:

This is what I'm doing in the Java API for search;
https://gist.github.com/4444788

And even if I put a 2 sec timeout, I have often requests that take more
than 5 and even 10 seconds that does not time out. But sometime, I have
some query that take under 2 sec and says timed out.

On the documentation it says;
timeout A search timeout, bounding the search request to be executed
within the specified time value and bail with the hits accumulated up to
that point when expired. Defaults to no timeout.

With that I'm expecting every query to be under (or roughly) around 2
second, but not 5 or 10 seconds.

Am I doing something wrong, or is it really and ES issue ?

--

--

Facets are implemented with FacetCollectors, which means they are computed
at search time. The TimeLimitingCollector is a simple wrapper around the
collectors that do the real work. The same goes for sorting, although there
has to be logic during the reduce phase that resorts and aggregates facets.

--
Ivan

On Thu, Jan 3, 2013 at 9:49 AM, Jérôme Gagnon jerome.gagnon.1@gmail.comwrote:

Possibly because I use a lot of facetting on the same query ? Facetting
and sorting is done on the reduce phase if I'm not wrong ?

On Thursday, January 3, 2013 12:28:40 PM UTC-5, Ivan Brusic wrote:

I have seen this issue pop up on the mailing list every now and then.
The timeout value is used only by the TimeLimitingCollector, so it only
limits the time used by Lucene in collecting documents. The
parsing/gather/reduce phases all lie outside of this time interval.
However, I would find it strange that something like the reduce phase would
take so long.

For the record, I have the same issue.

--
Ivan

On Thu, Jan 3, 2013 at 8:47 AM, Jérôme Gagnon jerome....@gmail.comwrote:

This is what I'm doing in the Java API for search;
https://gist.github.com/**4444788 https://gist.github.com/4444788

And even if I put a 2 sec timeout, I have often requests that take more
than 5 and even 10 seconds that does not time out. But sometime, I have
some query that take under 2 sec and says timed out.

On the documentation it says;
timeout A search timeout, bounding the search request to be executed
within the specified time value and bail with the hits accumulated up to
that point when expired. Defaults to no timeout.

With that I'm expecting every query to be under (or roughly) around 2
second, but not 5 or 10 seconds.

Am I doing something wrong, or is it really and ES issue ?

--

--

--

Hi Jérôme ,

It's a known ES issue.

Otis

Solr & ElasticSearch Support

On Thursday, January 3, 2013 11:47:08 AM UTC-5, Jérôme Gagnon wrote:

This is what I'm doing in the Java API for search;
https://gist.github.com/4444788

And even if I put a 2 sec timeout, I have often requests that take more
than 5 and even 10 seconds that does not time out. But sometime, I have
some query that take under 2 sec and says timed out.

On the documentation it says;
timeout A search timeout, bounding the search request to be executed
within the specified time value and bail with the hits accumulated up to
that point when expired. Defaults to no timeout.

With that I'm expecting every query to be under (or roughly) around 2
second, but not 5 or 10 seconds.

Am I doing something wrong, or is it really and ES issue ?

--

Hi Otis,

Is there a solution for this? More importantly, is there a fix for
ElasticSearch 0.90.0 release?

Thanks,
Connie

On Thursday, January 3, 2013 11:05:50 AM UTC-8, Otis Gospodnetic wrote:

Hi Jérôme ,

It's a known ES issue.

Otis

Solr & ElasticSearch Support
http://sematext.com/

On Thursday, January 3, 2013 11:47:08 AM UTC-5, Jérôme Gagnon wrote:

This is what I'm doing in the Java API for search;
https://gist.github.com/4444788

And even if I put a 2 sec timeout, I have often requests that take more
than 5 and even 10 seconds that does not time out. But sometime, I have
some query that take under 2 sec and says timed out.

On the documentation it says;
timeout A search timeout, bounding the search request to be executed
within the specified time value and bail with the hits accumulated up to
that point when expired. Defaults to no timeout.

With that I'm expecting every query to be under (or roughly) around 2
second, but not 5 or 10 seconds.

Am I doing something wrong, or is it really and ES issue ?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Connie,

No, I don't think there were changes around timeouts in 0.90 release.

Otis

ELASTICSEARCH Performance Monitoring - http://sematext.com/spm/index.html
Search Analytics - http://sematext.com/search-analytics/index.html

On Monday, May 20, 2013 6:34:07 PM UTC-4, Connie Yang wrote:

Hi Otis,

Is there a solution for this? More importantly, is there a fix for
ElasticSearch 0.90.0 release?

Thanks,
Connie

On Thursday, January 3, 2013 11:05:50 AM UTC-8, Otis Gospodnetic wrote:

Hi Jérôme ,

It's a known ES issue.

Otis

Solr & ElasticSearch Support
http://sematext.com/

On Thursday, January 3, 2013 11:47:08 AM UTC-5, Jérôme Gagnon wrote:

This is what I'm doing in the Java API for search;
https://gist.github.com/4444788

And even if I put a 2 sec timeout, I have often requests that take more
than 5 and even 10 seconds that does not time out. But sometime, I have
some query that take under 2 sec and says timed out.

On the documentation it says;
timeout A search timeout, bounding the search request to be executed
within the specified time value and bail with the hits accumulated up to
that point when expired. Defaults to no timeout.

With that I'm expecting every query to be under (or roughly) around 2
second, but not 5 or 10 seconds.

Am I doing something wrong, or is it really and ES issue ?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.