sync-domains generates 504 error due MessagingTimeout error

[Pavel Kirpichyov]

If designate has a lot of domains with records sync-domains command will throw MessagingTimeout.

api extension calls sync-domains method by rpc: https://github.com/openstack/designate/blob/master/designate/api/v1/extensions/sync.py#L31
and waiting result... but does not handle it

As option to fix problem it possible to use rpc cast method instead of call and return 202 HTTP response code.

[Graham Hayes (grahamhayes)]

we have a possible problem here...

to fix this, we would have to move the operation to an async method, which would be a breaking change in the API....

[Kiall Mac Innes (kiall)]

I think, as an admin only API with a real problem, we can do this.. That said.. I'd prefer to remove these methods entirely as the pools periodic functions are effectively doing just this..

[Federico Ceratto (federico-ceratto)]

The bug affects the V1 API and it does not affect newer releases.

[Abhilash Goyal (abhilash-goyal)]

Hello Pavel,
Your bug description says 'lot of domains', is there any finite number above which MessagingTimeout will be thrown. Kindly provide steps to replicate this bug.

[Pavel Kirpichyov (pavel-kirpichyov)]

Hello!
Unfortunately, I had finished my work with openstack and designate.
As I remember it was about 2000 domains in designate with powerdns as backend

[Graham Hayes (grahamhayes)]

This is for an old version of our API. sync is now depricated