n't see collections created where the
> replicas run on the same node.
>
> I tried to create a new version of the collection forcing it to use both
> nodes. However, that doesn't work both replicas are created on the same node:
> /solr/admin/collections?action=CREATE=sial-cat
Piotr,
Based on the questions that we've seen over the past month on this list,
there are still users with Solr on 6, 7, and 8. I suspect there are still
Solr 5 users out there too, although they don't appear to be asking for
help - likely they are in set it and forget it mode.
Solr 7 may not be
collections created where the
replicas run on the same node.
I tried to create a new version of the collection forcing it to use both nodes.
However, that doesn't work both replicas are created on the same node:
/solr/admin/collections?action=CREATE=sial-catalog-product-20201027=sial-catalog-product
Thanks for the answer! We added the line and now everything is working as
expected. Sorry for not reading the manual properly :)
Philipp
Am Mo., 26. Okt. 2020 um 09:27 Uhr schrieb Jan Høydahl <
jan@cominvent.com>:
> According to the source code here
>
>
>
Good to hear that. Thanks for closing the loop!
On Tue, Oct 27, 2020 at 11:14 AM Jonathan Tan wrote:
> Hi Shalin,
>
> Moving to 8.6.3 fixed it!
>
> Thank you very much for that. :)
> We'd considered an upgrade - just because - but we won't have done so so
> quickly without your information.
>
>
That first graph shows a JVM that does not have enough heap for the
program it is running. Look at the bottom of the dips. That is the amount
of memory still in use after a full GC.
You want those dips to drop to about half of the available heap, so I’d
immediately increase that heap to 4G.
Thanks!
Mark
On Tue, Oct 27, 2020 at 11:56 AM Dave wrote:
> Agreed. Just a JavaScript check on the input box would work fine for 99%
> of cases, unless something automatic is running them in which case just
> server side redirect back to the form.
>
> > On Oct 27, 2020, at 11:54 AM, Mark
Hi,
We are working on dependency updates at Apache Beam and I would like to
consult which versions should be supported so we don't break any existing
users.
Previously the supported Solr version was 5.5.4.
Versions 8.x.y and 7.x.y naturally come to mind as they are the only not
deprecated. But
Agreed. Just a JavaScript check on the input box would work fine for 99% of
cases, unless something automatic is running them in which case just server
side redirect back to the form.
> On Oct 27, 2020, at 11:54 AM, Mark Robinson wrote:
>
> Hi Konstantinos ,
>
> Thanks for the reply.
> I
Hi Konstantinos ,
Thanks for the reply.
I too feel the same. Wanted to find what others also in the Solr world
thought about it.
Thanks!
Mark.
On Tue, Oct 27, 2020 at 11:45 AM Konstantinos Koukouvis <
konstantinos.koukou...@mecenat.com> wrote:
> Oh hi Mark!
>
> Why would you wanna do such a
Oh hi Mark!
Why would you wanna do such a thing in the solr end. Imho it would be much more
clean and easy to do it on the client side
Regards,
Konstantinos
> On 27 Oct 2020, at 16:42, Mark Robinson wrote:
>
> Hello,
>
> I want to block queries having only a digit like "1" or "2" ,...
Hello,
I want to block queries having only a digit like "1" or "2" ,... or
just a letter like "a" or "b" ...
Is it a good idea to block them ... ie just single digits 0 - 9 and a - z
by putting them as a stop word? The problem with this I can anticipate is a
query like "1 inch screw" can
Hi Jaan,
You can also check in admin console in caches the sizes of field* caches. That
will tell you if some field needs docValues=true.
Regards,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> On 27
Hi Erick,
Thanks for this information, I will look into it.
Main changes were regarding parsing the results JSON got from solr, not the
queries or updates.
Jaan
P.S. configuration change about requestParser was not it.
-Original Message-
From: Erick Erickson
Sent: 27 October 2020
Jean:
The basic search uses an “inverted index”, which is basically a list of terms
and the documents they appear in, e.g.
my - 1, 4, 9, 12
dog - 4, 8, 10
So the word “my” appears in docs 1, 4, 9 and 12, and “dog” appears in 4, 8, 10.
Makes
it easy to search for
my AND dog
for instance,
I found one little difference from old solrconfig and new one.
It is in requestDispatchers section
It does not have this, but we had this in old configuration. Maybe it helps, I
will see.
Jaan
-Original Message-
From: Jaan Arjasepp
Sent: 27 October 2020 14:05
To:
Hi Emir,
I checked the solrconfig.xml file and we dont even use fieldValueCache. Also
are you saying, I should check the schema and all the fields in the old solr
and the new one to see if they match or contain similar settings? What does
this uninverted value means? How to check this?
As for
Hi,
we're running tests on a stand-alone Solr instance, which create Solr
cores from multiple applications using CoreAdmin (via SolrJ).
Lately, we upgraded from 8.4.1 to 8.6.3, and sometimes we now see a
LockObtainFailedException for a lock held by the same JVM, after which
Solr is broken
Hi Jaan,
It can be several things:
caches
fieldCache/fieldValueCache - it can be that you you are missing doc values on
some fields that are used for faceting/sorting/functions and that uninverted
field structures are eating your memory.
filterCache - you’ve changed setting for filter caches
Hi,
In order to see time range metrics, you’ll need to collect metrics periodically
and send it to some storage and then query/visualise. Solr has exporters for
some popular backends, or you can use some cloud based solution. One such
solution is our:
Hi folks,
Doing some faceted queries using 'facet.json' param and SolrJ, the results
of which I am processing using SolrJ NestableJsonFacet class.
basically as *queryResponse.getJsonFacetingResponse() -> returns
*NestableJsonFacet
object.
But I have noticed it does not maintain the facet-query
Hello,
We have been using SOLR for quite some time. We used 6.0 and now we did a
little upgrade to our system and servers and we started to use 8.6.1.
We use it on a Windows Server 2019.
Java version is 11
Basically using it in a default setting, except giving SOLR 2G of heap. It used
512, but
22 matches
Mail list logo
