Bug 102576
| Summary: | Lucene search index lock files cause errors | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Web Application Framework | Reporter: | Daniel Berrangé <berrange> |
| Component: | other | Assignee: | ccm-bugs-list |
| Status: | CLOSED WONTFIX | QA Contact: | Jon Orris <jorris> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | nightly | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-09-02 17:21:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 108447 | ||
Closing old tickets |
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314 Description of problem: Every so often we start receiving errors in the logs referring to lock files on the Lucene search index: 2003-08-18 11:03:09,271 [ead-3] ERROR lucene.Indexer - java.io.IOException: Index locked for write: Lock@/var/ccm-devel/web/dan/aplaws/logs/lucene-index/write.lock I believe this happens if you shutdown the server while the background indexer thread is in the middle of updating the index. It happens most frequently in development systems, but also sometimes on live servers. It always becomes apparent immediately after starting a server. Version-Release number of selected component (if applicable): How reproducible: Sometimes Steps to Reproduce: 1. Publish some content 2. Shutdown the server while the index is updating (rather tricky to schedule!) 3. Start up the server Actual Results: The following appears in the logs 2003-08-18 11:05:09,320 [ead-3] ERROR lucene.Indexer - java.io.IOException: Index locked for write: Lock@/var/ccm-devel/web/dan/aplaws/logs/lucene-index/write.lock Expected Results: No errors appear Additional info: We can probably solve this by simply removing the file: /var/ccm-devel/web/dan/aplaws/logs/lucene-index/write.lock upon server startup, however, we need to investigate whether there are any integrity issues with the index that could be caused by shutting down while the index it being updated.