lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <>
Subject Re: Solr updateRequestHandler and performance vs. atomicity
Date Wed, 02 Jun 2010 08:08:05 GMT
While preparing material for
I came across something that looks relevant:

...where the author wrote this:

"In conclusion, this directory attempts to marry the rich search-based 
query language of Lucene with the distributed fault-tolerant database 
that is Cassandra. By delegating the responsibilities of replication, 
durability and elasticity to the directory, we free the layers above 
from such non-functional concerns. Our hope is that users will choose to make their large-scale
indices instantly scalable by seamlessly 
migrating them to this type of directory (using 
Sematext :: :: Solr - Lucene - Nutch
Lucene ecosystem search ::

----- Original Message ----
> From: Yonik Seeley <>
> To:
> Sent: Tue, May 25, 2010 8:59:29 AM
> Subject: Re: Solr updateRequestHandler and performance vs. atomicity
> On Mon, May 24, 2010 at 9:10 AM,  <
> ymailto="" 
> href="">> wrote:
> In particular, it would be nice to be able to post documents in such a 
> way
> that you can guarantee that the document is permanently in Solr’s 
> queue,
> safe in the event of a Solr restart, etc., even if the document 
> has not yet
> been “committed”.

Yep, this is a longer term goal of 
> SolrCloud.
And to be truly safe, committing to stable storage is not enough 
> -
that still might crash and never recover.  One needs to write 
> to
multiple nodes.


> target=_blank 
> >

> unsubscribe, e-mail: 
> href="">
> additional commands, e-mail: 
> href="">

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message