t;> I read this as "If two client submit modifications and commits every
>> couple
>> >> of minutes, it could happen that modifications of client1 got committed
>> by
>> >> client2's commit before client1 asks for a commit."
>> >>
>>
; couple
> >> of minutes, it could happen that modifications of client1 got committed
> by
> >> client2's commit before client1 asks for a commit."
> >>
> >> As far as I understand Solr commit, they are serialized by design. And
> >> committi
sidis [mailto:savvas.andreas.moysi...@googlemail.com]
Envoyé : mercredi 9 février 2011 17:04
À : solr-user@lucene.apache.org
Objet : Re: Concurrent updates/commits
Hello,
Thanks very much for your quick replies.
So, according to Pierre, all updates will be immediately posted to Solr, but
all commits wi
Regards,
Em
--
View this message in context:
http://lucene.472066.n3.nabble.com/Concurrent-updates-commits-tp2459222p2459522.html
Sent from the Solr - User mailing list archive at Nabble.com.
, they are serialized by design. And
>> committing too often could lead you to trouble if you have many warm-up
>> queries (?).
>>
>> Hope this helps,
>>
>> Pierre
>> -Message d'origine-
>> De : Savvas-Andreas Moysidis [mailto:
>> sav
Hope this helps,
>
> Pierre
> -Message d'origine-
> De : Savvas-Andreas Moysidis [mailto:
> savvas.andreas.moysi...@googlemail.com]
> Envoyé : mercredi 9 février 2011 16:34
> À : solr-user@lucene.apache.org
> Objet : Concurrent updates/commits
>
> Hello,
>
&
l.com]
Envoyé : mercredi 9 février 2011 16:34
À : solr-user@lucene.apache.org
Objet : Concurrent updates/commits
Hello,
This topic has probably been covered before here, but we're still not very
clear about how multiple commits work in Solr.
We currently have a requirement to make our domain object
roblem somewhat, depending on the nature of your commits.
Jonathan
From: Savvas-Andreas Moysidis [savvas.andreas.moysi...@googlemail.com]
Sent: Wednesday, February 09, 2011 10:34 AM
To: solr-user@lucene.apache.org
Subject: Concurrent updates/commits
He
