Thanks for the link. I guess my problem is the deprecation of a feature
like this because of a use case where performance takes priority over
infrastructure. While that may suit many (most?) users of ES, we don't have
any issues with the performance of ES when using an S3 gateway, and the
convenience of using it as a backup is unrivaled compared to an API.
So, there is no technical reason for deprecating the S3 gateway, just that
the necessary IO to an external storage system carries with it an implication
of performance degradation that may impact some use cases?
I'm thankful that the shared gateway should be able to be maintained in a
separate project, but isn't the option for an integrated data backup
solution that survives cluster shutdown important enough to remain for
those use cases where ES is the main source of truth.
Perhaps kimchy's assertion that using the shared gateway as a backup
solution is a misuse of the feature is what I don't fully understand. We
embed ES as our only data persistence into a running web application. We
run on EC2 instances which are under the control of Elastic Beanstalk.
There are no EBS volumes to snapshot. We use S3 gateway to recover after
full cluster shutdowns (version upgrades to our software). I agree that
this is an unusual way of using ES as most people deploy ES as a server
unto itself, but the advantages it gives us in dynamically shrinking and
growing our cluster capacity is unrivaled because everything is self
contained in the web app. I can run 1 server or 100 servers with the exact
same WAR file deployed, and Amazon decides when to tear down or start up
new servers solely by monitoring metrics. It's may seem a bit strange but
it is also a beautiful thing to watch.
Jim Cook
jcook@pykl.com
Pykl Studios http://pykl.com/ (map) http://goo.gl/maps/ceMDN
147 N High St
Gahanna, OH 43230
phone+1 614 398 3636 tollfree+1 855 FOR PYKL skypejcook.pykl im (gtalk)
jcook@pykl.com
On Tue, Feb 26, 2013 at 10:41 AM, Jörg Prante joergprante@gmail.com wrote:
It is explained by kimchy here https://github.com/**
elasticsearch/elasticsearch/**issues/2458https://github.com/elasticsearch/elasticsearch/issues/2458
Jörg
--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/**
topic/elasticsearch/G_**WFPEFf0ZY/unsubscribe?hl=en-UShttps://groups.google.com/d/topic/elasticsearch/G_WFPEFf0ZY/unsubscribe?hl=en-US
**.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@**googlegroups.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.
--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.