| Summary: | Solr LOCK_FAILURE error appears during Git fetch | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mark Macdonald <mamacdon> | ||||||
| Component: | Server | Assignee: | Project Inbox <orion.server-inbox> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P3 | CC: | ahunter.eclipse, john.arthorne | ||||||
| Version: | 3.0 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Mark Macdonald
Created attachment 235722 [details] server log of LOCK_FAILURE This entry looks particularly bad: > 2013-09-23 10:27:03.823 [Finalizer thread] ERROR o.apache.solr.update.SolrIndexWriter - SolrIndexWriter was not closed prior to finalize(), indicates a bug -- POSSIBLE RESOURCE LEAK!!! I think you might have two servers running simultaneously? I also see: java.lang.Exception: Error starting Jetty on port: 8080 ... org.eclipse.equinox.http.jetty.JettyConfigurator.MasterJetty : Address already in use: bind The file it is trying to lock is a lock on the lucene search index file. No other thread should ever even know about this file, but if there are multiple copies of orion running it could be in contention with the lucene running in the other instance. Ok, I guess that log is a total red herring. I tried it again, and I get the LOCK_FAILURE error again, but absolutely nothing printed to the server log. We are no longer using Apache Solr on the Orion server for search. |