Le 09/09/2016 à 17:57, Shawn Heisey a écrit :
On 9/8/2016 9:41 AM, Bruno Mannina wrote:
- I stop SOLR 5.4 on Ubuntu 14.04LTS - 16Go - i3-2120 CPU @ 3.30Ghz
- I do a simple directory copy /data to my HDD backup (from 2To SATA
to 2To SATA directly connected to the Mothercard).
All files are copi
On 9/8/2016 9:41 AM, Bruno Mannina wrote:
> - I stop SOLR 5.4 on Ubuntu 14.04LTS - 16Go - i3-2120 CPU @ 3.30Ghz
>
> - I do a simple directory copy /data to my HDD backup (from 2To SATA
> to 2To SATA directly connected to the Mothercard).
>
> All files are copied fine but one not ! the biggest (~65G
Dear Solr Users,
I use since several years SOLR and since two weeks, I have a problem
when I try to copy my solr index.
My solr index is around 180Go (~100 000 000 docs, 1 doc ~ 3ko)
My method to save my index every Sunday:
- I stop SOLR 5.4 on Ubuntu 14.04LTS - 16Go - i3-2120 CPU @ 3.30Ghz
-
Hi all
I am having a strange error whenever I close my index (calling server.close()
The error is shown below. I am not sure where I should look - the configuration
file? The code? Or index fragments? Or else? The code causing the error is very
simple, just the “close()” method.
Many thanks
Below is a very large error message and associated stacktrace that I can
see in the Solr log on a Linux system running version 5.2.1 with Oracle
JDK 8u60. This message appeared a bunch of times over the weekend, but
does not appear to be happening now.
This looks like a low level Lucene error, th
Hallo,
when I do a full import of a SOLR index I become a strange error
message:
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.sql.SQLRecoverableException: Closed Resultset: next
It is only a simple query
select FIRMEN_ID, FIRMIERUNG, FIRMENKENNUNG,
PZN, DEBITORNUMMER
I fixed it by setting JVM properties in glassfish.
-Djavax.net.ssl.keyStorePassword=changeit
--
View this message in context:
http://lucene.472066.n3.nabble.com/Strange-error-in-Solr-4-2-tp4047386p4051159.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Mar 14, 2013, at 1:27 PM, Shawn Heisey wrote:
> I have been told that it is possible to override the handleError method to
> fix this
I'd say mitigate more than fix. I think the real fix requires some dev work.
- Mark
On 3/14/2013 9:24 AM, Uwe Klosa wrote:
This exception occurs in this part
new ConcurrentUpdateSolrServer("http://solr.diva-portal.org:8080/search";,
5, 50)
Side comment, unrelated to your question:
If you're already aware that ConcurrentUpdateSolrServer has no built-in
error handling and you
On Thursday, March 14, 2013 at 4:57 PM, Uwe Klosa wrote:
> I found the answer myself. Thanks for the pointer.
Would you mind sharing you answer, Uwe?
I found the answer myself. Thanks for the pointer.
Cheers
Uwe
On 14 March 2013 16:48, Uwe Klosa wrote:
> Thanks, but nobody has tempered with keystores. I have tested the
> application on different machines. Always the same exception is thrown.
>
> Do we have to set some system property to fix
Thanks, but nobody has tempered with keystores. I have tested the
application on different machines. Always the same exception is thrown.
Do we have to set some system property to fix this?
/Uwe
On 14 March 2013 16:36, Mark Miller wrote:
> Perhaps as a result of https://issues.apache.org/ji
Perhaps as a result of https://issues.apache.org/jira/browse/SOLR-4451 ?
Just a guess.
The root cause looks to be:
> Caused by: java.io.IOException: Keystore was tampered with, or password was
> incorrect
- Mark
On Mar 14, 2013, at 11:24 AM, Uwe Klosa wrote:
> Hi
>
> We have been using Sol
Hi
We have been using Solr 4.0 for a while now and wanted to upgrade to 4.2.
But our application stopped working. When we tried 4.1 it was working as
expected.
Here is a description of the situation.
We deploy a Solr web application under java 7 on a Glassfish 3.1.2.2
server. We added some clas
did you re-index everything after you changed from date to tdate? Looks to
me like you had some data already in your index, changed the defs, added a
few more docs and blew up.
I'd just blow away your entire index directory and re-index from scratch...
Best
Erick
On Tue, Mar 5, 2013 at 11:0
|
I am getting the following error when I try to use a stats.facet for a date
field. Anyone know how to fix this?
Invalid Date String:' #1;#0;#0;#0;oT$#0;'
||I have checked the values of the date and they are all fine.
I am not sure where this is coming from.
The really odd thing is that th
Hi,
I delete some data from Solr, post the deletion I am getting truncated XML
when I run q=*:* query, in all other cases the queries execute fine. The
following error is shown in the log files,
May 25, 2012 7:10:36 PM org.apache.solr.common.SolrException log
SEVERE: java.lang.NullPointer
On Wed, Aug 19, 2009 at 6:44 PM, ahammad wrote:
>
> Each core has a different database as a datasource, which means that they
> have different DB structures and fields. That is why the schemas are
> different.
> > If all the shards should have the same schema, then what is the point of
> > shar
t was used to combine
> different cores with different index structures...Right now, every core I
> have is unique, and every schema is different...
>
> --
> Regards,
> Shalin Shekhar Mangar.
>
>
--
View this message in context:
http://www.nabble.com/Strange-error-with-shards-tp25027486p25043859.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Tue, Aug 18, 2009 at 9:01 PM, ahammad wrote:
> HTTP Status 500 - null java.lang.NullPointerException at
>
> org.apache.solr.handler.component.QueryComponent.mergeIds(QueryComponent.java:437)
> at
>
> The way I created this shard was to copy an existing one, erasing all the
> data files/folders
are pretty much the same.
>
> If I try the shard parameter with any of the other 7 cores that I have, it
> works fine. It's only when this specific one is in the URL...
>
> Cheers
> --
> View this message in context:
> http://www.nabble.com/Strange-error-with-shards-tp25027486p25027486.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
--
Lici
pretty much the same.
If I try the shard parameter with any of the other 7 cores that I have, it
works fine. It's only when this specific one is in the URL...
Cheers
--
View this message in context:
http://www.nabble.com/Strange-error-with-shards-tp25027486p25027486.html
Sent from the
22 matches
Mail list logo
