zookeeper timeout issue

2013-12-16 Thread kaustubh147
Hi, Following warning message is filling our application logs very rapidly. This statement is printed every time application talks with zookeeper. [#|2013-12-13T08:33:03.023-0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=64;_ThreadName=Thread-2;|

how to remove documents which have been deleted from the database

2013-12-16 Thread kaustubh147
Hi, Glassfish 3.1.2.2 Solr 4.5 Zookeeper 3.4.5 We have set up a SolrCloud with 4 Solr nodes and 3 zookeeper instances. I have 5 cores with 1 shard/4 replica setup on each of them. One of our core is very small, and it takes less than one minute to index. We run full import on it every hour

Re: unable to load core after cluster restart

2013-11-12 Thread kaustubh147
Hi, So finally we got our jdk/jre upgraded to 1.6.0-33. but it didnt solve the problem. I am still seeing same write.lock error. I was able to solve the problem by changing the lock type from native to single. but I am not sure about other ramifications of this approach. Do you see any problems

Re: unable to load core after cluster restart

2013-11-06 Thread kaustubh147
Hi, I tried "simple" lock type too. It is throwing similar error... Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@/mnt/emc/app_name/data-prod-refresh/SolrCloud/SolrHome1/solr/collection1_shard1_replica2/data/index/write.lock at org.apa

Re: unable to load core after cluster restart

2013-11-06 Thread kaustubh147
Hi, Here is my solr.xml ${host:} 28081 /solr IP1:2181,IP2:2181,IP3:2181/mysolr 15000 ${genericCoreNodeNames:true} ${socketTimeout:0} ${connTimeout:0} --

Re: unable to load core after cluster restart

2013-11-06 Thread kaustubh147
Hi All, I have further investigated the difference between both the environments. We have JDK 1.6.0_17 (VM 14.3-b01)on UAT and JDK 1.6.0_33 (VM 20.8-b03)on QA1. Can it be the reason behind this error? Is there a recommended jdk version for SolrCloud ? Thanks, Kaustubh -- View this message i

Re: unable to load core after cluster restart

2013-11-02 Thread kaustubh147
Hi Shawn, One thing I forget to mention here is the same setup (with no bootstrap) is working fine in our QA1 environment. I did not have the bootstrap option from start, I added it thinking it will solve the problem. Nonetheless I followed Shawn's instructions, wherever it differed from my old a

Re: Problem with glassfish and zookeeper 3.4.5

2013-10-31 Thread kaustubh147
Thanks Shawn, I found a bug in my code, it was creating too many CloudSolrServer objects. Thanks Kaustubh -- View this message in context: http://lucene.472066.n3.nabble.com/Problem-with-glassfish-and-zookeeper-3-4-5-tp4097635p4098732.html Sent from the Solr - User mailing list archive at Nab

unable to load core after cluster restart

2013-10-31 Thread kaustubh147
Hi, Glassfish 3.1.2.2 Solr 4.5 Zookeeper 3.4.5 We have set up a SolrCloud with 4 Solr nodes and 3 zookeeper instances. I start the cluster for the first time with bootstrap_conf= true All the nodes starts property.. I am creating cores (with the same name) on all 4 instances. I can add

Problem with glassfish and zookeeper 3.4.5

2013-10-24 Thread kaustubh147
Hi, Glassfish 3.1.2.2 Solr 4.5 Zookeeper 3.4.5 We have set up a SolrCloud with 4 Solr nodes and 3 zookeeper instances. It seems to be working fine from Solr admin page. but when I am trying to connect it to web application using Solrj 4.5. I am creating my Solr Cloud Server as suggested on the w

Solr on glassfish with multiple nodes - problem in data import

2013-08-09 Thread kaustubh147
Hi, We have Solr installed on Glassfish cluster which has 4 nodes and we have a single solr.data directory which is shared among all 4 nodes. When I trigger full data import on one of the cores on the server, because it is a http request, it goes to one of the nodes on the cluster. Now after the

Why Solr slows down when accessed thru load balancer

2013-07-25 Thread kaustubh147
Hi, When I am connecting my application to solr thru a load balancer (https://domain name/apache-solr-4.0.0), it is significantly slow. but if I connect Solr directly (https://11.11.1.11:8080/apache-solr-4.0.0) on the application server it works better. Ideally use of load balancer should give b