[MAPREDUCE-3687] If AM dies before it returns new tracking URL, proxy redirects to http://N/A/ and doesn't return error code

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.1
• Fix Version/s: 0.23.2
• Component/s: mrv2
• Assignee: Ravi Prakash
• Reporter: David Capwell
• Created: 18/Jan/12 18:03
• Updated: 01/Mar/12 13:58
• Resolved: 29/Feb/12 15:23

Description

I tried to turn on Uber AM and put 9223372036854775807l (last char is an L) for maxbytes. This caused a
NumberFormatException in the AM and killed it.

When I try to go to the RM proxy, it redirects me to http://N/A/

curl -i http://resource.manager.example.com:$port/proxy/application_1326504761991_0001/
HTTP/1.1 302 Found
Content-Type: text/plain; charset=utf-8
Location: http://N/A/
Content-Length: 0
Server: Jetty(6.1.26)

Since the AM has no tracker URL, I would expect the return code to be 400~ or 500~ and return an error.