Created
June 25, 2014 05:04
-
-
Save jayunit100/8bce967c3c86c94a7e2b to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The simplest way to start with SOLR is using a tarball, for example, the ones distributed by the ASF. | |
Extract the tarball, and go to the examples/ directory, where you can launch an embedded core. | |
Then, find the solrconfig.xml file. Edit it to contain the following xml: | |
<directoryFactory name="DirectoryFactory" class="org.apache.solr.core.HdfsDirectoryFactory"> | |
<str name="solr.hdfs.home">glusterfs:///solr</str> | |
<str name="solr.hdfs.confdir">/etc/hadoop/conf</str> | |
</directoryFactory> | |
This tells solr, when launched, to use gluster as the underlying file store. You also should make sure that glusterfs-hadoop jar, and the hadoop-common jar, are both on the classpath of the solr web server. To do so – you can update the solrconfig.xml jar directives. You can also copy the jars in at runtime, to be really safe. | |
Once your example core with gluster configuration is setup, launch it with the following properties: | |
java -Dsolr.directoryFactory=HdfsDirectoryFactory -Dsolr.lock.type=hdfs -Dsolr.data.dir=glusterfs:///solr -Dsolr.updatelog=glusterfs:///solr -Dlog4j.configuration=file:/opt/solr-4.4.0-cdh5.0.2/example/etc/logging.properties -jar start.jar | |
This starts a basic SOLR server on port 8983. | |
From here, you will want to make sure you are plugged into the gluster file system for backend storage. | |
If the launch works, then you will be able to see a healthy SOLR core running on http://mrg42.lab.bos.redhat.com:8983/solr/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment