Thanks you both for time spent and for good suggestions. Hope you'll be
glad to know that this solution seems to work very well. :)
Best regards,
Vincenzo
On Tue, Jan 30, 2018 at 10:55 AM, Alessandro Benedetti wrote:
> "At last, please let me ask another question, is it
"At last, please let me ask another question, is it true that after every
commit, even if I had only updated one document, the SolrCloud cache is
invalidated (i.e. Solr must open a new searcher)?
Because this what the second clients does, updating a document at time and
commit.
In other
Hey guys, thank you so much for this help.
Recalling all your suggestions I think I should:
1. Have two collections with an alias that alternatively point to one of
them. Use the configuration with autoSoftCommit and openSearcher=true. I
call this scenario an active/passive configuration.
2. The
Generally speaking, if a full re-index is happening everyday, wouldn't be
better to use a technique such as collection alias ?
You could point your search clients to the "Alias" which points to the
online collection "collection1".
When you re-index you build "collection2", when it is finished you
On 1/26/2018 4:23 AM, Vincenzo D'Amore wrote:
> The first client does the following:
>
> 1. rollbacks all add/deletes made to the index since the last commit (in
> case previous client execution was completed unsuccessfully).
> 2. reads data from sql server
> 3. updates solr documents
> 4.
Thanks Shawn,
>>
>> 30
>> false
>>
>>
>
> That autoCommit configuration is not affecting document visibility at all,
> because openSearcher is set to false. Don't rush to change this -- this
> kind of configuration is what you want. I would probably use one minute
> here rather than five
On 1/25/2018 7:48 AM, Vincenzo D'Amore wrote:
I have few questions about SolrCloud and how could behave in an
environment where there are more concurrent clients updating the same
collection.
We have a SolrCloud 4.8.1 collection that stores a catalog of millions
of products (index size about
Hi All,
I have few questions about SolrCloud and how could behave in an
environment where there are more concurrent clients updating the same
collection.
We have a SolrCloud 4.8.1 collection that stores a catalog of millions
of products (index size about 20GB).
Actually there is only one SolrJ