embedded in ES without node restart.
A restartable plugin is:
https://github.com/jprante/elasticsearch-plugin-ratpack
Jörg
On Thu, Jan 8, 2015 at 5:24 PM, Radu Gheorghe radu.gheor...@sematext.com
wrote:
Hello Ben,
Maybe it works if you uninstall the plugin from one node at a time and do
://sematext.com/
On Fri, Jan 9, 2015 at 10:20 AM, joergpra...@gmail.com
joergpra...@gmail.com wrote:
No I didn't :(
I still struggle with stateful plugins - there is no good solution I know
of and that is the reason of trouble.
Jörg
On Fri, Jan 9, 2015 at 9:01 AM, Radu Gheorghe radu.gheor
, Paresh Behede paresh2...@gmail.com wrote:
Thank you so much Rodu...solution worked for me...
Regards,
Paresh B.
On Thursday, 8 January 2015 21:11:47 UTC+5:30, Radu Gheorghe wrote:
Thanks, David! I had no idea it works until... about one hour ago :)
--
Performance Monitoring * Log Analytics
Hello,
The search threadpool size (that is, how many requests can be actually
worked on at once) defaults to 3 times the number of processors. This might
be reduced in future, though, see:
https://github.com/elasticsearch/elasticsearch/pull/9165
The queue size (how many requests ES can accept
Hello Phani,
Usually the dedicated masters are much smaller than the data nodes, because
they have much less work to do. If the 4 nodes you're talking about are
equal, it might be inefficient to add a 5th so you can have 2 data and 3
master nodes. Maybe for the same budget of adding the 5th you
You're welcome.
So you're saying you're running 5 searches on a single index with 5 shards
(25 per-shard queries in total) and you're getting an error? I assume that
error doesn't say the queue is full because the queue is 1000. Can you post
the full error and also a gist where you reproduce the
Hi Paresh,
If you want to sort on the field, I think it has to be the same type. So if
you make everything a double, it should work for all numeric fields. To do
that, you can use dynamic templates
OK, now it makes sense. 5 requests with 320 shards might saturate your
queue.
But 320 shards sounds like a lot for one index. I assume you don't need to
scale that very index to 320 nodes (+ replicas). If you can get the number
of shards down (say, to the default of 5) things will surely look
Hello Ben,
Maybe it works if you uninstall the plugin from one node at a time and do a
rolling restart (sticking to 1.3.2), then do the upgrade with another
rolling restart, then install the plugin back again with yet another
rolling restart?
I would understand if you said no way I do 3
Hello,
I assume you query lots of shards/indices? If not, then it might just be
that ES is overloaded with that many requests and you have to add nodes.
If yes, you'll can increase the queue size of the search thread pool.
Something like:
curl -XPUT localhost:9200/_cluster/settings -d '{
Hi Amit,
You'll probably need to use a multi field
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_multi_fields.html
(one with standard analyzer, one with keyword analyzer). This should return
the string on:
message:string
and
message.raw:this.*string
Best regards,
Radu
Hi Elasticsearch list :)
I'm having some trouble while running Elasticsearch on r3.large (HVM
virtualization) instances in AWS. The short story is that, as soon as I put
any significant load on them, some requests take a very long time (for
example, Indices Stats) and I see disconnected/timeout
, 2014 at 9:57 PM, Mohit Anchlia mohitanch...@gmail.comwrote:
What's not clear is how does elasticsearch identify what pieces of data is
missing between the primary and the replica?
On Wed, Apr 30, 2014 at 3:27 AM, Radu Gheorghe radu.gheor...@sematext.com
wrote:
Hi Mohit,
I'll answer inline
foils shaver -- 1 word distance + 1 plural
5. men's foil advanced shaver -- 2 word distance
4. norelco men's foil advanced shaver -- 2 word distance
Why higher distance document scored higher?
Is there any problem with stemmer or nGram settings?
On Thursday, May 1, 2014 7:26:02 AM UTC-4, Radu
Hi Kruti,
The short answer is yes, it is possible. Here's one way to do it:
Have the fields you search on as multi
fieldhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_multi_fields.html,
where you index them with various settings, like once not-analyzed for
exact matches,
Hello,
Using _source for scripts is typically slow, because ES has to go to each
stored document and extract fields from there. A faster approach is to use
something like doc['field3'].values[12], which will used the field data
cache (already loaded in memory, at least after the first run):
Hello,
Normally, you would send indexing requests to the REST API with the stuff
you want Elasticsearch to index:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/docs-index_.html
If you want Elasticsearch to automatically fetch files from the file system
for you, have a
UTC+2, Radu Gheorghe a écrit :
Hello,
One way to do it would be to store all those IDs in an Elasticsearch
document. Then, you can use the terms filter with the terms lookup
mechanism to have ES fetch all the terms for you:
http://www.elasticsearch.org/guide/en/elasticsearch/
reference
Hi Alexey,
Your message field is analyzed by default using the Standard Analyzer:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-standard-analyzer.html
This means your test message will become [test, message].
On the other hand, the prefix query isn't analyzed.
You're welcome :)
On Thu, Apr 24, 2014 at 10:16 AM, Dominic Gross dvgro...@gmail.com wrote:
Thats awesome, thank you for your help!
Am Donnerstag, 24. April 2014 09:10:10 UTC+2 schrieb Radu Gheorghe:
You can do that, too, yes.
On Thu, Apr 24, 2014 at 10:08 AM, Dominic Gross dvgr
Hello,
I'm not sure if you're already aware of the predefined _index and _type
fields:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-index-field.html
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-type-field.html
You can enable them
Hello,
What happens if you start ES without any plugin? Do you get the same high
CPU load?
If not, then you can try enabling one plugin at a time and see which one is
the cause. Also, make sure that your plugins match your version. For
example, you seem to need the mongodb river to be version
Hello,
One way to do it would be to store all those IDs in an Elasticsearch
document. Then, you can use the terms filter with the terms lookup
mechanism to have ES fetch all the terms for you:
': 'dark_beer'}]}
Well, I want to concatenate index and type names and pass it to ES facets.
The only way I see is to use `script`, but I don't know how to access
`_index` and `_type` from there.
Thank you for understanding.
On Thu, Apr 24, 2014 at 3:30 PM, Radu Gheorghe radu.gheor
24 matches
Mail list logo
