Re: now throttling indexing

2015-03-13 Thread Eric Jain
On Fri, Mar 13, 2015 at 6:09 AM, Michael McCandless m...@elastic.co wrote: That is the right setting to disable store throttling, but even without throttling writes MB/sec for merges, the merges can still fall behind, leading to index throttling. ES does this to protect the health of the

now throttling indexing

2015-03-12 Thread Eric Jain
I set `indices.store.throttle.type: none` in the elasticsearch.yml, and yet this shows up in the logs: now throttling indexing: numMergesInFlight=5, maxNumMerges=4 stop throttling indexing: numMergesInFlight=3, maxNumMerges=4 Did I misunderstand the purpose of this setting? -- You

Geohash grid aggregation broken in 1.4.0!

2014-11-17 Thread Eric Jain
If you are using the geohash grid aggregation, and your index can contain documents with more than one value, you may want to hold off migrating to 1.4.0 (see comment at see https://github.com/elasticsearch/elasticsearch/issues/8512)... -- You received this message because you are subscribed

Re: Geohash grid aggregation broken in 1.4.0!

2014-11-17 Thread Eric Jain
On Mon, Nov 17, 2014 at 10:48 AM, Eric Jain eric.j...@gmail.com wrote: If you are using the geohash grid aggregation, and your index can contain documents with more than one value, you may want to hold off migrating to 1.4.0 [...] The correct issue link is https://github.com/elasticsearch

Re: 1.4.0 data node can't join existing 1.3.4 cluster

2014-11-14 Thread Eric Jain
. I ended up starting a new cluster (ignoring all the warnings logged on startup), and restoring from a snapshot. Once all the 1.3.4 nodes were gone, no issues. -- Eric Jain Got data? Get answers at zenobase.com. -- You received this message because you are subscribed to the Google Groups

1.4.0 data node can't join existing 1.3.4 cluster

2014-11-13 Thread Eric Jain
(using elasticsearch-cloud-aws 2.4) This should work, right? Or do I need to upgrade the cluster to 1.3.5 first? The connection fails after a few errors like: 2014-11-13 07:18:22,498 [WARN] org.elasticsearch.discovery.zen.ping.unicast - [Porcupine] failed to send ping to

Re: 1.4.0 data node can't join existing 1.3.4 cluster

2014-11-13 Thread Eric Jain
On Thu, Nov 13, 2014 at 10:05 AM, joergpra...@gmail.com joergpra...@gmail.com wrote: Do not mix 1.3 with 1.4 nodes, it does not work. If that is so, that seems like something the release notes should mention? -- You received this message because you are subscribed to the Google Groups

Re: Replicating TermsFacet functionality with aggregations

2014-08-08 Thread Eric Jain
https://github.com/elasticsearch/elasticsearch/issues/7213 On Thursday, February 13, 2014 3:31:34 PM UTC-8, Adrien Grand wrote: Indeed, I don't think this is possible with aggregations right now. Can you open an issue on Github? On Wed, Feb 12, 2014 at 6:38 PM, Brian Hudson

Register snapshot repositories via config file?

2014-07-25 Thread Eric Jain
Would it make sense to allow snapshot repositories to be registered via the config file? The docs have an example, but it's for running the tests only. repositories: s3: bucket: bucket_name region: us-west-2 -- You received this message because you are subscribed to the

Re: Is this link still applicable on EC2? http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/

2014-07-25 Thread Eric Jain
The S3 Gateway has been dropped, so you'll either need to use EBS, or set up some mechanism to do snapshots to S3. Other than that, no major changes. On Thursday, July 24, 2014 10:12:25 PM UTC-7, vjbangis wrote: Hi, Is this link

Re: elasticsearch 1.1.1 initialization failed

2014-04-18 Thread Eric Jain
This issue has been resolved with cloud-aws 2.1.1: https://github.com/elasticsearch/elasticsearch-cloud-aws/issues/74 On Thursday, April 17, 2014 6:32:05 PM UTC-7, Eric Jain wrote: Just tried to upgrade elasticsearch 1.1.0 to 1.1.1 (with the cloud-aws plugin 2.1.0), and am no longer able

elasticsearch 1.1.1 initialization failed

2014-04-17 Thread Eric Jain
Just tried to upgrade elasticsearch 1.1.0 to 1.1.1 (with the cloud-aws plugin 2.1.0), and am no longer able to start any nodes: 2014-04-18 01:19:42,754 [INFO] node - [Skywalker] version[1.1.1], pid[22901], build[f1585f0/2014-04-16T14:27:12Z] 2014-04-18 01:19:42,767 [INFO] node - [Skywalker]

Re: S3 gateway issues

2014-04-17 Thread Eric Jain
The S3 gateway from the cloud-aws 2.1.0 plugin works fine up to elasticsearch 1.1.0, but appears to be broken with 1.1.1, see my other post. On Friday, April 11, 2014 1:01:34 AM UTC-7, David Pilato wrote: What is the cloud-aws plugin version please? -- *David Pilato* | *Technical

Facets multi-valued, numeric fields

2014-03-13 Thread Eric Jain
For sorting, elasticsearch lets me specify how I want to deal with fields that contain multiple numeric values, so I can have elasticsearch use e.g. the max value in each document. Is there a similar option I can use when aggregating documents? For example, I might want to get the average of

Illegal character in path

2014-03-01 Thread Eric Jain
Just had this error (elasticsearch 1.0.1), don't recall seeing it before: java.net.URISyntaxException: Illegal character in path at index 29: /cache/11_/seg0/index12450141[12450141].ts Should I be concerned? -- You received this message because you are subscribed to the Google Groups