Determine cause of first-hit 504 on help endpoint
suever opened this issue · comments
Whenever the documentation for a version is fetched for the first time, the backend has to do some conversions to convert the documentation into a JSON output which is causing a 504 Gateway Timeout for some reason. I need to figure out at what layer this timeout is coming from and address it by either optimizing how we compute that JSON or increasing the appropriate timeout
This appears to have been caused by an issue in ambassador so for now we're going to just set the timeout_ms to a large value.