Remove cluster aware updating


18-Mar-2015 22:25

I’m describing for one tomcat instance and similarly follow the same steps for other two tomcat servers with appropriate values (Solr home, app server port no.) #! - [email protected]_HOME=$(/usr/libexec/java_home) # run JVM in server mode JAVA_OPTS="$JAVA_OPTS -server" # memory JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx2048m" JAVA_OPTS="$JAVA_OPTS -XX: Perm Size=64m -XX: Max Perm Size=128m -XX:+Use G1GC" # Timezone and JVM file encoding JAVA_OPTS="$JAVA_OPTS -Duser.timezone=UTC -Dfile.encoding=UTF8" # home = Zoo Keeper client timeout SOLR_OPTS="home=/Users/jeeva/dc-1/solr/home1 -Dhost=solr1.-Dport=7070 -Dhost Context=solr -Dzk Client Timeout=20000 -Dzk Host=localhost:2181,localhost:2182,localhost:2183,localhost:2184,localhost:2185" JAVA_OPTS="$JAVA_OPTS $SOLR_OPTS""home=/Users/jeeva/dc-1/solr/home1 -Dhost=solr1.-Dport=7070 -Dhost Context=solr -Dzk Client Timeout=20000 -Dzk Host=localhost:2181,localhost:2182,localhost:2183,localhost:2184,localhost:2185" SOLR_OPTS="home=/Users/jeeva/dc-1/solr/home1 -Dhost=solr1.-Dport=7070 -Dhost Context=solr -Dzk Client Timeout=20000 -Dzk Host=localhost:2181,localhost:2182,localhost:2183,localhost:2184,localhost:2185/solr""home=/Users/jeeva/dc-1/solr/home1 -Dhost=solr1.-Dport=7070 -Dhost Context=solr -Dzk Client Timeout=20000 -Dzk Host=localhost:2181,localhost:2182,localhost:2183,localhost:2184,localhost:2185/solr"Let’s make use of Solr Collections and Core Admin API’s to create collection, shard(s), Replica(s) and replication factor.Design phase is considered to be a vital & crucial phase of the project.We are going to execute the following design plan for designing Solr Cloud cluster.For this article I’m planning to use example configuration shipped with Solr 4 artifacts.$ java -classpath .:/Users/jeeva/dc-1/solr-cli-lib/* org.cloud. Zk CLI -cmd upconfig -zkhost localhost:2181,localhost:2182,localhost:2183,localhost:2184,localhost:2185 -confdir /Users/jeeva/dc-1/config-files -confname myconf $ java -classpath .:/Users/jeeva/dc-1/solr-cli-lib/* org.cloud. [zk: localhost:2181(CONNECTED) 0] [zk: localhost:2181(CONNECTED) 1] ls / [configs, collections, zookeeper] [zk: localhost:2181(CONNECTED) 2] ls /configs [myconf] [zk: localhost:2181(CONNECTED) 3] ls /configs/myconf [admin-extra.menu-top.html, currency.xml, protwords.txt, mapping-Fold To ASCII.txt, solrconfig.xml, stopwords.txt, lang, spellings.txt, mapping-ISOLatin1Accent.txt, admin-extra.html, xslt, synonyms.txt, scripts.conf, update-script.js, velocity, elevate.xml, admin-extra.menu-bottom.html, schema.xml] [zk: localhost:2181(CONNECTED) 4] ls /collections [europe-collection] [zk: localhost:2181(CONNECTED) 5]In this section we will be setting up tomcat instance(s) and Solr Cloud Cluster.

However the design plan can be executed / simulated cross multiple boxes.

Data Center is represented as /Users/jeeva/dc-1 Solr home for respective Solr Node(s) /Users/jeeva/dc-1/solr/home1 /Users/jeeva/dc-1/solr/home2 /Users/jeeva/dc-1/solr/home3 Tomcat 7 home for respective Solr Node(s) /Users/jeeva/dc-1/tomcat1 /Users/jeeva/dc-1/tomcat2 /Users/jeeva/dc-1/tomcat3 Solr Cloud Configuration Directory /Users/jeeva/dc-1/config-files Solr Zk CLI [Command Line Interface] Libraries /Users/jeeva/dc-1/solr-cli-lib Every organization is unique and has its own requirement and hence create Solr configuration files adhering to the unique business requirements of the the organization.