Bug 747836
Summary: | Transaction failed when re-indexing full-text-search database | ||
---|---|---|---|
Product: | [Retired] Zanata | Reporter: | Sean Flanigan <sflaniga> |
Component: | Component-Logic | Assignee: | David Mason <damason> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ding-Yi Chen <dchen> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 1.4-SNAPSHOT | CC: | jwulf, zanata-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-23 04:32:33 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: | 756229 |
Description
Sean Flanigan
2011-10-21 05:29:52 UTC
Fixed in 1.4 and 1.5 Reindexing is now a global action so does not depend on an individual session. Errors still occur on some reindex operations, but it should now be easier to detect a failed reindex through the GUI and re-run as appropriate. https://github.com/zanata/zanata/compare/fbc68a29faf35486959833c8533967478d4c47c5...252016b6d4f56336166c76b144a3b7363743ef21 VERIFIED with Zanata version 1.4.3-alpha-3-SNAPSHOT (20111128-1320) Zanata version 1.5-SNAPSHOT (20111129-0927) For the release notes: How do you detect a failed reindex from the GUI? RELEASE NOTES TEXT: Cause: Database reindexing was implemented in an individual session. Consequence: A reindex operation on a large database could time-out rather than complete. When this occurred, some entries were not indexed. Fix: Database reindexing is now a global action, and no longer depends on an individual session. Result: Timeouts during reindexing operations are now less frequent, and when they do occur they are reported in the administrative interface, where they can be detected and the reindex operation performed again. QUESTION: How do you detect them through the GUI and how do you kick off the reindexing operation? ANSWER: Sign in as an administrator. Navigate to Administration -> Manage Search If a reindex operation is not in progress, a button labeled "Re-index full text search database" is visible. This begins a full text search. If no error message is shown on this page, the most recent reindex operation since server restart was successful. No error message is shown if no reindex operation has been run since server restart, even if the most recent reindex before server restart failed. If a reindex operation is in progress, a progress bar is shown. If the most recent reindex operation failed, an error message is shown (generic for full text search, server log should give more specific information), the progress bar should be visible showing how much of the reindex operation was successful, and the "Re-index full text search database" button should be visible. The "Manage Search" page may be blank occasionally - refreshing the page will fix this. |