If AM dies before it returns new tracking URL, proxy redirects to http://N/A/
and doesn't return error code
-----------------------------------------------------------------------------------------------------------
Key: MAPREDUCE-3687
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3687
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2
Affects Versions: 0.23.1
Reporter: David Capwell
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
