> On 16 Mar 2022, at 04:27, Sam Lee wrote:
>
> On 2022/03/15 15:37:59 "Ing. Andrea Vettori" wrote:
>> in our setup we have two Solr servers and we index documents to both
>> (we keep track of the last sync for each server so they can also be
>> not aligned in a certain moment for example for ma
On 2022-03-15 10:12 -0400, Eric Pugh wrote:
> I am proposing Standalone Solr ;-)
>
> You are quite right that if the indexer goes offline, then you
> wouldn’t see updates in your two separate Solrs….However, assuming
> you aren’t in a near real time situation where your application is
> broken
On 2022/03/15 15:37:59 "Ing. Andrea Vettori" wrote:
> in our setup we have two Solr servers and we index documents to both
> (we keep track of the last sync for each server so they can also be
> not aligned in a certain moment for example for maintenance).
Thank you for proposing this simple setup
Hi all,
just asking how can I rely on the number of processors the solr dashboard
shows.
Just to give you a context, I have a 2 nodes solrcloud instance running in
kubernetes.
Looking at solr dashboard (8.3.0) I see there is only 1 cpu available per
solr instance.
but the Solr pods are deployed i
Hi,
I have some strange results when using both mm and q.op with edismax in
solr 8.11. In this case it looks like q.op has priority on mm.
In all other cases (solr 4 with both dismax and edismax ou Solr 8 with
dismax) in accordance with the documentation, mm has priority on q.op.
Here is my quer
On 3/16/22 04:52, Dominique Bejean wrote:
I have some strange results when using both mm and q.op with edismax in
solr 8.11. In this case it looks like q.op has priority on mm.
In all other cases (solr 4 with both dismax and edismax ou Solr 8 with
dismax) in accordance with the documentation, mm
Hi Shawn,
For both dismax and edismax, documentation explain q.op is used only if mm
is not set and q.op=and is equal to mm=100% and q.op=or is equal to mm=0%.
It works fine with dismax but strangely but not with edismax in Solr 8.
Regards
Dominique
Le mer. 16 mars 2022 à 18:29, Shawn Heisey
On 3/16/22 03:56, Vincenzo D'Amore wrote:
just asking how can I rely on the number of processors the solr dashboard
shows.
Just to give you a context, I have a 2 nodes solrcloud instance running in
kubernetes.
Looking at solr dashboard (8.3.0) I see there is only 1 cpu available per
solr instanc
On 3/16/22 11:40, Dominique Bejean wrote:
For both dismax and edismax, documentation explain q.op is used only if mm
is not set and q.op=and is equal to mm=100% and q.op=or is equal to mm=0%.
It works fine with dismax but strangely but not with edismax in Solr 8.
I'd say that's enough for an is
Hi Shawn, thanks for your help.
Given that I’ll put the question in another way.
If Java don’t correctly detect the number of CPU how the overall performance
can be affected by this?
Ciao,
Vincenzo
--
mobile: 3498513251
skype: free.dev
> On 16 Mar 2022, at 18:56, Shawn Heisey wrote:
>
> O
On 3/16/2022 6:11 PM, Vincenzo D'Amore wrote:
Given that I’ll put the question in another way.
If Java don’t correctly detect the number of CPU how the overall performance
can be affected by this?
I could be wrong, but I don't think Solr makes decisions based on CPU
count, at least not withou
11 matches
Mail list logo
