| 2017-08-21 21:35:09 |
Mike Pontillo |
bug |
|
|
added bug |
| 2017-08-21 21:35:34 |
Mike Pontillo |
description |
MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.)
MAAS should throttle consecutive updates. (For example, when the first DNS change occurs, schedule a task for a few seconds in the future which will update DNS, and don't ever schedule more additional updates while that task is pending.) |
MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.)
MAAS should throttle consecutive updates. (For example, when the first DNS change occurs, schedule a task for a few seconds in the future which will update DNS, and don't ever schedule more additional updates while that task is pending.)
See also: bug #1710308. |
|
| 2017-08-22 00:13:28 |
Mike Pontillo |
summary |
[2.2] MAAS should batch multiple DNS changes into a single reload request |
[2.2] MAAS should avoid updating DNS if nothing changed |
|
| 2017-08-22 00:16:03 |
Mike Pontillo |
description |
MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.)
MAAS should throttle consecutive updates. (For example, when the first DNS change occurs, schedule a task for a few seconds in the future which will update DNS, and don't ever schedule more additional updates while that task is pending.)
See also: bug #1710308. |
MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.)
By checking the zone serial (per bug #1710308), MAAS now implicitly throttles reloads. But what it does NOT do is ensure that a DNS update is *necessary* (results in a change to the current DNS zone).
For example, MAAS may receive notification of an updated StaticIPAddress due to the DHCP server committing a new lease. Right now, this may trigger a DNS update, when nothing has actually changed. |
|
| 2017-08-22 14:43:31 |
Felipe Reyes |
tags |
|
sts |
|
| 2017-08-22 16:18:29 |
Andres Rodriguez |
marked as duplicate |
|
1711700 |
|
