Can you please share your experience of how ES behaves while you have
a huge say 10 TB of data and its stability and the scenario under
which ES is being used by you.
I am trying to collect some success stories of ES and build a document
which supports ES as a solution for search and retrieval for people
who know very little to nothing about ES.
Give me some links from where I can pick up your success stories.
Can you please share your experience of how ES behaves while you have
a huge say 10 TB of data and its stability and the scenario under
which ES is being used by you.
I am trying to collect somesuccessstories of ES and build a document
which supports ES as a solution for search and retrieval for people
who know very little to nothing about ES.
Give me some links from where I can pick up yoursuccessstories.
I can't disclose the users that are indexing 10s of TBs of data into elasticsearch, at least until they will be willing to go public with it, but elasticsearch is used to index this amount of data.
Of course, with those sizes, you need to make sure to run some capacity tests in order to make sure that you are sizing the cluster correctly. Its hard to give "off the shelf" numbers since it depends on many different factors, including size of docs, complexity of them, number of docs, search requirements, and so on.
-shay.banon
On Tuesday, April 19, 2011 at 1:08 PM, Katrina K wrote:
Can you please share your experience of how ES behaves while you have
a huge say 10 TB of data and its stability and the scenario under
which ES is being used by you.
I am trying to collect somesuccessstories of ES and build a document
which supports ES as a solution for search and retrieval for people
who know very little to nothing about ES.
Give me some links from where I can pick up yoursuccessstories.
Can you give the success stories of ES which you would be able to give
some points that you have? So that we would be having some tests on it
and make our servers effective.
I can't disclose the users that are indexing 10s of TBs of data into elasticsearch, at least until they will be willing to go public with it, but elasticsearch is used to index this amount of data.
Of course, with those sizes, you need to make sure to run some capacity tests in order to make sure that you are sizing the cluster correctly. Its hard to give "off the shelf" numbers since it depends on many different factors, including size of docs, complexity of them, number of docs, search requirements, and so on.
-shay.banon
On Tuesday, April 19, 2011 at 1:08 PM, Katrina K wrote:
Can you please share your experience of how ES behaves while you have
a huge say 10 TB of data and its stability and the scenario under
which ES is being used by you.
I am trying to collect somesuccessstories of ES and build a document
which supports ES as a solution for search and retrieval for people
who know very little to nothing about ES.
Give me some links from where I can pick up yoursuccessstories.
it really depends on the type of machines, data, and search, but, I have seen 1700 indices in production each with 1 shard and 1 replica (and some work in upcoming 0.16 has been done to make it even more lightweight) on ~15 nodes cluster. Each index (shard in this case as well) was around 200gb.
On Friday, April 22, 2011 at 2:03 AM, Rich Kroll wrote:
Shay,
Is it possible to disclose the upper bounds on the number of indexes you have seen in production?
Rich
On Apr 19, 2011 6:38 AM, "Shay Banon" shay.banon@elasticsearch.com wrote:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.