Bug 1024990
| Summary: | [DWH] ETL process doesn't recover from postgres restart | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Barak Dagan <bdagan> | ||||
| Component: | ovirt-engine-dwh | Assignee: | Yaniv Lavi <ylavi> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Barak Dagan <bdagan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.3.0 | CC: | acathrow, bazulay, bdagan, iheim, juan.hernandez, mperina, pstehlik, Rhev-m-bugs, yeylon, ylavi | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | 3.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | infra | ||||||
| Fixed In Version: | IS25 - rhevm-dwh-3.3.0-23.el6ev.noarch.rpm | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-01-21 15:01:45 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1028216 | ||||||
| Bug Blocks: | 1038284 | ||||||
| Attachments: |
|
||||||
Please recreate using SI21 Yaniv Martin, DWH Heartbeat seems to stop working after restart of postgres. Do tou have a clue to why this is? Yaniv It's not a problem of DWH HeartBeat, but it's probably a bug in JBoss EAP 6.1+. DWH Heartbeat works properly on oVirt master using JBoss 7.1.1 According to the JBoss team adding <validate-on-match>true</validate-on-match> to the data source definition should fix the issue with reconnecting to the database. http://gerrit.ovirt.org/21634 Please check. *** Bug 1034272 has been marked as a duplicate of this bug. *** As cam be seen in https://bugzilla.redhat.com/show_bug.cgi?id=1034272. it continues (In reply to Barak Dagan from comment #8) > As cam be seen in https://bugzilla.redhat.com/show_bug.cgi?id=1034272. it > continues Barak, did you apply the patch before testing? I tried this today on is24.2 with patch applied and ovirt-engine now works correctly after db is started again. So IMHO the patch should solve the issue ... This bug is currently attached to errata RHEA-2013:15116. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. Verified on IS26, rhevm-dwh-3.3.0-24.el6ev.noarch. dwh doesn't log connectivity errors when engine or db services are down for a short time (few minutes) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0036.html |
Created attachment 817543 [details] dwh log Description of problem: During reports installation, the engine shuts down and restart when installation is over. ETL process continue to flood the log with connectivity issues, untill it is manually restarted Version-Release number of selected component (if applicable): is20.1 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: