On 9 September 2017 at 05:17, Ravi Prakash <ravihad...@gmail.com> wrote:
> I'm not sure my reply will be entirely helpful, but here goes. It sheds more light on things than I previously understood, Ravi, so cheers > The ResourceManager either proxies your request to the ApplicationMaster (if > the application is running), or (once the application is finished) serves it > itself if the job is in the "cache" (usually the last 10000 applications) or > redirects to the MapReduce JHS if its a MapReduce job. That suggests that I don't have the ApplicationMaster(s) setup correctly (or possibly at all!) or that the caching setup is wrong because the ResourceManager and JobHistoryServer clearly both has the Job Info once the Jobs have ended, as I listed before > > http://rmserver.ecs.vuw.ac.nz:8088/cluster/app/application_1234567890123_4567/ > > Similarly, over on the Job History Server, we can get to a page, > related to the job > > http://jhserver.ecs.vuw.ac.nz:19888/jobhistory/job/job_1234567890123_4567/ however, trying to access those, though the "proxy channel" http://rmserver.ecs.vuw.ac.nz:8088/proxy/ URI doesn't take anyone anywhere. Thanks again for the insight: I think know where I need to look now, Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@hadoop.apache.org For additional commands, e-mail: user-h...@hadoop.apache.org
