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
; Health Market Science | 2700 Horizon Drive | King of Prussia, PA 19406
> p: 215.588.6024
> blog: http://weblogs.java.net/blog/boneill42/
> blog: http://brianoneill.blogspot.com/
>
>
>
> From: Anthony Ikeda
> Reply-To:
> Date: Tue, 18 Oct 2011 14:18:17 -0700
> To:
> Subject
t; Lead Architect, Software Development
> Health Market Science | 2700 Horizon Drive | King of Prussia, PA 19406
> p: 215.588.6024
> blog: http://weblogs.java.net/blog/boneill42/
> blog: http://brianoneill.blogspot.com/
>
>
>
> From: Anthony Ikeda
> Reply-To:
> D
:
Date: Tue, 18 Oct 2011 14:18:17 -0700
To:
Subject: Re: Using elasticsearch on cassandra nodes
At the moment we are only prototyping so we haven't bridged the two at all.
We had planned on creating a write-through operation that allowed us to
filter the calls (AOP perhaps?) to man
At the moment we are only prototyping so we haven't bridged the two at all.
We had planned on creating a write-through operation that allowed us to
filter the calls (AOP perhaps?) to manage the indexing as we stored it in
Cassandra.
We are still trying to work out if we go the elastic search route
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
