lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Furkan KAMACI <>
Subject Re: Filtering Search Cloud
Date Wed, 03 Apr 2013 19:52:15 GMT
Thanks for your explanation, you explained every thing what I need. Just
one more question. I see that I can not make it with Solr Cloud, but I can
do something like that with master-slave replication of Solr. If I use
master-slave replication of Solr, can I eliminate (filter) something
(something that is indexed from master) from being a response after
querying (querying from slaves) ?

2013/4/3 Shawn Heisey <>

> On 4/3/2013 1:13 PM, Furkan KAMACI wrote:
> > Shawn, thanks for your detailed explanation. My system will work on high
> > load. I mean I will always index something and something always will be
> > queried at my system. That is why I consider about physically separating
> > indexer and query reply machines. I think about that: imagine a machine
> > that both does indexing (a disk IO for it, I don't know the underlying
> > system maybe Solr makes a sequential IO) and both trying to reply queries
> > (another kind of IO) That is my main challenge to decide separating them.
> > And the next step is that, if I separate them before response can I
> filter
> > the data of indexer machines (I don't have any filtering  issues right
> now,
> > I just think that maybe I can need it at future)
> We do seem to have a language barrier, so let me try to be very clear:
> If you use SolrCloud, you can't separate querying and indexing.  You
> will have to use the master-slave replication that been part of Solr
> since at least 1.4, possibly earlier.
> Thanks,
> Shawn

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message