lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: Solrcloud: external fields and frequent commits
Date Fri, 22 Nov 2013 13:21:56 GMT
1> I'm not quite sure I understand. External File Fields are keyed
by the unique id of the doc. So every shard _must_ have the
eff available for at least the documents in that shard. At first glance
this doesn't look simple. Perhaps a bit more explanation of what
you're using EFF for?

2> Let's be sure we're talking about the same thing here. In Solr,
a "commit" is the command that makes documents visible, often
controlled by the autoCommit and autoSoftCommit settings in
solrconfig.xml. You will not be able to issue 100 commits/second.

If you're using "commit" to mean adding a document to the index,
then 100/s should be no problem. I regularly see many times that
ingestion rate. The documents won't be visible to search until
you do a commit however.

Best
Erick


On Fri, Nov 22, 2013 at 4:44 AM, Flavio Pompermaier <pompermaier@okkam.it>wrote:

> Hi to all,
> we're migrating from solr 3.x to solr 4.x to use Solrcloud and I have two
> big doubts:
>
> 1) External fields. When I compute such a file do I have to copy it in the
>  data directory of shards..? The external fields boosts the results of the
> query to a specific collection, for me it doesn't make sense to put it in
> all shard's data dir, it should be something related to the collection
> itself.
> Am I wrong or missing something? Is there a simple way to upload the
> popularity file (for the external field) at one in all shards?
>
> 2) My index requires frequently commits (i.e. sometimes up to 100/s). How
> do I have to manage this? Do I have to use soft commits..? Any simple
> configuration/code snippet to use them? Is it true that external fields
> affect performance on commit?
>
> Best,
> Flavio
>

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