Skip to content
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

TO API POST /cdns/dnsseckeys/generate times out with large numbers of delivery services #5732

Closed
rawlinp opened this issue Apr 9, 2021 · 0 comments · Fixed by #5810
Closed
Labels
bug something isn't working as intended Traffic Ops related to Traffic Ops Traffic Vault related to Traffic Vault

Comments

@rawlinp
Copy link
Contributor

rawlinp commented Apr 9, 2021

I'm submitting a ...

  • bug report

Traffic Control components affected ...

  • Traffic Ops
  • Traffic Vault

Current behavior:

With a large number of delivery services (e.g. 266), the POST /cdns/dnsseckeys/generate route times out and returns a 503 because the operation exceeds 1 minute.

Expected behavior:

The operation should succeed in less than 1 minute instead of timing out.

Minimal reproduction of the problem with instructions:

In a CDN with a large number of delivery services (e.g. 266), call this API, and observe that it times out after 1 minute and returns a 503.

Anything else:

This was observed on a VM w/ 8 CPUs at 2596.986 MHz, so the results might be different on baremetal or more powerful VMs. However, we should be able to run TO on low-performance VMs. I would propose that we parallelize this CPU-intensive operation so that we can take advantage of multicore servers.

@rawlinp rawlinp added bug something isn't working as intended Traffic Ops related to Traffic Ops Traffic Vault related to Traffic Vault labels Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended Traffic Ops related to Traffic Ops Traffic Vault related to Traffic Vault
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant