Hi Edwin
Yes, we did not seem to have hit any filesystem upper-bounds.
I have not been able to reproduce this since this date.
> On Apr 1, 2019, at 7:28 PM, Zheng Lin Edwin Yeo wrote:
>
> Have you check if there are enough space to index all the documents on your
> disk?
>
> Regards,
> Edwin
Turns out the cause was multiple indexing jobs indexing into the index
simultaneously, which one can imagine can cause jvm loads on certain replicas
for sure.
Once this was found and only one job ran at a time, things were back to normal.
Your comments seem right on no correlation to the stack
Hi, i have some problem when implementing this solr classification,
this is my schema :
and this is my solrconfig :
classi
pagetext_mlt
knn_tags
prebayes_tags
bayes
Have you check if there are enough space to index all the documents on your
disk?
Regards,
Edwin
On Fri, 29 Mar 2019 at 15:16, Aroop Ganguly wrote:
> Trying again .. Any idea why this might happen?
>
>
> > On Mar 27, 2019, at 10:43 PM, Aroop Ganguly
> wrote:
> >
> > Hi Everyone
> >
> > My
Hi Bill,
Previously, did you index the date in the same format as you are using now,
or in the Solr format of "-MM-DDTHH:MM:SSZ"?
Regards,
Edwin
On Tue, 2 Apr 2019 at 00:32, Bill Tantzen wrote:
> In a legacy application using Solr 4.1 and solrj, I have always been
> able to add documents
4/1/2019 5:40 PM, Aroop Ganguly wrote:
Thanks Shawn, for the initial response.
Digging into a bit, I was wondering if we’d care to read the inner most stack.
From the inner most stack it seems to be telling us something about what
trigger it ?
Ofcourse, the system could have been overloaded
Thanks Shawn, for the initial response.
Digging into a bit, I was wondering if we’d care to read the inner most stack.
From the inner most stack it seems to be telling us something about what
trigger it ?
Ofcourse, the system could have been overloaded as well, but is the exception
telling us
Please follow the instructions here:
http://lucene.apache.org/solr/community.html#mailing-lists-irc
. You must use the _exact_ same e-mail as you used to subscribe.
If the initial try doesn't work and following the suggestions at the "problems"
link doesn't work for you, let us know. But note
On 4/1/2019 4:44 PM, Aroop Ganguly wrote:
I am facing this issue again.The stack mentions Heap space issue.
Are the document sizes too big ?
Not sure what I should be doing here; As on the solr admin ui I do not see jvm
being anywhere close to being full.
Any advise on this is greatly
Hi Group
I am facing this issue again.The stack mentions Heap space issue.
Are the document sizes too big ?
Not sure what I should be doing here; As on the solr admin ui I do not see jvm
being anywhere close to being full.
Any advise on this is greatly welcome.
Full Stack trace:
Please un-subscribe me.
Thanks in Advance,
Ashwin
On Mon, Apr 1, 2019 at 5:54 PM Aroop Ganguly wrote:
>
> Hi Group
>
> I am facing this issue again.The stack mentions Heap space issue.
>
> Are the document sizes too big ?
>
> Not sure what I should be doing here; As on the solr admin ui I do
Hi Group
I am facing this issue again.The stack mentions Heap space issue.
Are the document sizes too big ?
Not sure what I should be doing here; As on the solr admin ui I do not see jvm
being anywhere close to being full.
Any advise on this is greatly welcome.
Full Stack trace:
2019-04-01
Hi,
I am getting the following error while creating a core in Solr 8.0.0
"ERROR: Error CREATEing SolrCore 'nutch': Unable to create core [nutch]
Caused by: invalid boolean value:"
Command I am using to create the core:
#/opt/solr/bin/solr create -c nutch -d /opt/solr/server/solr/nutch/conf/
Wow, thank you Trey, great information! We are a Fusion client, works well for
us, we are leveraging the Signals Boosting. We were thinking omitNorms might be
of help here, turning that off actually. The PERSON document ranks #1 always
because it’s a tiny document with very short fields. I'll
Did you find out a way to get multiple payloadFields ?
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi Brett,
There are a couple of angles you can take here. If you are only concerned
about this specific term or a small number of other known terms like "IRA"
and want to spot fix it, you can use something like the query elevation
component in Solr (
In a legacy application using Solr 4.1 and solrj, I have always been
able to add documents with TrieDateField types using java.util.Date
objects, for instance,
doc.addField ( "date", new java.util.Date() );
having recently upgraded to Solr 7.7, and updating my schema to
leverage DatePointField
Minor nit. For IndexUpgraderTool and optimize to be identical, you have to
specify maxSegments=1 on optimize.
As of LUCENE-7976, optimize respects the max segment size and does _not_
necessarily rewrite segments that have no deleted documents, especially if
they’re near 5G which is the
Many Thanks!
-Ursprüngliche Nachricht-
Von: Shawn Heisey
Gesendet: Montag, 1. April 2019 18:03
An: solr-user@lucene.apache.org
Betreff: Re: AW: Solr 8.0.0 + IndexUpgrader
On 4/1/2019 9:47 AM, Herbert Hackelsberger wrote:
> So, am I correct:
> - When using the IndexUpgrader, it will
On 4/1/2019 9:47 AM, Herbert Hackelsberger wrote:
So, am I correct:
- When using the IndexUpgrader, it will make the Index usable in the actual
version, without all new features.
- Using the Index Upgrader in the future again on the next major version will
again result in this error situation.
Hi all,
I just wanted to inform you, when I stumbled across the ref guide at
https://lucene.apache.org/solr/guide/7_7/indexupgrader-tool.html
I had problems to run the command on my Windows System
Instead of
java -cp lucene-core-7.7.0.jar:lucene-backward-codecs-7.7.0.jar
Thanks for the fast response!
I used the IndexUpgrader to upgrade to 7.7.1 from 6.x and afterwards from 7.7.1
to 8.0.0
java -cp lucene-core-7.7.1.jar;lucene-backward-codecs-7.7.1.jar
org.apache.lucene.index.IndexUpgrader C:\solr\server\solr\syneris\data\index\
java -cp
Hello,
Looking for ideas on how to determine intent and drive results to a
person result or an article result. We are a financial institution and we have
IRA's Individual Retirement Accounts and we have a page that talks about an
Advisor, IRA Black.
Our users are in a bad
As of Lucene 6, a marker was written into each segment, and when segments are
merged the lowest marker is preserved. If any marker for version of Lucene X-2
is found, you will see the error you see.
This has been a source of considerable confusion. The guarantee of “one major
revision
On 4/1/2019 9:19 AM, Herbert Hackelsberger wrote:
I tried to upgrade my test index from Solr 7.7.1 to Solr 8.0.0.
The file segments_4h7 already contains the string Lucene70.
I upgraded before with this command:
java -cp lucene-core-7.7.1.jar;lucene-backward-codecs-7.7.1.jar
Hi,
I tried to upgrade my test index from Solr 7.7.1 to Solr 8.0.0.
The file segments_4h7 already contains the string Lucene70.
I upgraded before with this command:
java -cp lucene-core-7.7.1.jar;lucene-backward-codecs-7.7.1.jar
org.apache.lucene.index.IndexUpgrader
Hi Joseph –
I don’t think this is a Solr issue. It sounds like your http crawling process
doesn’t trust the cert that Solr is using.
Looks like you’re on the right track here – [I stumbled onto your post at
Github]
https://github.com/Norconex/collector-http/issues/581
Jeremy Branham
The Solr Reference Guide (of which the online documentation is a part)
gets built and released separately from the Solr distribution itself.
The Solr community tries to keep the code and documentation releases
as close together as we can, but the releases require work and are
done on a volunteer
Hello,
I’m looking for the documentation for the latest release of SolR (8.0) but it
looks like it’s not online yet.
https://lucene.apache.org/solr/news.html
http://lucene.apache.org/solr/guide/
Do you know when it will be available?
Best regards.
--
Yoann Moulin
EPFL IC-IT
29 matches
Mail list logo
