On 5/6/2013 1:25 PM, cleardot wrote:
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:
<snip>
SOLR 4.2.1 log error
======================================================
INFO: [mycore] webapp=/solr path=/update params={} {} 0 0
May 6, 2013 6:13:55 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: Missing ContentType
This isn't the first time I've seen empty params in a Solr log on this
list, but the other one was with 3.6.2 for both server and client. Is
"params={}" what actually got logged, or did you remove the stuff there
to sanitize your logs on a public list?
Are you by chance setting the response parser on your solr server object
to something besides the Binary (javabin) parser? If you are, could you
remove the setParser call in your client code? The only time you need
to change the parser is when you're using SolrJ with a version of Solr
that does not have the same javabin version. The javabin version was v1
in Solr 1.4.1 and earlier, then v2 in 3.1.0 and later. The other
response parsers are less efficient than javabin.
Thanks,
Shawn
