[RFE] juju agent prefer the closest controller
Bug #1747924 reported by
Felipe Reyes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
There are scenarios where a user wants to deploy a juju controller in HA and each unit in a different place (for example: 1 unit's controller per rack) so it would be desired that juju agents running in servers in rack A connect (if possible) to the controller in rack A.
In the case of racks having a juju agent in rack B connect to a controller in rack A may not impact the performance of the system, but we found at least one user chose to deploy the controller (a single controller in HA = 3 machines) across regions, so the latency was impacting the performance.
Currently the agent shuffles the list stateaddresses , an idea is to instead of shuffling choose the IPs that belong to the same subnet where the agent is.
| Changed in juju: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| importance: | Wishlist → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.