Karel Minarik

The state of things in Tire regarding this is messy right now. Will leave it open as a reminder.

Hi, sorry for the delay. **tl;dr: yes, it's probably a useful feature for `tire-contrib` and EC2 will eventually force us to implement it** This is something which has been debated...

Yes, definitely makes sense, that's the vision I have, and close to what I have described above, thanks for chiming in, @kimchy. I'm still unsure about the precise mechanics --...

@clintongormley Hi, sorry for the delay with the response, Clint! What you're saying makes perfect sense, and I was thinking that maybe keeping track of some counter and issuing cluster...

No updates yet -- I guess putting a proxy in front of ES if you're interested in high availability makes sense for now.

@mkdynamic The best solution would be to use a real proxy, such as HProxy, Nginx, etc. You can use Nginx as a round-robin proxy with keepalive pretty easy, see eg....

I wouldn't describe Nginx-based proxy to have "obviously potential performance and cost downsides". But yes, every proxy would be a "single point of failure", though I'd hesitate to describe it...

Hello, the Tire gem is truly retired, and the development is frozen when it comes to adding features. Please have a look at the new https://github.com/elastic/elasticsearch-ruby and https://github.com/elastic/elasticsearch-rails gems...

@brightbits I like the suggestion, there's an issue or two already opened for this. This would be easy to handle -- just `delete` the setting from mapping and conditionally perform...

@sgringwe I think the right way would be to create the index+alias(es) in advance, then the automatic behaviour doesn't kick in. I'm afraid the behaviour in the gem won't be...