You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Dennis Lawler (JIRA)" <ji...@apache.org> on 2013/05/01 18:38:15 UTC
[jira] [Created] (CLOUDSTACK-2299) New VM instantiations trigger 2
second DNS outage
Dennis Lawler created CLOUDSTACK-2299:
-----------------------------------------
Summary: New VM instantiations trigger 2 second DNS outage
Key: CLOUDSTACK-2299
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2299
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Network Controller, Network Devices
Affects Versions: 4.0.1, 4.0.0, pre-4.0.0
Environment: Virtual Router used for DHCP, DNS services
Reporter: Dennis Lawler
Every time a new VM is started up, there is a 2 second outage in DNS services that can cause problems in guest VMs that use the router VM for DNS.
For Cloudstack configurations using both DHCP and DNS services on the router VM (both implemented with dnsmasq), there is currently a 2 second DNS service outage every time a new VM is instantiated
The source of this outage is in edithosts.sh, which uses “service dnsmasq restart” to pick up the freshly added DNS and DHCP entries. Restarting the dnsmasq service triggers a sleep for 2 seconds after killing dnsmasq before starting it back up again.
See thread on dev@cloudstack.apache.org for discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira