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
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
On 11/6/2013 1:18 PM, kaustubh147 wrote:
I am attaching a small log file with debug option enabled.. log shows
following process
1. first start of solr cluster
2. create collection "collection1"
3. shutdown cluster
4. start cluster again
error is in only the 4th step...and it is coming after so
On 11/6/2013 2:03 PM, Chris Geeringh wrote:
--- In the case of Java 7, 1.7.0_40 and 1.7.0_45 have known problems with
Lucene/Solr.
Shawn, this is interesting. What are the problems, where are the documented?
https://issues.apache.org/jira/browse/LUCENE-5212
The issue comments say that one of
--- In the case of Java 7, 1.7.0_40 and 1.7.0_45 have known problems with
Lucene/Solr.
Shawn, this is interesting. What are the problems, where are the documented?
On 6 November 2013 20:18, kaustubh147 wrote:
> Hi,
>
> Here is my
> solr.xml
>
>
>
>
>
>
> ${host:}
> 28081
> /sol
Hi,
Here is my
solr.xml
${host:}
28081
/solr
IP1:2181,IP2:2181,IP3:2181/mysolr
15000
${genericCoreNodeNames:true}
${socketTimeout:0}
${connTimeout:0}
--
On 11/6/2013 11:53 AM, kaustubh147 wrote:
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 ?
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
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
On 10/31/2013 9:18 PM, kaustubh147 wrote:
> 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
10 matches
Mail list logo
