Re: Read past EOF error due to broken connection

Hi Pravesh, I was just indexing some documents remotely on a single node instance when the connection broke. So, there isn't any manual copy that I did. I think I will go ahead and re-index. Just curious to know, if there is any option to specify the check-point for last commit and rollback to it

Re: Read past EOF error due to broken connection

Did you do manual copy of index from Master to Slave of servers. I suppose, it won't be copied properly. If this is the case, then you can check the size of indexes on both servers. Otherwise, you would've to recreate the indexes. Thanx Pravesh -- View this message in context: http://lucene.4720

Re: Read past EOF error due to broken connection

Hi Pravesh, Thanks for your reply. I tried both the approaches- Commit fails with this exception- Exception in thread "main" org.apache.solr.common.SolrException: Severe errors in solr configuration. Check your log files for more detailed information on what may be wrong. If you want solr to c

Re: Read past EOF error due to broken connection

First commit and then try again to search. You can also use lucene's CheckIndex tool to check & fix your index (it may remove some corrupt segments in your index) Thanx Pravesh -- View this message in context: http://lucene.472066.n3.nabble.com/Read-past-EOF-error-due-to-broken-connection-tp309