cloud-scripts | Configuration scripts for cloud instances | AWS library

I fixed the problem by using the Redhat OpenJDK UBI image (ubi8/openjdk-8)

You will have to add the following lines in your dockerfile. I have also added redhat UBI image link for reference.

Hope this helps anyone else who may get stuck :)

No, it is not possible. You need Solr running, you hit this Collections api endpoint to create the collection. And this endpoint is served by Solr

This question was recently discussed on the solr-user mailing list and the conclusion was the same, you need to have Solr running in order to create a collection.

One suggestion to work around this limitation is to write a script that waits for the appropriate number of nodes to become available before calling the collections API endpoint to create the collection. An example python script is mentioned in the email thread that is capable of doing this.

Sets of configuration are usually found in a directory called /configs. If the zookeeper is dedicated to solr this is usually at the top level, if it's used by multiple applications it's common to "zk chroot" the configs to a sub directory.

Once you find the right location in zookeeper, one directory in the configs directory should match the name shown as "config-name" in the admin UI under Collections > name_of_your_collection

If your project uses gradle, the up/down load of configs from the project (where you might want to check these things into version control) can be smoothed somewhat by a plugin (disclaimer: I wrote this plugin)

https://plugins.gradle.org/plugin/com.needhamsoftware.solr-gradle

There's an additional complication to be aware of however, if the collection is using managed schema, the acutal schema in use will not be in schema.xml, but in a file called "managed-schema"

Fields may have been added via the Schema Rest API, so "files used to create the collection" is a bit fuzzy in that respect, but the managed_schema can be renamed to schema.xml and the solr config modified to take things out of managed mode if you want.

The solution is as simple as follows: The 'solrconfig.xml' file was located @ /server/solr/web/conf/solrconfig.xml I have to move it to/server/solr/web/ and then upload to ZooKeeper.

This is probably caused by Solr detecting its own, wrong IP on startup, and thus, using the wrong IP when registering the node in the Solr cluster.

You can tell Solr which IP to use by giving the embedded Jetty container the IP to use (or for only intra-node communication, using SOLR_HOST should be enough).

Someone asked me how to ensure that Solr is exposed exclusively on a server’s internal IP address so I thought this bit of information would be useful more generally. On Linux, edit the solr.in.sh file, find the property called SOLR_HOST (it is commented out by default) and set its value to the IP address or the host name that you want Solr to listen for requests.

SOLR_HOST="192.168.1.55"

The procedure is similar on Windows, except that the file to be edited is solr.in.cmd.

It was pointed out to me later that setting SOLR_HOST is not enough because the host/IP set by that property is only used by SolrCloud for making inter-shard requests. We also need to set a property used by Jetty in solr.in.sh or solr.in.cmd:

SOLR_OPTS="$SOLR_OPTS -Djetty.host=192.168.1.55"