<p>This has worked - the following query has to return content-type application/xml:</p>

<pre><code> /solr/COLLECTION/select?q=*:*&amp;rows=0
</code></pre>

CC BY-SA 3.0
2017-11-16T15:35:26.603Z
2017-11-16T15:35:26.603Z
Ta Mu
<p>By current state of the art, we <a href="https://devops.stackexchange.com/questions/2016/defined-start-sequence-of-containers">cannot</a> enforce an ordered start sequence of service containers directly, neither in Docker Swarm nor in Kubernetes. (Maybe there is a standard solution for that via a specialized orchestraton service)</p>

<p>Now, imagine we want to have a Solr instance with considerable amount of data, and want to get it ready before other services can start their work.</p>

<p>What is the best way to verify this status?</p>

<p>It seems for example that calling and validating the expected list of loaded collections is not enough:</p>

<pre><code>/solr/admin/collections?action=LIST
</code></pre>

<p>Other ideas?</p>

<docker><kubernetes>
Waiting for Solr to load
Ta Mu
# Waiting for Solr to load

(Asked by: username_0 on 2017-11-15)

By current state of the art, we cannot enforce an ordered start sequence of service containers directly, neither in Docker Swarm nor in Kubernetes. (Maybe there is a standard solution for that via a specialized orchestraton service)
Now, imagine we want to have a Solr instance with considerable amount of data, and want to get it ready before other services can start their work.
What is the best way to verify this status?
It seems for example that calling and validating the expected list of loaded collections is not enough:
/solr/admin/collections?action=LIST

Other ideas?

**Tags:** docker, kubernetes


---

## 1 answers

### Answer by username_0 on 2017-11-16. Score: 1 | Accepted answer

This has worked - the following query has to return content-type application/xml:
 /solr/COLLECTION/select?q=*:*&rows=0


---

