Re: Anyone familiar with Solandra or Lucandra?
This will be possible once triggers are finished for cassandra, then we can hook into CF inserts and auto index in solandra. On Tue, May 17, 2011 at 5:10 PM, kenf_nc wrote: > Ah. I see. That reduces its usefulness to me some. The multi-master aspect > is > still a big draw of course. But I was hoping this also added an integrated > persistence layer to Solr as well. > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Anyone-familiar-with-Solandra-or-Lucendra-tp2927357p2954320.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- http://twitter.com/tjake
Re: Anyone familiar with Solandra or Lucandra?
Ah. I see. That reduces its usefulness to me some. The multi-master aspect is still a big draw of course. But I was hoping this also added an integrated persistence layer to Solr as well. -- View this message in context: http://lucene.472066.n3.nabble.com/Anyone-familiar-with-Solandra-or-Lucendra-tp2927357p2954320.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Anyone familiar with Solandra or Lucandra?
On Tue, May 17, 2011 at 3:07 PM, kenf_nc wrote: > But I can query Cassandra directly for the documents if I wanted/needed to? > > The data is available in the Solandra Keyspace but I wouldn't recommend accessing it directly. Most people who want todo this end up not storing the document fields in Solandra and instead use a unique id to fetch the data from their custom Cassandra CF. > And, when I need to re-index, I could read from Cassandra, index into Solr, > which will write back to Cassandra overwriting the existing document(s)? > > That sounds really strange, but you can use your source data to index back into solandra. but as i mentioned I wouldn't try accessing the data directly from the Solandra keyspace. > Basically the steps would be, index documents into Solr which would write > to > Cassandra. If I need to update a document, I can query it from Solr OR > query > it from Cassandra, make my modification and re-index it back to Solr which > will update Cassandra. If I need to drop my Solr index and completely > recreate it I could read all documents from Cassandra and index them into > the clean Solr instance, which will update (with no change) the documents > in > Cassandra. If I update a document directly in Cassandra without going thru > Solr indexing, the change would show up on a Solr query of that document, > but the search indexes would not reflect any change. Is all that correct? > > Since cassandra scales writes very well I would suggest you index it in solr with stored="false" and also store it in cassandra. If the format of how Solandra stores documents you don't want to have you change your application code. > Also, is index and query performance on par with a Sharded pure Solr > implementation? > > Since writes in Cassandra are durable the performance on writes isn't as fast as Solr's buffered writes on a single node. However since Solandra is multi-master the writes scale well across the cluster. Solandra perform on par with most solr searches one the data is in memory. Most people using Solandra are indexing TBs of data so they are IO bound... -Jake > Thanks for the feedback, > Ken > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Anyone-familiar-with-Solandra-or-Lucendra-tp2927357p2953764.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- http://twitter.com/tjake
Re: Anyone familiar with Solandra or Lucandra?
But I can query Cassandra directly for the documents if I wanted/needed to? And, when I need to re-index, I could read from Cassandra, index into Solr, which will write back to Cassandra overwriting the existing document(s)? Basically the steps would be, index documents into Solr which would write to Cassandra. If I need to update a document, I can query it from Solr OR query it from Cassandra, make my modification and re-index it back to Solr which will update Cassandra. If I need to drop my Solr index and completely recreate it I could read all documents from Cassandra and index them into the clean Solr instance, which will update (with no change) the documents in Cassandra. If I update a document directly in Cassandra without going thru Solr indexing, the change would show up on a Solr query of that document, but the search indexes would not reflect any change. Is all that correct? Also, is index and query performance on par with a Sharded pure Solr implementation? Thanks for the feedback, Ken -- View this message in context: http://lucene.472066.n3.nabble.com/Anyone-familiar-with-Solandra-or-Lucendra-tp2927357p2953764.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Anyone familiar with Solandra or Lucandra?
Hi, Solandra does give you multi-master writes and will even work cross-dc. There are a number of companies in the process of moving to Solandra and the company I work for DataStax has support options for it. But there are few installs in production at the moment. I am hopeful this will change after the next month or two and will start marketing Solandra outside of the github page :) One thing. Solandra does not index documents already in cassandra, it can't at least until trigger are finished in Cassandra (1.0?) So you do need to index the data via solr. -Jake On Thu, May 12, 2011 at 3:03 PM, Smiley, David W. wrote: > The old name is "Lucandra" not Lucendra. I've changed the subject > accordingly. > > I'm looking forward to responses from people but I'm afraid it appears it > has not yet gotten much uptake yet. I think it has enormous potential once > it's hardened a bit and there's more documentation. Personally, I've been > looking forward to kicking the tires a bit once I get some time. > > ~ David Smiley > Author: http://www.packtpub.com/solr-1-4-enterprise-search-server/ > > On May 12, 2011, at 2:54 PM, kenf_nc wrote: > > > I modified the subject to include Lucendra, in case anyone has heard of > it by > > that name. > > > > -- > > View this message in context: > http://lucene.472066.n3.nabble.com/Anyone-familiar-with-Solandra-or-Lucendra-tp2927357p2933051.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > > > > -- http://twitter.com/tjake
Re: Anyone familiar with Solandra or Lucandra?
The old name is "Lucandra" not Lucendra. I've changed the subject accordingly. I'm looking forward to responses from people but I'm afraid it appears it has not yet gotten much uptake yet. I think it has enormous potential once it's hardened a bit and there's more documentation. Personally, I've been looking forward to kicking the tires a bit once I get some time. ~ David Smiley Author: http://www.packtpub.com/solr-1-4-enterprise-search-server/ On May 12, 2011, at 2:54 PM, kenf_nc wrote: > I modified the subject to include Lucendra, in case anyone has heard of it by > that name. > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Anyone-familiar-with-Solandra-or-Lucendra-tp2927357p2933051.html > Sent from the Solr - User mailing list archive at Nabble.com.
Re: Anyone familiar with Solandra or Lucendra?
I modified the subject to include Lucendra, in case anyone has heard of it by that name. -- View this message in context: http://lucene.472066.n3.nabble.com/Anyone-familiar-with-Solandra-or-Lucendra-tp2927357p2933051.html Sent from the Solr - User mailing list archive at Nabble.com.
Anyone familiar with Solandra?
The recent Amazon outage exposed a weakness in our architecture. We could really use a Master-Master redundancy. We already have Master to multiple Slaves. I've looked at the various options of converting a Slave into a Master, of having a Repeater (hybrid master/slave) become the Master etc. But, just yesterday, found out about https://github.com/tjake/Solandra#readme Solandra . It looks like exactly what I want. Especially considering we use Cassandra for a different part of our architecture already. And, if I'm reading it correctly, it could replace the SQL Server data store we use for persistence. It looks like Solandra gives me Multi-Master instead of master-slave, and the documents stored in Cassandra are persistent. If I need to drop and fully re-index the Solr side of the house, it can do so on the existing documents already in Cassandra. Two questions: Is what I just described accurate? Is Solandra ready for production? Thanks, Ken -- View this message in context: http://lucene.472066.n3.nabble.com/Anyone-familiar-with-Solandra-tp2927357p2927357.html Sent from the Solr - User mailing list archive at Nabble.com.
