We have done the solr cloud setup:
In one machine
1. Centos 6.3
2. Apache solr 4.1
3. JbossasFinal 7.1.1
4 .ZooKeeper 
Lets setup the zookeeper cloud on 2 machines

download and untar zookeeper in /opt/zookeeper directory on both servers
solr1 & solr2. On both the servers do the following

root@solr1$ mkdir /opt/zookeeper/data
root@solr1$ cp /opt/zookeeper/conf/zoo_sample.cfg
/opt/zookeeper/conf/zoo.cfg
root@solr1$ vim /opt/zookeeper/zoo.cfg
Make the following changes in the zoo.cfg file

dataDir=/opt/zookeeper/data
server.1=solr1:2888:3888
server.2=solr2:2888:3888
Save the zoo.cfg file.
ssign different ids to the zookeeper servers

on solr1

root@solr1$ cat 1 > /opt/zookeeper/data/myid

on solr2

root@solr2$ cat 2 > /opt/zookeeper/data/myid

Start zookeeper on both the servers

root@solr1$ cd /opt/zookeeper
root@solr1$ ./bin/zkServer.sh start
Note : in future when you need to reset the cluster/shards information do
the following

4.RAM-2GB
5.set the heap size to 1GB
Extracted the solr.war and change the solr home in web.xml of solr.
In bin folder of jboss ,the JAVA_OPTS parameter has been set in
standalone.conf
java -DzkHost=solr1:2181,solr2:2181 -Dbootstrap_confdir=solr/corename/conf/
-DnumShards=2

Restart the jboss

In another machine

1. Centos 6.3
2. Apache solr 4.1
3. JbossasFinal 7.1.1
4.RAM-2GB
5.set the heap size to 1GB
Extracted the solr.war and change the solr home in web.xml of solr.
In bin folder of jboss ,the JAVA_OPTS parameter has been set in
standalone.conf

Restart the jboss

Everything has been  done properly.
But it is taking too much time to upload data into solr.
It is taking more time than uploading data with one solr without shard
concept
Able to view two shards in solr cloud option present in ui.
Please explain how the larger index splits and allocated in two shards.

Please suggest some optimization techniques.





--
View this message in context: 
http://lucene.472066.n3.nabble.com/Solr-cloud-Performance-Problems-tp4107392.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to