-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large Number of Records? #104
Comments
Wow! That is a lot of records! That kind of use case is probably better served via a different implementation. This module makes heavy use of concat, which is not very efficient. Can you tell me more about your use case and how you use this module? Maybe I could suggest some alternatives? |
We were looking to automate management of bind for all of our dns zones and On Tue, Apr 28, 2015 at 7:49 PM, Kyle Anderson notifications@github.com
|
But do they need to be defined in the puppet DSL? |
no, they just need to be automated...they all fit within the constraints of On Wed, Apr 29, 2015 at 7:24 AM, Kyle Anderson notifications@github.com
|
I got past the timeouts with:
in puppet.conf Also had to increase java memory maximums in /etc/sysconfig/pe-puppetdb and --Alex On Wed, Apr 29, 2015 at 9:02 AM, Alex Scoble bloggingitguy@gmail.com
|
Ok. Certainly do what you need to do. I personally think this module is not the right tool for the job to scale to thousands of records and thousands of domains. This is certainly true if many of them are DNAMEs or can be easily templated. Or, if you do need to scale and must use puppet, you could do a thing where you slave to a different server for subdomains or a subset of zones, to separate the megazones into smaller domains. I don't know if that is possible in your use case, but it works for many. (.dev, .stage, .prod, etc) We can keep this issue here for others who need to search, or we can reference back to it in the future. |
We're getting timeouts when trying to do puppet runs with large number of zones (5000+) and records (5000+)...is anyone using this module with a large amount of records successfully?
The text was updated successfully, but these errors were encountered: