It is correct you noted that Elasticsearch comes with developer settings - that is exactly what a packages ES is meant for.
If you find issues when configuring and setting up ES for critical use, it would be nice to post your issues so others can also find help too, and maybe share their solutions , because there are ES installations that run successfully in critical environments. By just quoting "hate" of dev teams, it is rather impossible for me to learn about the reason why this is so. Learning facts is more important than emotions to fix software issues. The power of open source is that such issues can be fixed by the help of a public discussion in the community. In closed software products, you can not rely on issues being discussed publicly for best solutions how to fix them. Jörg On Thu, Jun 19, 2014 at 2:48 PM, Thomas Paulsen <monokit2...@googlemail.com> wrote: > We had a 2,2TB/d installation of Splunk and ran it on VMWare with 12 > Indexer and 2 Searchheads. Each indexer had 1000IOPS guaranteed assigned. > The system is slow but ok to use. > > We tried Elasticsearch and we were able to get the same performance with > the same amount of machines. Unfortunately with Elasticsearch you need > almost double amount of storage, plus a LOT of patience to make is run. It > took us six months to set it up properly, and even now, the system is quite > buggy and instable and from time to time we loose data with Elasticsearch. > > I don´t recommend ELK for a critical production system, for just dev work, > it is ok, if you don´t mind the hassle of setting up and operating it. The > costs you save by not buying a splunk license you have to invest into > consultants to get it up and running. Our dev teams hate Elasticsearch and > prefer Splunk. > > Am Samstag, 19. April 2014 00:07:44 UTC+2 schrieb Mark Walkom: >> >> That's a lot of data! I don't know of any installations that big but >> someone else might. >> >> What sort of infrastructure are you running splunk on now, what's your >> current and expected retention? >> >> Regards, >> Mark Walkom >> >> Infrastructure Engineer >> Campaign Monitor >> email: ma...@campaignmonitor.com >> web: www.campaignmonitor.com >> >> >> On 19 April 2014 07:33, Frank Flynn <faultle...@gmail.com> wrote: >> >>> We have a large Splunk instance. We load about 1.25 Tb of logs a day. >>> We have about 1,300 loaders (servers that collect and load logs - they may >>> do other things too). >>> >>> As I look at Elasticsearch / Logstash / Kibana does anyone know of a >>> performance comparison guide? Should I expect to run on very similar >>> hardware? More? or Less? >>> >>> Sure it depends on exactly what we're doing, the exact queries and the >>> frequency we'd run them but I'm trying to get any kind of idea before we >>> start. >>> >>> Are there any white papers or other documents about switching? It seems >>> an obvious choice but I can only find very little performance comparisons >>> (I did see that Elasticsearch just hired "the former VP of Products at >>> Splunk, Gaurav Gupta" - but there were few numbers in that article either). >>> >>> Thanks, >>> Frank >>> >>> -- >>> 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 elasticsearc...@googlegroups.com. >>> >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/elasticsearch/ea1a338b-5b44-485d-84b2-3558a812e8a0% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/elasticsearch/ea1a338b-5b44-485d-84b2-3558a812e8a0%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/32c23e38-2a2f-4c09-a76d-6a824edb1b85%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/32c23e38-2a2f-4c09-a76d-6a824edb1b85%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGtte%3DRWjZCNtBWcX5y4Z9j7yXpyXC5MWdzpqubtCce5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
