Hi Adrien, I'm using OSX (Mavericks) and java: (having the issue)
$ java -version java version "1.7.0_25" Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode) My colleague is running OSX (Lion) and java: (having the issue) $ java -version java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03-383-11D50) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-383, mixed mode) A server soon to be used for production Ubuntu 12.04 LTS with java: (Not having the issue) $ java -version java version "1.7.0_45" Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) Could this be an issue with java on OSX than? On Wednesday, February 5, 2014 4:38:36 PM UTC+1, Adrien Grand wrote: > > I didn't manage to reproduce the issue locally either. What JVM / OS are > you using (RC1 introduced Unsafe to perform String comparisons in terms > aggs so I'm wondering if that could be related to your issue)? > > > On Wed, Feb 5, 2014 at 4:33 PM, Nils Dijk <[email protected] <javascript:>>wrote: > >> I did only test it with 1 and with 10 shards, indeed with 1 shard it did >> not have any issues, with 10 shards it has issues all the time. >> I also had a colleague testing it with the two scripts in the gist (which >> uses 10 shards). >> >> Also I do not think the analyzer _should_ have impact, since it would >> only index more terms on that field if it tokenizes it. Can you use the >> aggsbug.load.sh to load the data? And than use aggsbug.test.sh to run >> the test? It should give you a field analyzed with the default analyzer and >> 10 shards. >> >> I'll try out some different analyzers, and loading the data in 3 shards >> now to see if that changes things. >> >> On Wednesday, February 5, 2014 4:02:54 PM UTC+1, Jörg Prante wrote: >>> >>> Also the same with shards = 3 and analyzer = standard. Stable results. >>> >>> { >>> "took" : 240, >>> "timed_out" : false, >>> "_shards" : { >>> "total" : 3, >>> "successful" : 3, >>> "failed" : 0 >>> }, >>> "hits" : { >>> "total" : 1060387, >>> "max_score" : 0.0, >>> "hits" : [ ] >>> }, >>> "aggregations" : { >>> "a" : { >>> "buckets" : [ { >>> "key" : "totaltrafficbos", >>> "doc_count" : 3599 >>> }, { >>> "key" : "mai93thm", >>> "doc_count" : 2517 >>> }, { >>> "key" : "mai90thm", >>> "doc_count" : 2207 >>> }, { >>> "key" : "mai95thm", >>> "doc_count" : 2207 >>> }, { >>> "key" : "totaltrafficnyc", >>> "doc_count" : 1660 >>> }, { >>> "key" : "confessions", >>> "doc_count" : 1534 >>> }, { >>> "key" : "incidentreports", >>> "doc_count" : 1468 >>> }, { >>> "key" : "nji80thm", >>> "doc_count" : 1180 >>> }, { >>> "key" : "pai76thm", >>> "doc_count" : 1142 >>> }, { >>> "key" : "txi35thm", >>> "doc_count" : 379 >>> } ] >>> } >>> } >>> } >>> >>> You should examine your log files if your ES cluster was able to process >>> all the docs correctly while indexing or searching, maybe you encountered >>> OOMs or other subtle issues. >>> >>> Jörg >>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/7c74c649-8a4a-46c5-aaec-b6f3254cc0d9%40googlegroups.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Adrien Grand > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8f0f80b7-fbf2-4747-90d4-725a06560938%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
