I added an optimization in match_all cases (including query string
like :), but, that optimization has resulted in excessive processing
in some cases. Easily fixable while still maintaing the optimization.
I have created a branch for 0.12 on github with the fix:
http://github.com/elasticsearch/elasticsearch/tree/0.12. I will
release 0.12.1 pretty soon (likely today) as this is a major
regression. Can you give it a go?
Can I restart one node at a time?
Also, does this affect constant_score as well as match_all?
On Tue, Oct 26, 2010 at 9:47 AM, Paul firstname.lastname@example.org wrote:
I can confirm that this is the only slow down we have run
pumped millions of real world queries through since, mostly
of complex nested fielded boolean queries sorted by date and
no other performance differences. I'm definitely only touching
fraction of the search functionality, though.
On Oct 25, 10:51 pm, Clinton Gormley <clin...@iannounce.co.uk>
> On Mon, 2010-10-25 at 16:58 -0700, Paul wrote:
> > Further update, by removing the unseeded *:* I have
> > search times are blazing again.
> Paul - please keep an eye out for other slowdowns - I am
> very slow responses on 0.12 for queries which were working
> Web Announcements Limited is a company registered in England
> with company number 05608868, with registered address at 10
> London, N5 1PR.
Web Announcements Limited is a company registered in England and Wales,
with company number 05608868, with registered address at 10 Arvon Road,
London, N5 1PR.