FW: Problem accessing /solr/_shard1_replica_n1/get

-----Original Message-----
From: Hendrik Haddorp [mailto:hendrik.haddorp@gmx.net]
Sent: 23 March 2018 15:38
To: solr-user@lucene.apache.org
Subject: Problem accessing /solr/<collection-name>_shard1_replica_n1/get

Hi,

I have a Solr Cloud 7.2.1 setup and used SolrJ (7.2.1) to create 1000
collections with a few documents. During that I got multiple times in the
Solr logs exceptions because an access of the /get handler of a collection
failed. The call stack looks like this:
    at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClien
t.java:607)
    at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java
:255)
    at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java
:244)
    at
org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1219)
    at
org.apache.solr.handler.component.HttpShardHandler.lambda$submit$0(HttpShard
Handler.java:172)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at
com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(In
strumentedExecutorService.java:176)
    at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$e
xecute$0(ExecutorUtil.java:188)
    at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
49)
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
24)
    at java.lang.Thread.run(Thread.java:748)

I did not define a /get request handler but I also don't see one being
default in the solrconfig.xml files that come with Solr 7.2.1. Do I need to
add that as described in
https://www.garysieling.com/blog/fixing-solrj-error-expected-mime-type-appli
cationoctet-stream-got-texthtml
or is there something wrong in Solr? Is Solr doing those /get calls? My
program is not doing any, unless SolrJ does them under the covers, and is
actually not showing any error.

regards,
Hendrik