I created a Solr collection from some existing schema and configuration using:
-d server/solr/classiccore1/conf
While I can see schema.xml and solrconfig.xml in the Solr Admin UI for a solr collection I just created, I can't find it on the filesystem.
My SolrCloud contains 2 nodes and 1 embedded zookeeper instance.
Is there any way to modify schema.xml on filesystem rather then using relevant APIs?
If you're using Solr in the cloud configuration, all the configuration files has to be available in the cluster - that means that the files are stored in Zookeeper, which keeps all the state and configuration for your cluster.
See Reloading Zookeeper solr conf (schema.xml), as well as the examples in the reference manual on how you upload a new configuration file or configuration set to Zookeeper.
Related
I am using SolrCloud on Windows and I need to upload OpenNLP model files(binary files) into Zookeeper. How can I do this?
Here are my related questions:
Can not apply patch LUCENE-2899.patch to SOLR on Windows
SolrCloud OpenNLP error Can't find resource 'opennlp/en-sent.bin' in classpath or '/configs/_default'
I am new in SOLR Cloud so sorry for this question. I am using 3 nodes of SOLR and now I need to update database setting in data-config.xml. But I have now idea how to do that.
In standalone SOLR we have data-config.xml and we can change in it, but I dont how to do this it in SOLR cloud.
Please help me.
data-config.xml is just another piece of a collection's configuration (if it needs it, not all collections have one). So you just get it ready, and then deploy it the same way you deploy schema.xml, by using bundled utilities:
bin\solr upconfig ...
Solr reload is not picking up the latest changes from Zookeeper.
Configuration Details:
Solr: 6.0.0
Zookeeper: 3.4.6
OS: AWS Linux
We are facing an issue that when we RELOAD an existing collection in solr to pick up the latest configuration from zookeeper (which we upconfig in Zookeeper) the changes are not reflected on the collection. We verified the same using the solr admin ui. But the changes we made were available on zookeeper, we have verified the same by connecting to zookeeper using zkcli.sh script.
Note: We are able to see the latest config picked correctly if we create a new collection based on the config we uploaded to zookeeper. Issue occurs only for the solr RELOAD call.
Please help us narrow down the issue.
I am implementing Solr Cloud for the first time. I've worked with normal Solr and have that down pretty well, but I'm not finding a lot on what you can and can't do with Solr Cloud. So my question is about Managed Resources. I know you can CRUD stop words and synonyms using the new RESTful api in solr. However with the cloud do I need to CRUD my changes to each individual solr server in the cloud, or do I send them to a different url that sends them through to each server? I'm new to cloud and zookeeper. I have not found anything in the solr wiki about working with the managed resources in the cloud setup. Any advice would be helpful.
In SolrCloud configuration and other files like stopwords, are stored and maintained by Zookeeper. Which means you do not need to individually send updates to each server.
Once you have SolrCloud, before putting in any data, you will create a collection. Each collection has its own set of resources/config folder.
So for example if u have a collection called techproducts with 2 servers localhost1 and localhost2 the below command from any of the servers will work on the same resource.
curl "http://localhost1:8983/solr/techproducts/schema/analysis/synonyms/english"
curl "http://localhost2:8983/solr/techproducts/schema/analysis/synonyms/english"
I am using apache solr and I have created another core and its works fine.But once i shutdown my server and restart it,the new core gets deleted. But the folder seems to be there in the solr dir.Can any one tell me why does it get deleted from my apache solr? Thanks in advance
Check for the persistent attribute in the solr.xml <solr persistent="true"> which will persist the changes made through Admin UI and these would be available after restarts as well.
If persistence is enabled (persist=true), the configuration for this
new core will be saved in 'solr.xml'.