My SolrJ client uses ConcurrentUpdateSolrServer to index > 50Gs of docs to a
SOLR 3.6 instance on my Linux box. When running the same client against
SOLR 4.2.1 on EC2 I got the following:
SolrJ client error
request: http://ec2-
Shawn,
I didn't sanitize the log other than the ec2 servername. The constructor is
ConcurrentUpdateSolrServer solrServer
= new ConcurrentUpdateSolrServer(solrUrl,
solrBufferCount, solrThreadCount);
and I don't use setParser at all.
But the SolrJ client is using
This is resolved, I switched in the 4.2.1 jars and also corrected a mismatch
between the compile and runtime JDKs, for some reason the system was
overriding my JAVA_HOME setting (6.1) and running the client with a 5.0 JVM.
I did not have to use setParser.
I did try running the 'new' 4.2.1 SolrJ c
I know this issue has been answered somewhere.
I've got SolrCloud running under Tomcat 6, the respective settings are
tomcat6.conf
---
I am deliberately running Tomcat on 80 but on SOLR I stuck with 8983 because
it appears
That worked. Thanks both of you (Hoss too).
I had in fact set the solr.xml hostPort on both shards to 80 earlier to
match Tomat. But I kept getting
INFO: Update state numShards=null message={
"operation":"state",
"core_node_name":"10.x.x.105:8983_solr_mycore",
"numShards":null,
"shard":