Re: Any blog or url that explain step by step configure grafana dashboard to monitor solr metrics
You can refer the below url https://lucene.apache.org/solr/guide/7_3/monitoring-solr-with-prometheus-and-grafana.html On Thu, 24 Sep, 2020, 8:25 am yaswanth kumar, wrote: > Can some one post here any blogs or url where I can get the detailed steps > involved in configuring grafana dashboard for monitoring solr metrics?? > > Sent from my iPhone
Any blog or url that explain step by step configure grafana dashboard to monitor solr metrics
Can some one post here any blogs or url where I can get the detailed steps involved in configuring grafana dashboard for monitoring solr metrics?? Sent from my iPhone
solr performance with >1 NUMAs
Hi, Recently we deployed solr 8.4.1 on a batch of new servers with 2 NUMAs. I noticed that query latency almost doubled compared to deployment on single NUMA machines. Not sure what's causing the huge difference. Is there any tuning to boost the performance on multiple NUMA machines? Any pointer is appreciated. Best, Wei
Re: Difference in q.op param behavior between Solr 6.3 and Solr 8.5.2
In 6.3 it did that? It shouldn't have. q and fq shouldn't share parameters.
fq's themselves shouldn't, IMO, have global defaults. fq's need to be stable
and often uniquely specified kinds of constraining query parsers
({!terms/term/field,etc}) or rely on basic Lucene query parser syntax and be
able to stably rely on AND/OR.
Relevancy tuning on q and friends, tweaking those parameters, shouldn't affect
fq's, to say it a little differently.
One can fq={!lucene q.op=AND}id:(1 2 3)
Erik
> On Sep 23, 2020, at 4:23 PM, gnandre wrote:
>
> Is there a way to set default operator as AND for fq parameter in Solr
> 8.5.2 now?
>
> On Tue, Sep 22, 2020 at 7:44 PM gnandre wrote:
>
>> In 6.3, q.op param used to affect q as well fq param behavior. E.g. if
>> q.op is set to AND and fq is set to id:(1 2 3), no results will show up but
>> if it is set to OR then all 3 results will show up. This does not happen in
>> Solr 8.5.2 anymore.
>>
>> Is this a bug? What does one need to do in Solr 8.5.2 to achieve the same
>> behavior besides passing the operator directly in fq param i.e. id:(1 OR 2
>> OR 3)
>>
Re: Difference in q.op param behavior between Solr 6.3 and Solr 8.5.2
Is there a way to set default operator as AND for fq parameter in Solr 8.5.2 now? On Tue, Sep 22, 2020 at 7:44 PM gnandre wrote: > In 6.3, q.op param used to affect q as well fq param behavior. E.g. if > q.op is set to AND and fq is set to id:(1 2 3), no results will show up but > if it is set to OR then all 3 results will show up. This does not happen in > Solr 8.5.2 anymore. > > Is this a bug? What does one need to do in Solr 8.5.2 to achieve the same > behavior besides passing the operator directly in fq param i.e. id:(1 OR 2 > OR 3) >
Re: Solr 8.6.2 - Solr loaded a deprecated plugin/analysis
On 9/22/2020 10:22 PM, Anuj Bhargava wrote: How to solve this issue? How to replace it? SolrResourceLoader Solr loaded a deprecated plugin/analysis class [solr.DataImportHandler]. Please consult documentation how to replace it accordingly. That is a generic message about using deprecated features. It's a message that means "Hey, we noticed you're using something that's going to disappear one day. You might want to look into using something else, because one day that thing you're using is going to be gone." DIH (the DataImportHandler) is being discontinued. It will no longer be maintained by the project. Its functionality might be continued by the community in a new project, that may or may not be part of the Apache Foundation. If you stick with Solr 8.x, you will not need to find a replacement for DIH. It should remain part of Solr in all 8.x versions, most things that are deprecated are not removed until the next *major* version is released, which in this case, will be version 9.0.0. We do not yet know when that version will be released. Thanks, Shawn
