Hello,
Last year paramedic reported thousands o searches per second (whereas our
regular load are in the hundreds range) this eventually led to an excessive
cpu load across the cluster (4 machines). Not more than a month later the
same thing happened. We updated to ES 0.90.12 at the time,
On 10 August 2014 02:24, Rafael Almeida almeida...@gmail.com wrote:
Hello,
Last year paramedic reported thousands o searches per second (whereas our
regular load are in the hundreds range) this eventually led to an excessive
cpu load across the cluster (4 machines). Not more than a month later
Right. Let me elaborate my question, then.
This is my analyzer at first:
test:
type: custom
tokenizer: standard
filter: [standard]
$ curl -XPUT 'http://localhost:1980/t';echo
{ok:true,acknowledged:true}
$ curl -XPUT
Hello,
I had the following analyzer on my elasticsearch configuration:
teste:
type: custom
tokenizer: standard
filter: [standard]
A field named title uses that analyzer. I indexed ATLÉTICO using it.
Searching for ATLÉTICO works. Searching for
Hello,
Say I have an index called duckling and an alias called duck which points
to duckling and no other index. Except for creating an alias pointing to
duck, all the other operations seem to route directly to duckling. Is that
true? is there something besides creating an alias that I can do
Hello,
I want to know when and if I should manually call optimize on
elasticsearch. This blog seems to say it's a bad idea:
http://gibrown.wordpress.com/2013/01/24/elasticsearch-five-things-i-was-doing-wrong/
However, there must be a reason for optimize to be exposed in the rest api.
[]'s
