Issue faced while re-starting solr 6.1.0 after cleaning zk data.

2016-08-07 Thread Naveen Pajjuri
Hi, I'm trying to move to solr-6.1.0. it was working fine and i cleaned up zk data (version folder) and restarted solr and zookeeper. I started getting this error. - *sample_shard1_replica1:* org.apache.solr.common.cloud.ZooKeeperException:org.apache.solr.common.cloud.ZooKeeperException: Sp

Re: Issue faced while re-starting solr 6.1.0 after cleaning zk data.

2016-08-07 Thread Naveen Pajjuri
Here sample is the name of my collection. Thanks On Sun, Aug 7, 2016 at 3:10 PM, Naveen Pajjuri wrote: > Hi, > I'm trying to move to solr-6.1.0. it was working fine and i cleaned up zk > data (version folder) and restarted solr and zookeeper. I started getting > this error. > > >- *sample_s

RE: Issue faced while re-starting solr 6.1.0 after cleaning zk data.

2016-08-07 Thread Ritesh Kumar (Avanade)
Hi Naveen, I had the same issue, I did the below steps to fix it. 1. Stop SOLR service across all Solr VM’s. 2. Stop ZooKeeper service in all ZK VM’s. 3. Rename all the log files again eg: _log.1 [cid:image001.png@01D1F0C5.D8D498D0] 4. Start ZooKeeper service in al

Re: Issue faced while re-starting solr 6.1.0 after cleaning zk data.

2016-08-07 Thread Shalin Shekhar Mangar
Hi Naveen, When you cleaned up the zk data, it also removed the configuration files that are stored in Zookeeper. These configuration files are used by Solr and therefore they can no longer be found. You need to upload those configuration files again to ZK using: bin/solr zk upconfig -d /path/to/

Unique key field type in solr 6.1 schema

2016-08-07 Thread Bharath Kumar
Hi All, I have an issue with cross data center replication, when we delete the document by id from the main site. The target site document is not deleted. I have the id field which is a unique field for my schema which is configured as "long". If i change the type to "string" it works fine. Is th

RE: Solr Cloud with 5 servers cluster failed due to Leader out of memory

2016-08-07 Thread Tim Chen
Hi Erick, Shawn, Thanks for following this up. 1, For some reason, ramBufferSizeMB in our solrconfig.xml is not set to 100MB, but 32MB. In that case, considering we have 10G for JVM, my understanding is we should not run out of memory due to large number of documents being added to Solr. Just

RE: Solr Cloud with 5 servers cluster failed due to Leader out of memory

2016-08-07 Thread Tim Chen
Sorry Erick, forgot to answer your question: No, I didn't increase the maxWarmingSearchers. It is set to 2. I read it somewhere that increasing this is a risk. Just to make sure, you didn't mean the "autowarmCount " in the -Original Message- From: Erick Erickson

Re: Solr Cloud with 5 servers cluster failed due to Leader out of memory

2016-08-07 Thread Erick Erickson
You're correct on maxWarmingSarchers, and autowarming isn't really a concern since you're not exceeding maxWarmingSearchers. Wait... the error is a _tomcat_ error according to the stack trace. If this were the internals of Solr you'd be seeing org.apache.solr in there somewhere. I've seen the "una