Thanks Hoss. Yes, that jira seems like a good one to fix.
And the variable name definitely does not explain why it will not cause any
sort operation.
-SG
On Mon, Mar 2, 2020 at 10:06 AM Chris Hostetter
wrote:
> : docid is the natural order of the posting lists, so there is no sorting
> effort.
I got below ERROR in Solr 6.1.0 log
2020-03-05 16:54:09.508 ERROR (qtp1239731077-468949) [c:workflows s:shard1
r:core_node1 x:workflows] o.a.s.h.RequestHandlerBase
org.apache.solr.common.SolrException: Exception writing document id
WF204878828_42970103 to the index; possible analysis error.
at
Hi all,
We have a solr 8.4.1 server running on Windows. (Very simple setup.)
16GB RAM / JVM-Mem set to 4GB
Solr host 4 cores. (2 GB + 1GB + 75MB + 75MB)
Full data import every night. No delta import.
This server is used for tests by 2 people. (very low request rate)
We have an issue we don't unde
v6.6.0 is from 2017 and not supported anymore. You are really encouraged to
upgrade!
Are you by any chance using Internet Explorer? (See
https://stackoverflow.com/questions/56262704/solr-solrcore-initialization-failures-core-error)
Jan
> 5. mar. 2020 kl. 22:03 skrev Ryan W :
>
> Hi all,
>
>
Hi all,
On my dev server, in the Solr admin UI, I see...
SolrCore Initialization Failures
{{core}}: {{error}}
Please check your logs for more information
{{exception.msg}}
These appear to be template variables, but they are never populated. They
just dump to the screen. There i
Just keep in mind that the total memory should be much more than the heap to
leverage Solr file caches. If you have 8 GB heap probably at least 16 gb total
memory make sense to be available on the machine .
> Am 05.03.2020 um 16:58 schrieb Walter Underwood :
>
>
>>
>> On Mar 5, 2020, at 4:29
> On Mar 5, 2020, at 4:29 AM, Bunde Torsten wrote:
>
> -Xms512m -Xmx512m
Your heap is too small. Set this to -Xms8g -Xmx8g
In solr.in.sh, that looks like this:
SOLR_HEAP=8g
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
Hello @all,
I've got a problem with Solr (version 7.7.2) since some days.
On March, 4th I got an OOM and the log file just says the following:
Running OOM killer script for process 12351 for Solr on port 8983
Killed process 12351
So I started the service again and the service is running fine. B
Hi
Solr query parser has special handling for single asterisk * which is rewritten
as a «MatchAllDocs» query, the same as *:*. So when you do ** you probably
explicitly invoke the wildcard feature which enumerates all terms in the
dictionary.
I don’t see what you are trying to achieve with the
