[Dnsmasq-discuss] How does DNSMASQ handle large concurrent configure file updating request requests

Sun Feb 15 22:49:25 GMT 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 15/02/15 06:15, Yongkang You wrote:
> On Sun, Feb 15, 2015 at 4:11 AM, Simon Kelley
> <simon at thekelleys.org.uk> wrote:
> 
>> Got it. Do you have --no-hosts set? That would explain why it
>> was working for me and not for you.
>> 
>> I just pushed the fix to git.
>> 
> 
> Your guessing is completely right! I am using no-hosts in
> dnsmasq.conf. Now the new codes work greatly in my environment.
> 
> But another issue I found is, the IP binding can't be really
> released even after remove the config files and manually call
> dhcp_release. So when I create another VM with the same IP address,
> it will report duplication.
> 
> dnsmasq.log is something like: --------------- Feb 15 06:12:45
> dnsmasq-dhcp[3521]: DHCPRELEASE(eth2) 10.11.0.3 fa:e1:51:0b:a5:00 
> ...
> 
> Feb 15 06:13:13 dnsmasq[3521]: inotify, new or changed file 
> /etc/hosts.dhcps//fa:e9:4a:40:7f:00 Feb 15 06:13:13
> dnsmasq-dhcp[3521]: read /etc/hosts.dhcps//fa:e9:4a:40:7f:00 Feb 15
> 06:13:13 dnsmasq[3521]: duplicate dhcp-host IP address 10.11.0.3
> at line 1 of /etc/hosts.dhcps//fa:e9:4a:40:7f:00
> 
> .... Feb 15 06:13:23 dnsmasq-dhcp[3521]: DHCPDISCOVER(eth2)
> fa:e9:4a:40:7f:00 no address available Feb 15 06:13:26
> dnsmasq-dhcp[3521]: DHCPDISCOVER(eth2) fa:e9:4a:40:7f:00 no address
> available
> 
> ---------------
> 
> Anything wrong?
> 

The current code doesn't do anything when a file is deleted. To make
that have an affect, you're back to sending SIGHUP to clean out the
data and re-read the current set of files.

I'm pretty sure I mentioned that way back.

If deleting lots of VMs one-at-time is something that will happen,
then we need to look at solving that, but my impressiion is that it's
not something openstack does often? Am I wrong?

Cheers,

Simon.