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.
Related
I am using apache solr in backend to provide search in my website. As solr is using jetty as server. I have changed jetty.xml to enable request.log file. Now I have to enable it in running setup. I cannot restart solr. How I can made these changes visible in running setup.
Not sure, I have not tried, but given that Jetty use internally log4j, you can use JMX.
Log4j registers its loggers as JMX MBeans. Using the JDK's jconsole.exe
you can reconfigure each individual loggers. These changes are not persistent
and would be reset to the config as set in the configuration file
after you restart your application (server).
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.
Ok, so I'm trying to setup nutch to crawl a site and index the pages into solr. I'm currently using Nutch 1.9 with Solr 4.10.2
I've followed these instructions: http://wiki.apache.org/nutch/NutchTutorial#A4._Setup_Solr_for_search
The crawling appears to go just fine but when I check the collection on Solr (using the web ui) there are no documents indexed...any idea where I could check for problems?
Found my problem, I'll leave it as an answer in case anyone else has the same symptoms:
My problem was the proxy configuration. My linux box has the proxy configured to be applied system-wide, but I also had to configure Nutch to use the same proxy. Once I changed that, it started to work.
The configuration is under config/nutch-default.xml
Edit with more info
To be more specific, here is the Proxy configuration I had to change:
<property>
<name>http.proxy.host</name>
<value>xxx.xxx.xxx</value>
<description>The proxy hostname. If empty, no proxy is used.</description>
</property>
I have a solr instance up and running and I can visit the solr admin page without any problem. I have setup a solr multicore with one core for ckan and another core for a different application. I can see two different collections as well in the admin page. I don't understand why ckan is not able to connect to Solr. I have even include solr site url in production.ini.
ckan.lib.search Problems were found while connecting to the SOLR server
Edit # 1: I have installed ckan from Source; I already had Solr running so all I did was added a new core & collection for ckan in an existing solr instance
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'.