Glad it's resolved, thanks for letting us know, it
removes some uncertainty.
Erick
On Mon, Feb 17, 2014 at 12:23 PM, Eric_Peng wrote:
> I solved it , my mistake
> I was using Solr4.6.1 jars, but in my solrconfig.xml I used
> LucenMatcheVersion 4.5
> I just coped from last project and didn't ch
I solved it , my mistake
I was using Solr4.6.1 jars, but in my solrconfig.xml I used
LucenMatcheVersion 4.5
I just coped from last project and didn't check it.
My really stupid mistake
--
View this message in context:
http://lucene.472066.n3.nabble.com/Could-not-connect-or-ping-a-core-afte
I found out in this stranger situation, I could import, update, or delete
data(using DIH or SolrJ)
But the query will waiting forever.
So I delete all the documents or just reduce the document number and then
restart the server, problem disappeared
--
View this message in context:
http://l
Sir, after I made experiment
if I there are more than 1000(roughly) documents in the core, the problem
will show up.
then I make a query in command window it shows
Exception in thread "main"
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Error
opening new searcher. exceeded
Last 3 lines of the log(only these have something special)
12:17:12
WARN
SolrResourceLoader
Solr loaded a deprecated plugin/analysis class
[solr.JsonUpdateRequestHandler]. Please consult documentation how to replace
it accordingly.
12:17:12
WARN
SolrResourceLoader
Solr loaded a deprecated plugin/a
More looking for log messages at the end of the log. There are a bunch of
messages that come out when you start up your server. Also look at enabling
more detailed logging, will take editing the log properties file since, if
you don't
find anything useful at the INFO level, you need to change thing
One another thing wield is that: If I just import a small data
everything goes very well.
Still have the same warnings in log but everything works fine
--
View this message in context:
http://lucene.472066.n3.nabble.com/Could-not-connect-or-ping-a-core-after-import-a-big-
I think I juse used hard Commit
// Make the docs we just added searchable using a "hard" commit
solr.commit(true, true);
--
View this message in context:
http://lucene.472066.n3.nabble.com/Could-not-connect-or-ping-a-core-after-import-a-big-data-into-it-tp4117416p4117432.html
S
Some warning...always,but no errors
12:00:23
WARN
SolrResourceLoader
Can't find (or read) directory to add to classloader:
../../../contrib/extraction/lib (resolved as:
D:\workspaceEE\TestSolr\solr\collection1\..\..\..\contrib\extraction\lib).
12:00:23
WARN
SolrResourceLoader
Can't find (or read)
You should check your server logs for error messages during startup related to
loading that core. Feel free to post them here if you can't parse them.
Thanks,
Greg
On Feb 14, 2014, at 10:14 AM, Eric_Peng wrote:
> Need help, Thx in advance.
>
> About import a big XML document (using DIH or Sol
when you restart the server, what do the logs show?
Take a look at the size of your transaction log. There's
a possibility that if you do not commit correctly, all the
data you put in the core is replaying on startup, see:
http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-a
11 matches
Mail list logo
