Hi Graham, thanks for your suggestion. But in fact the initial import was a
simple while-curl scripts with no concurrency.
With this script, a request will not be sent unless previous one gets
reponse from designate-api. So I think it's not the rate of initial
importing but the number of records th
Hi vinod, thanks for you reply. I have report a bug with related log
snippets here:
https://bugs.launchpad.net/designate/+bug/1434479
On Thu, Mar 19, 2015 at 10:11 PM, Vinod Mangalpally <
vinod.m...@rackspace.com> wrote:
> Hi Zhang,
>
> Thank you for reporting the bug. The number of records do
Hi Zhang,
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.
--vinod
From: stanzgy mailto:stan.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/19/2015 07:41 AM, stanzgy wrote:
> 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 d
