Re: Using ElasticSearch for exploratory data analysis

Hello Nick, I would love to hear some feedback on how did you go forward and whether elasticsearch was the tool for the job and if not why. Thanks On Thursday, February 13, 2014 at 3:02:02 AM UTC+1, Nick C wrote: We are building an app to help us keep track of user behaviour on site,

AvgFieldLength seem wrong

I am running an index with bm25 similarity over a field named title. When I (manually) calculate the teh average field length I find ~10.2 However when I use elastic search explain I get much smaller. This ruins the score expected calculation Any clue what goes wrong ? *Example of the result:*

Re: Memory usage of the machine with ES is continuously increasing

I have straced elasticsearch for a couple of minutes strace -fp PID -o file.txt out of the 40k+ events recorded 2.2k + events have resulted in errors like this https://gist.github.com/vanga/55ca296f737b3c1fb9a2 I think this is the reason for the dentry bloating, though I am not sure if there is

Elasticsearch lareg heap usage.

Hi, running... ES 1.5.2 Java 1.8_45 Windows 2008 4 nodes of: 32 cores 128GB 5 TB SSDs (each) ES_HEAP_SIZE configured to 30g I just finished bulk indexing 350,000,000 records but all 4 nodes are consumming 60% heap usage and not collecting. I have your kit running on 1 node and I tried

Elk + ruby + syslog plugins

I've installed the syslog plugins (input, filter, output) using gem. What I don't seem to be able to do is to make logstash use them. I suspect it has something to do with using ruby from within logstash, but I've not managed to get it to work. Does anyone have a working logstash

Elastic search CRUD function only working in debug mode

2 issues are there: 1.Elastic search CRUD function only working in debug mode, not in normal mode.(while running in eclipse debug mode) Or else if we put Thread .sleep(5000),then also it is working(without debug mode) but impact the performance. . 2.Allowing only to add upto 10 records.If try

[ANN] Elasticsearch AWS cloud plugin 2.4.2 released

Heya, We are pleased to announce the release of the Elasticsearch AWS cloud plugin, version 2.4.2. The Amazon Web Service (AWS) Cloud plugin allows to use AWS API for the unicast discovery mechanism and add S3 repositories.. https://github.com/elasticsearch/elasticsearch-cloud-aws/ Release

elasticsearch curator 3.0.3: option --older-than

I have installed the last curator and unfortunately, my old command is not supported: # curator --version curator, version 3.0.3 # curator delete --older-than 1 --prefix .marvel- Error: no such option: --older-than It seems that option --older-than is not supported but mentioned in CHANGELOG.

Re: elasticsearch curator 3.0.3: option --older-than

Try curator --host localhost delete indices --older-than 1 --time-unit days --prefix .marvel --timestring %Y.%m.%d PS - We're moving to https://discuss.elastic.co/, please join us there for any future discussions! On 21 May 2015 at 06:58, Jean-Max Reymond jmreym...@gmail.com wrote: I have

[ANN] Elasticsearch AWS cloud plugin 2.5.1 released

Heya, We are pleased to announce the release of the Elasticsearch AWS cloud plugin, version 2.5.1. The Amazon Web Service (AWS) Cloud plugin allows to use AWS API for the unicast discovery mechanism and add S3 repositories.. https://github.com/elastic/elasticsearch-cloud-aws/ Release Notes

Re: elasticsearch curator 3.0.3: option --older-than

It works nicely Thanks a lot Le mercredi 20 mai 2015 22:58:05 UTC+2, Jean-Max Reymond a écrit : I have installed the last curator and unfortunately, my old command is not supported: # curator --version curator, version 3.0.3 # curator delete --older-than 1 --prefix .marvel- Error: no

Re: Lots of segments per index

It merges segments in response to indexes and updates so an index that doesn't change will not have merges. You can manually optimize the index once, when it is mostly done with updates. Once the index is optimized further calls to optimize with the same parameters are noops. You can't really ads

Lots of segments per index

Hi All, We have monthly indexes (currently 11 months) with 22 shards per index. I am seeing what seems to be a lot of segments per index (roughly 1200 to 1380 segments). The older indexes should have very little, if any updates occurring on them. From everything I have read it sounds like

Multi_Match filter by _type?

I have an index created by the JDBC river that contains types of objects: Orders, Accounts etc. If I execute the boosted multimatch query below I get back 50 of each type of result. All is well. However I'm trying to give the option to filter the list by user control and lets say i only want

Re: JDBC River missing documents??

Found a defect in the prior stored procedure. If new data is being added while the index is being created and after it already did the current month it will go back in time forever. Subsequently never getting to the point where it will start indexing the newer modified or created as it