I've seen this error (or similar) reported due to permissions errors.
It's kind of a long shot but worth checking.
See the discussion at: https://issues.apache.org/jira/browse/LUCENE-7959
Best,
Erick
On Sun, Sep 17, 2017 at 9:24 AM, Ode3 wrote:
> HI all -
>
> I think I am seeing something s
HI all -
I think I am seeing something similar and I had just posted
https://issues.apache.org/jira/browse/SOLR-11361 a bit ago.
Starters - on my test bed I decided to update from 6.2.1 to 6.6.1. All
seemed okay until I restart Solr and the Core would not load. Going to
6.6.0 helped or at leas
Pls note that we are using Solr 6.4.2.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi Eric,
We are seeing the same issue on our production as well. Changing the
LockWriteTimeout to 5000 did not help. Please let me know if there are other
things we can try out to recover from this issue.
Thanks.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
I need to look at this a bit.
If either of you have the time/inclination, I have some anecdotal
evidence that if you specify
5000
in solrconfig.xml you won't see this problem. This is not a proper fix
of the root issue, but if you test this and don't see the error it'd
be a great help in me trac
On 8/26/2017 9:53 AM, Erick Erickson wrote:
> Setting loadOnStartup=false won't work for you in the long run,
> although it does provide something of a hint. Setting this to false
> means the core at that location simply has its coreDescriptor read and
> stashed away in memory. The first time you _
I am also seeing 2 threads loading the cores, I am using Solr 6.6.0.
On Sat, Aug 26, 2017 at 11:53 AM, Erick Erickson
wrote:
> Setting loadOnStartup=false won't work for you in the long run,
> although it does provide something of a hint. Setting this to false
> means the core at that location s
Setting loadOnStartup=false won't work for you in the long run,
although it does provide something of a hint. Setting this to false
means the core at that location simply has its coreDescriptor read and
stashed away in memory. The first time you _use_ that core an attempt
will be made to load it an
Hi Erick,
I spent some more time on this and found that if I modify 'core.properties'
to contain the following values (my core.propreties file is empty otherwise
and only being used for shard discovery), then the solr server works fine.
loadOnStartup=false
transient=false
The fact is that shards
Thanks Erik
I expected that but it is really not the case . I have only one core per
solr installation . Though i run 3 solr processes on each host.
If you see the thread names they are :coreLoadExecutor and qtp761960786-31
. If it was the case of two core pointing to one index (though it does not
In that case you probably have two different cores pointing to the
_same_ data directory. Examine your core.properties files and see if
any dataDir variables are set
Best,
Erick
On Fri, Aug 25, 2017 at 1:12 PM, Nawab Zada Asad Iqbal wrote:
> Ok, after looking at the logs for some more time,
Ok, after looking at the logs for some more time, i found that there are
more than one threads trying to load the core at startup time. This doesn't
make sense to me, is it configurable? Is there any reason why this is even
an option?
Aug 25, 2017 12:04:37 PM INFO (main) [ ] o.e.j.s.Server
jet
Hi,
I am getting this error. i have deleted the file and restarted the server,
but this error doesn't go away.
What should I do to fix it?
Caused by: org.apache.solr.common.SolrException: Error opening new searcher
at org.apache.solr.core.SolrCore.(SolrCore.java:977)
at org.apa
13 matches
Mail list logo
