[openstack-dev] [designate] Designate performance issues
vinod.mang at RACKSPACE.COM
Thu Mar 19 14:11:14 UTC 2015
Thank you for reporting the bug. The number of records does not seem too high. At this point I do not have a suggestion to improve the situation, but I will investigate this. Could you file a bug report? Relevant log snippets would also be helpful.
From: stanzgy <stan.zgy at gmail.com<mailto:stan.zgy at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thursday, March 19, 2015 2:39 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [designate] Designate performance issues
Hi all. I have setup kilo designate services with powerdns backend and mysql innodb storage in a single node.
The services function well at first. However, after inserting 13k A records via API within 3 domains (5k, 5k, 3k for each), the service stops working.
designate-api returns 500 and many RPCs timeout
designate-central takes 100% cpu, seems trying hard updating domains but failed
designate-mdns also takes 100% cpu, flooded with "Including all tenants items in query results" logs
powerdns gets timeout errors during AXFR zones
The server doesn't seem to turn any better after suffering in this state for hours. What I could do to recover the service is to cleanup databases and restart the service.
My question is:
1. Is it not recommended to create too many records in a single domain?
2. Any suggestions to improve this situation?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev