GoTime has Elasticsearch in production. We are currently using it to
index pageview analytics as a trial while we prepare other code that
uses it.
Our current index has 6.5 million documents with around 25 fields
each. Future plans are for multiple indices each with 4-5 million
complex nested documents.
We have 3 c1.xlarge instances on ec2 running both cassandra and
elasticsearch. Cpu usage is very low but load stays around the 6-8
range, so we are using the 8-core instances for now. We are using the
S3 gateway but haven't had any restore scenarios yet. In our testing,
recovery of large indices from S3 has not been promising, so we are
looking forward to the reuse of work directories feature that is being
worked on. To be fair, the recovery testing was done with 0.7.2, and I
understand the gateway format has changed since then.
Another feature that we're looking forward to is the enhanced facet
support, especially histogram facets.
Overall I've been very impressed with Elasticsearch and the pace of
development. Keep up the good work Shay!
Currently, it only lists a link to the site / company that uses it, but I
think the below description you gave is great info as well, so maybe, if you
are going to update the wiki, also add the description?
-shay.banon
On Tue, Jun 29, 2010 at 12:39 AM, Grant Rodgers grantr@gmail.com wrote:
GoTime has Elasticsearch in production. We are currently using it to
index pageview analytics as a trial while we prepare other code that
uses it.
Our current index has 6.5 million documents with around 25 fields
each. Future plans are for multiple indices each with 4-5 million
complex nested documents.
We have 3 c1.xlarge instances on ec2 running both cassandra and
elasticsearch. Cpu usage is very low but load stays around the 6-8
range, so we are using the 8-core instances for now. We are using the
S3 gateway but haven't had any restore scenarios yet. In our testing,
recovery of large indices from S3 has not been promising, so we are
looking forward to the reuse of work directories feature that is being
worked on. To be fair, the recovery testing was done with 0.7.2, and I
understand the gateway format has changed since then.
Another feature that we're looking forward to is the enhanced facet
support, especially histogram facets.
Overall I've been very impressed with Elasticsearch and the pace of
development. Keep up the good work Shay!
Currently, it only lists a link to the site / company that uses it, but I
think the below description you gave is great info as well, so maybe, if you
are going to update the wiki, also add the description?
-shay.banon
On Tue, Jun 29, 2010 at 12:39 AM, Grant Rodgers gra...@gmail.com wrote:
GoTime has Elasticsearch in production. We are currently using it to
index pageview analytics as a trial while we prepare other code that
uses it.
Our current index has 6.5 million documents with around 25 fields
each. Future plans are for multiple indices each with 4-5 million
complex nested documents.
We have 3 c1.xlarge instances on ec2 running both cassandra and
elasticsearch. Cpu usage is very low but load stays around the 6-8
range, so we are using the 8-core instances for now. We are using the
S3 gateway but haven't had any restore scenarios yet. In our testing,
recovery of large indices from S3 has not been promising, so we are
looking forward to the reuse of work directories feature that is being
worked on. To be fair, the recovery testing was done with 0.7.2, and I
understand the gateway format has changed since then.
Another feature that we're looking forward to is the enhanced facet
support, especially histogram facets.
Overall I've been very impressed with Elasticsearch and the pace of
development. Keep up the good work Shay!
Currently, it only lists a link to the site / company that uses it, but I
think the below description you gave is great info as well, so maybe, if you
are going to update the wiki, also add the description?
-shay.banon
On Tue, Jun 29, 2010 at 12:39 AM, Grant Rodgers gra...@gmail.com wrote:
GoTime has Elasticsearch in production. We are currently using it to
index pageview analytics as a trial while we prepare other code that
uses it.
Our current index has 6.5 million documents with around 25 fields
each. Future plans are for multiple indices each with 4-5 million
complex nested documents.
We have 3 c1.xlarge instances on ec2 running both cassandra and
elasticsearch. Cpu usage is very low but load stays around the 6-8
range, so we are using the 8-core instances for now. We are using the
S3 gateway but haven't had any restore scenarios yet. In our testing,
recovery of large indices from S3 has not been promising, so we are
looking forward to the reuse of work directories feature that is being
worked on. To be fair, the recovery testing was done with 0.7.2, and I
understand the gateway format has changed since then.
Another feature that we're looking forward to is the enhanced facet
support, especially histogram facets.
Overall I've been very impressed with Elasticsearch and the pace of
development. Keep up the good work Shay!
Currently, it only lists a link to the site / company that uses it, but I
think the below description you gave is great info as well, so maybe, if you
are going to update the wiki, also add the description?
-shay.banon
On Tue, Jun 29, 2010 at 12:39 AM, Grant Rodgers gra...@gmail.com wrote:
GoTime has Elasticsearch in production. We are currently using it to
index pageview analytics as a trial while we prepare other code that
uses it.
Our current index has 6.5 million documents with around 25 fields
each. Future plans are for multiple indices each with 4-5 million
complex nested documents.
We have 3 c1.xlarge instances on ec2 running both cassandra and
elasticsearch. Cpu usage is very low but load stays around the 6-8
range, so we are using the 8-core instances for now. We are using the
S3 gateway but haven't had any restore scenarios yet. In our testing,
recovery of large indices from S3 has not been promising, so we are
looking forward to the reuse of work directories feature that is being
worked on. To be fair, the recovery testing was done with 0.7.2, and I
understand the gateway format has changed since then.
Another feature that we're looking forward to is the enhanced facet
support, especially histogram facets.
Overall I've been very impressed with Elasticsearch and the pace of
development. Keep up the good work Shay!
Currently, it only lists a link to the site / company that uses it, but I
think the below description you gave is great info as well, so maybe, if you
are going to update the wiki, also add the description?
-shay.banon
On Tue, Jun 29, 2010 at 12:39 AM, Grant Rodgers gra...@gmail.com wrote:
GoTime has Elasticsearch in production. We are currently using it to
index pageview analytics as a trial while we prepare other code that
uses it.
Our current index has 6.5 million documents with around 25 fields
each. Future plans are for multiple indices each with 4-5 million
complex nested documents.
We have 3 c1.xlarge instances on ec2 running both cassandra and
elasticsearch. Cpu usage is very low but load stays around the 6-8
range, so we are using the 8-core instances for now. We are using the
S3 gateway but haven't had any restore scenarios yet. In our testing,
recovery of large indices from S3 has not been promising, so we are
looking forward to the reuse of work directories feature that is being
worked on. To be fair, the recovery testing was done with 0.7.2, and I
understand the gateway format has changed since then.
Another feature that we're looking forward to is the enhanced facet
support, especially histogram facets.
Overall I've been very impressed with Elasticsearch and the pace of
development. Keep up the good work Shay!
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.