I need help to understand a issue I am getting with jobHistory of my mapreduce job. I am submitting the Java MR2 code remotely using RPC from my web application which is running inside the WebSphere. Application submission work perfectly fine, give back job_id. Application works fine on backend but after job complete jobhistory url stop working. We cant see the job history. Real problem is we are not able to read the job status from RPC as JobClient comes pack with job not found error.
When we try to submit the job from java application outside the WebSphere it works as expected and keep jobhistory.
I am thinking there must be some property or setting needed for keep the jobHistory saved in cluster so that we can read the job status.
Any help in this regard is appreciated.
Once again thanks.
Regarding using full xml resource load. I understand that is always good. But in our environment its not permitted hence endup adding one by one.
I am trying to convince ops team to adopt conf folder approach.