Bug #1090
closed
When editing DHCP records, ISC backend times out if the number of subnets is large.
Added by Bash Shell almost 13 years ago.
Updated about 7 years ago.
Description
When adding hosts through Foreman, foreman-proxy times out if the number of subnets is large.
With 3k subnets, it takes 3-4 minutes to add the record.
In this time, the logs show that the proxy is "Enumerating hosts" for each subnet.
Something in-efficient is happening, and needs to be improved?
Files
could you provide (here or privately) an example of such configuration? its would be much easier to optimize this way.
thanks
After the holidays, I'll privately send a similar config file.
- Status changed from New to Need more information
I can't provide the company dhcpd.conf file.
But this is easy to re-produce.
Create a large number of subnets (say 500) and this problem happens.
Attached is a dhcpd subnets file which can be included in the main dhcpd.conf.
- Status changed from Need more information to New
- Related to Bug #5847: Successfully adds DHCP record, while GUI reports timeout added
I successfully used the isc provider to manage over 3000 subnets and while it was slow and took a while to load them each time, never had a timeout.
YMMV
- Related to Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy) added
- Description updated (diff)
- Category set to DHCP
- Status changed from New to Feedback
The inotify-related changes from ticket #2687 have now been made in develop (nightly) for 1.13, which should drastically reduce the amount of re-parsing of config/lease files during smart proxy requests and moves the bulk of the work to the service startup. I'm moving this ticket state to feedback as hopefully the next release will resolve this issue.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous