Brian,
We've taken the same approach, with ElasticSearch running on the same
nodes as Cassandra.
Make sure you have enough memory on your nodes, because ElasticSearch
and Cassandra both love memory.
We started with 12gb of memory, allocating ElasticSearch and Cassandra
5gb each and it wasn't enough. We ended up upgrading to 48gb of memory,
allocating 15gb to Cassandra, 15gb to ElasticSearch and haven't had any
issues since.
Thanks,
Mike Peters
On 10/18/2011 9:14 AM, Brian O'Neill wrote:
Anthony,
We've been looking at elastic search as well. Presently we have SOLR
in place, but it is cumbersome dealing with SOLR schemas when indexing
information out of Cassandra (since you can't anticipate all the
columns ahead of time).
What are you using as your bridge between Cassandra and ES? Are you
developing a Cassandra river?
-brian
On Mon, Oct 17, 2011 at 5:29 PM, Anthony Ikeda
<anthony.ikeda....@gmail.com <mailto:anthony.ikeda....@gmail.com>> wrote:
I've already posted to the elasticsearch groups and thought it
prudent to also ask here.
We are looking at using elastic search to index our data that
we currently store to Cassandra. I was wondering if there are
any concerns running elastic search on the same nodes that we use
for Cassandra? We have a ring of 6 nodes (2 DCs each with 3 nodes)
I was thinking of installing elastic search on 2 nodes in each
datacentre - maybe all three. The only reason I'd use the same
infrastructure would be because we have the distributed visibility
already in place.
Has anyone else taken this approach? Pros? Cons?
Anthony
--
Brian ONeill
Lead Architect, Health Market Science (http://healthmarketscience.com)
mobile:215.588.6024
blog: http://weblogs.java.net/blog/boneill42/
blog: http://brianoneill.blogspot.com/
