github-actions[bot] commented on issue #14172: URL: https://github.com/apache/cloudstack/issues/14172#issuecomment-5932641838
## ๐ฏ Triage report Reporter observes that with `db.ha.enabled=true` on MySQL 8.x, after the configured source becomes unreachable, the management server UI becomes extremely slow because the connector keeps retrying the dead source on (nearly) every request. Manually promoting the replica and pointing `db.cloud.host`/`db.usage.host` at it (per the install guide's Failover procedure) restores normal performance. A maintainer has already commented that this DB HA mechanism was likely never fully implemented/tested, and a candidate PR (#14279) has been opened to address it. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | `type:new-feature` | Maintainer comment indicates the existing `db.ha.enabled` client-side failover was never seriously implemented and should be treated as a new feature rather than a regression/bug fix. | | **Component** | `component:database`, `component:management-server`, `component:mysql` | Issue concerns MySQL connector failover behavior within the management server's DB HA configuration. | | **Severity** | n/a | Not labeled as a bug; classified as new-feature work per maintainer. | | **Labels** | type:new-feature, component:database, component:management-server, component:mysql, status:Has a PR | See reasoning above; `status:Has a PR` added since #14279 is linked. | | **Coding agent** | Suitable | Well-documented repro steps, config, versions, and a maintainer-linked candidate PR (#14279) already exist; mainly needs validation/testing by the reporter against that PR. | ### ๐ Similar issues No clearly duplicate or related open issues were found via search for "db.ha.enabled MySQL failover replica". <details><summary>๐ก Notes and suggestions</summary> - PR #14279 was opened in response to this issue โ worth asking `@nabassa1323` to validate it against their reproduction steps (2 MS nodes, GTID replication, source outage simulation). - Consider updating the admin guide (currently references MySQL 5.1/5.5 testing) once the fix/feature lands, to reflect supported MySQL 8.x behavior and clarify whether manual promotion remains the documented production path. - Relevant connector settings called out by reporter: `secondsBeforeRetrySource`, `queriesBeforeRetrySource`, `initialTimeout` โ may need tuned defaults or documentation if the new implementation still relies on MySQL Connector/J failover semantics. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/36869901112) ยท sonnet50 77.8K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) > <details> <summary>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 36869901112, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/36869901112 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
