In MAAS, we should: * throttle reloads (at least make sure a reload is complete before we trigger the next one) * monitor the actual service from the perspective of rackd's (perhaps have rackd's do a dig @region-controller for a name we send them whenever they talk to the region controller) * log loudly, kill and restart when the service monitoring fails
Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
