[AMBARI-5047] API proxy returns "204 No Content" if the underlying call takes more than a few seconds

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.5.1
• Fix Version/s: 1.5.1
• Component/s: ambari-agent
• Assignee: Vitaly Brodetskyi
• Reporter: Vitaly Brodetskyi
• Created: 12/Mar/14 12:19
• Updated: 12/Mar/14 14:28
• Resolved: 12/Mar/14 14:28

Description

It looks like the API proxy behaves in an expected manner (returns HTTP code 204 with no response) when the underlying API call being proxied does not return in a timely manner.
It seems like this threshold is around 3 seconds.
When I was testing Falcon, I kept getting 204 from Ambari's API proxy, but the underlying API calls were successful when directly run against Falcon.
3 seconds is a bit aggressive. Perhaps we can pass a parameter to change the timeout value in milliseconds, with a hard limit on 15 seconds or so?
Also, returning 204 is not ideal. We should return

{error: "400", message: "Connection timed out"}

or something like that (I didn't check the actual format that we use... just an example), so that the API client can perform appropriate error handling.

Issue Links

• links to: RequestBoard