7.2 Set Up a Proxy to Access Solr Service on the Cluster In this section, we will demonstrate how to setup a proxy to access Solr service on the cluster. By following the steps below, you should be able to browse through Solr Admin UI with your local browser to reach all the indexed collections on the cluster. the following command to specify the hostname and port number for the Solr service on the cluster. This is port-forwarding via SSH, which creates a secure connection between a local computer and a remote machine through which services can be relayed. $ ssh -L 9983:solr2.dlrl:8983 <user>@hadoop.dlib.vt.edu Enter address in your browser, and you should be able to see the “localhost:9983/solr” Solr Admin UI. In the highlighted area, you can choose which collection you want to access. 7.3 Extend Solr with custom libraries Ultimately, Solr is a Java web application and as such is composed of compiled JAR containing classes to handle requests, create indexes, manage Solr cores and return search results. Additionally, Solr provides high degree of customizations as it allows its user to implement and set up custom behavior with the use of Solr plugins. This section contains information on how to configure the Solr with custom libraries and JARs. Currently, the only way to add user-written JARs to Solr is by uploading them directly to the file system of the machine running Solr service -- unlike indexes, Solr cannot import custom classes from HDFS. Additionally, if run in mode, every machine running Solr must contain a copy of the JAR files located under the same (absolute) file path. Solr loads libraries dynamically, via reflection, based on the instruction provided in solrconfig.xml. These libraries are only loaded once - when collection/core starts or restarts (is reloaded). As such, library update doesn’t require neither Solr restart nor administrative rights. Steps: Create a directory that will contain custom JAR files on all the machines running Solr service. Make sure this directory can be found at the same path for all of them.
7.2 Set Up a Proxy to Access Solr Service on the Cluster In this section, we will demonstrate how to setup a proxy to access Solr service on the cluster. By following the steps below, you should be able to browse through Solr Admin UI with your local browser to reach all the indexed collections on the cluster. the following command to specify the hostname and port number for the Solr service on the cluster. This is port-forwarding via SSH, which creates a secure connection between a local computer and a remote machine through which services can be relayed. $ ssh -L 9983:solr2.dlrl:8983 <user>@hadoop.dlib.vt.edu Enter address “localhost:9983/solr” in your browser, and you should be able to see the Solr Admin UI. In the highlighted area, you can choose which collection you want to access. 7.3 Extend Solr with custom libraries Ultimately, Solr is a Java web application and as such is composed of compiled JAR containing classes to handle requests, create indexes, manage Solr cores and return search results. Additionally, Solr provides high degree of customizations as it allows its user to implement and set up custom behavior with the use of Solr plugins. This section contains information on how to configure the Solr with custom libraries and JARs. Currently, the only way to add user-written JARs to Solr is by uploading them directly to the file system of the machine running Solr service -- unlike indexes, Solr cannot import custom classes from HDFS. Additionally, if run in mode, every machine running Solr must contain a copy of the JAR files located under the same (absolute) file path. Solr loads libraries dynamically, via reflection, based on the instruction provided in solrconfig.xml. These libraries are only loaded once - when collection/core starts or restarts (is reloaded). As such, library update doesn’t require neither Solr restart nor administrative rights. Steps: Create a directory that will contain custom JAR files on all the machines running Solr service. Make sure this directory can be found at the same path for all of them.
Solr_Final_Report.docx