Thank you for your reply. I looked at solr.in.sh I see that
SOLR_SSL_CLIENT_KEY_STORE is already commented out by default. But you are
right I looked at the running solr, I see the option -Djavax.net.ssl.keyStore
pointing to solr-ssl.keystore.p12 , not sure how it is getting that value. Let
Hi all,
I'm facing the problem that Solr is throwing a NullPointerException when
performing a distributed search with multiple shards having elevation
configured where one or more shards do have elevated results but others do not.
We are using Solr 8.2 and have the QueryElevationComponent confi
From the /bin directory I did grep for SOLR_SSL_CLIENT_KEY_STORE ,
this is what I see . But somehow the option option -Djavax.net.ssl.keyStore is
added
grep SOLR_SSL_CLIENT_KEY_STORE *
grep: init.d: Is a directory
solr: if [ -n "$SOLR_SSL_CLIENT_KEY_STORE" ]; then
solr:SOLR_SSL_OPTS+=" -Dja
The Lucene PMC is pleased to announce the release of Apache Solr 8.6.0.
Solr is the popular, blazing fast, open source NoSQL search platform from
the Apache Lucene project. Its major features include powerful full-text
search, hit highlighting, faceted search, dynamic clustering, database
integra
On 14/07/2020 12:48, Erick Erickson wrote:
This is almost certainly a mismatch between what you think is happening
and what you’ve actually told Solr to do ;).
That's a great one-line explanation of 90% of the issues people face
with Solr :-)
Charlie
Best,
Erick
On Jul 14, 2020, at 7:05
Ok , I looked at the solr script , here is the logic , even if the
SOLR_SSL_CLIENT_KEY_STORE_PASSWORD is not set , it sets the
-Djavax.net.ssl.keyStore=$SOLR_SSL_KEY_STORE" . Let me remove the else part and
test it . Thanks again for the pointer
if [ -n "$SOLR_SSL_CLIENT_KEY_STORE" ]; then
Here is the result. I removed the else block and tested . You are correct , the
previous exception which I saw went away.
But I see bel.ow exception , not sure what is the reason for this NPE.
2020-07-15 10:28:14.453 INFO (MetricsHistoryHandler-12-thread-1) [ ]
o.a.s.c.s.i.SolrClientNodeStat
Hi,
I am using Solr 7.7
I am trying to start my solr server with G1 GC instead of the default CMS
but the solr service doesn't get up.
The command I use to start solr is
bin/solr start -p 25280 -a "-Dsolr.solr.home=
-Denable.slave=true -Denable.master=false -XX:+UseG1GC
-XX:MaxGCPauseMillis=500
Well, the first thing I’d do is not use _any_ options. Just bin/solr start.
If that works, try adding things in.
-Denable.master and -Denable.slave are specifically for the old master/slave
architecture. Is that your intent? At any rate, leave them out at first.
Second, there’s not much heap allo
Heck, Charlie, it explains 90% of the problems I’ve personally had with
programming in general over my entire career...
> On Jul 15, 2020, at 5:08 AM, Charlie Hull wrote:
>
> On 14/07/2020 12:48, Erick Erickson wrote:
>> This is almost certainly a mismatch between what you think is
>> happenin
Hmmm, looking at the code that line looks like this:
sortSpec.getSort().getSort();
I’m curious what happens if you specify a sort on the query? If that makes the
problem go away,
it’s a smoking gun.
Whether or not adding sorting makes the problem go away, this looks like
something
that’s a le
You need to remove the references from bin/solr or bin/solr.cmd to
SOLR_SSL_CLIENT_KEY_STORE and "-Djavax.net.ssl.keyStore". This is different
from solr.in.sh.
The way the bin/solr script is written it is falling back to whatever is
provided as SOLR_SSL_KEY_STORE for the client keystore which is c
Yes ,that's correct . I did that and the exception is gone.
But I see bel.ow exception , not sure what is the reason for this NPE.
2020-07-15 10:28:14.453 INFO (MetricsHistoryHandler-12-thread-1) [ ]
o.a.s.c.s.i.SolrClientNodeStateProvider Error on getting remote info, trying
again: IOExce
Dear Solr Users,
In this release (Solr 8.6), we have deprecated the following:
1. Data Import Handler
2. HDFS support
3. Cross Data Center Replication (CDCR)
All of these are scheduled to be removed in a future 9.x release.
It was decided that these components did not meet the standar
Am 15.07.20 um 16:07 schrieb Ishan Chattopadhyaya:
> Dear Solr Users,
>
> In this release (Solr 8.6), we have deprecated the following:
>
> 1. Data Import Handler
>
> 2. HDFS support
>
> 3. Cross Data Center Replication (CDCR)
>
Seriously? :-(
So next steps will be kicking out Cloud
I don’t see a heap size specified, so it is probably trying to run with
a 512 Megabyte heap. That might just not work with the 32M region
size.
Here are the options we have been using for 3+ years on about 150 hosts.
SOLR_HEAP=8g
# Use G1 GC -- wunder 2017-01-23
# Settings from https://wiki.apac
Hello,
I was wondering if we can expect significant disk usage reduction (index size)
if we move from fields defined as "docValues=true + stored=true" to
"docValues=true + stored=false" (with useDocValuesAsStored=true as default in
both cases)?
Considering the use case we are targeting is only
howdy,
i have a field that sorts fine all other content, and i cant seem to debug
why it wont sort for me on this one chunk of it.
"sort":"alphatitle asc", "debugQuery":"on", "_":"1594733127740"}}, "response
":{"numFound":3,"start":0,"docs":[ { "title":"Money orders", {
"title":"Finance,
consolidat
I’d look two places:
1> try the admin/analysis page from the admin UI. In particular, look at what
tokens actually get in the index.
2> again, the admin UI will let you choose the field (alphatitle and title) and
see what the actual indexed tokens are.
Both have the issue that I don’t know wha
thanks, ill check the admin, didnt want to send a big clock of text but:
-
-
Tokenizer:
org.apache.lucene.analysis.core.KeywordTokenizerFactoryclass:
solr.KeywordTokenizerFactoryluceneMatchVersion: 7.1.0
-
Token Filters:
org.apache.lucene.analysis.co
You’re off track a bit. useDocValuesAsStored has no effect on the size on disk.
It’s purely a runtime option that pulls the data to return from either the
stored or docValues parts of the index. If you change the definition and
reindex, you should see significant differences in the size of your
Yeah, it’s always a question “how much is enough/too much”.
That looks reasonable for alphatitle, but what about title? Your original
question was that the sorting changes depending on which field you
sort on. If your title field uses something that tokenizes or doesn’t
include the same analysis
That’s a good place to start. The idea was to make sure titles that started
with a date would not always be at the forefront and the actual title of the
doc would be sorted.
> On Jul 15, 2020, at 4:58 PM, Erick Erickson wrote:
>
> Yeah, it’s always a question “how much is enough/too much”.
>
On Wed, 15 Jul, 2020, 8:37 pm Bernd Fehling,
wrote:
>
>
> Am 15.07.20 um 16:07 schrieb Ishan Chattopadhyaya:
> > Dear Solr Users,
> >
> > In this release (Solr 8.6), we have deprecated the following:
> >
> > 1. Data Import Handler
> >
> > 2. HDFS support
> >
> > 3. Cross Data Center Replica
To address your concern Bernd,
The goal of this deprecation is not to remove the functionality entirely.
The primary purpose is to remove the code from Solr Core. Before removing a
feature we aim to either:
- Move the code to another repository, and have it be loadable via a
plugin
- Rep
May we ask what in hdfs support is being deprecated? Is Hdfs backup and restore
being deprecated ?
Sent from my iPhone
> On Jul 15, 2020, at 3:41 PM, Houston Putman wrote:
>
> To address your concern Bernd,
>
> The goal of this deprecation is not to remove the functionality entirely.
> The
Resending this again as I still could not make this work. So would like to know
if this is even possible to have
both solr.CdcrUpdateProcessorFactory and
solr.IgnoreCommitOptimizeUpdateProcessorFactory in solrconfig.xml and get both
functionalities work.
Please let me know.
Thank you,
Rajeswar
Thanks Erick for your fast response.
I've checked out adding the sort param and yes that vanished the problem but it
also disables elevation if I'm not mistaken. So after adding
forceElevation=true to the query then a ClassCastException was thrown:
http://localhost:9983/solr/core1/select?q=elev
Ok, makes sense.
Thanks for your answer Erick.
Gaël
De : Erick Erickson
Envoyé : mercredi 15 juillet 2020 22:53
À : solr-user@lucene.apache.org
Objet : Re: Disk usage with useDocValuesAsStored
You’re off track a bit. useDocValuesAsStored has no effect on the si
29 matches
Mail list logo
