Bug 1417708
| Summary: | ovirt-ha-agent should reuse json-rpc connections | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Troy Dash <ddash> | |
| Component: | ovirt-hosted-engine-ha | Assignee: | Simone Tiraboschi <stirabos> | |
| Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 3.6.7 | CC: | alukiano, baptiste.agasse, bgraveno, bugs, c.handel, cshao, dfediuck, eedri, fdeutsch, frolland, gveitmic, gwatson, jbelka, lsurette, mavital, michal.skrivanek, mwest, pkliczew, rbalakri, redhat, Rhev-m-bugs, sbonazzo, s.kieske, srevivo, stirabos, warlord, ycui, ykaul, ylavi | |
| Target Milestone: | ovirt-4.2.0 | Keywords: | Triaged, ZStream | |
| Target Release: | 4.2.0 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
Previously the ovirt-ha-agent would open a new json-rpc connection each time it communicated with VDSM. Now it will try and reuse an open connection if available to improve performance.
|
Story Points: | --- | |
| Clone Of: | 1349829 | |||
| : | 1471617 (view as bug list) | Environment: | ||
| Last Closed: | 2018-05-15 17:32:29 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1343005, 1349829, 1376843 | |||
| Bug Blocks: | 1383108, 1417709, 1457471, 1471617 | |||
|
Comment 1
Troy Dash
2017-01-30 18:02:56 UTC
*** Bug 1349829 has been marked as a duplicate of this bug. *** *** Bug 1383108 has been marked as a duplicate of this bug. *** The auto reconnect feature is just in json rpc client from 4.2; abandoning 4.1 patch and already ready on 4.2. Verified on ovirt-hosted-engine-ha-2.2.0-1.el7ev.noarch 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. https://access.redhat.com/errata/RHBA-2018:1472 BZ<2>Jira Resync |