Elasticsearch : Need advice on architectural design of my cluster

I am quite new to elasticsearch. I need to build a search system using the data from MongoDB. So, here is a high level overview of my application: - There are different users belonging to different organizations - A User can upload multiple datasets. Each dataset is stored as a

Re: Aging strategy described in the ES website's Retiring Data document isn't working for me

Thanks Mark for pointing out the first part about not needing the close/open. I must have picked those up while fooling around trying to affect the correct behavior. I originally followed the post I mentioned, which did not have the close/open. For the second pointI want a replica of

boosting with another field

Hi! I have a text fields used for fts, and I have an integer field used at search operation for sorting.That is I use _score as the first soring field and that integer field as the second one. Is it possible to use this integer field on the indexing operation with the aim to get natural

Re: GIS Query not working on ES as expected

I think I figured out what's going on, see the github issue. -P On Sunday, 28 December 2014 05:21:07 UTC, AndyGIS wrote: Filed https://github.com/elasticsearch/elasticsearch/issues/9079 FYI! On Saturday, December 27, 2014 9:07:50 PM UTC-8, AndyGIS wrote: What i have is a simple test case

Client.setTimeout(millis) does not seem to work ( unlike ActionFuture.actionGet(millis) )

Hi, our cluster has been experiencing some query timeouts which we originally attributed to GC issues. We resolved those but we still have timeouts. *Question 1:* We increased the timeout value in the search builder's action future. We did this by setting the future task's timeout value as

Re: elasticsearch index plan

It is the default configuration that Elasticsearch uses all nodes, if you configure the shard number of an index to the number of nodes you have. I am not familiar with Flume but Elasticsearch is not the bottleneck if configured carefully. You must check your I/O subsystem for the write load.

Re: [ANN] Elasticsearch RDF Jena Plugin

Great idea! Need a clarification. All of the java source files I opened say Apache license, but the readme says AGPL. Which license is it? On Sun, Dec 28, 2014 at 12:01 PM, joergpra...@gmail.com joergpra...@gmail.com wrote: Hi, do you want to turn your Elasticsearch into a SPARQL

Re: [ANN] Elasticsearch RDF Jena Plugin

HI great news!! :-) nice work, as well as the plugin from Gazzarini on Solr! :-) I can't wait to seriously play a little with both... :-) Have you already done some tests on the triples? I mean: is it possible to use the ES replication to provide triples to other nodes, query on multiple nodes

Re: [ANN] Elasticsearch RDF Jena Plugin

Apache - sorry for the README mistake, will be fixed. Jörg On Sun, Dec 28, 2014 at 9:19 PM, Jack Park jackp...@topicquests.org wrote: Great idea! Need a clarification. All of the java source files I opened say Apache license, but the readme says AGPL. Which license is it? On Sun, Dec

Re: [ANN] Elasticsearch RDF Jena Plugin

With this RDF Jena plugin, you can set up indices like any other index, only the mapping is kind of strict: https://github.com/jprante/elasticsearch-plugin-rdf-jena/blob/master/src/main/resources/org/xbib/elasticsearch/module/rdf/jena/mapping.json That means, with replica settings, triples (like

Re: Elasticsearch gets unresponsive with logstash

Hello, sorry for the incomplete information I'm kinda new to elasticsearch. - In our setup we have 2x elasticsearch data/client nodes and 4 logstash instances just seen as clients. - both elsaticsearch servers have 32 GB memory and the heap is 8GB -Xms8g -Xmx8g -Xss256k - 150