About mukgup

mukgup · ‎10-02-2015

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. Thanks, MG

mukgup · ‎10-02-2015

Harsh - Thanks for the properties name info. This solve my problem. I was setting mapreduce.jobhistory.address and mapreduce.jobhistory.webapp.address but not the yarn.app.mapreduce.am.staging-dir. Once I set this third propery it solve the problem What I learn in this process is when we make RPC call from inside IBM Webshpere we need to set all the properties expecilty which are required. Where as when I make a call from standalone program using same JDK it took some implicit properties Thanks, MG

mukgup · ‎09-23-2015

Hi, 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. Thanks, MG

Online	Offline
Last Visited	‎02-22-2017 03:15 PM

Member Since	‎08-20-2015 08:19 PM
Last Visited	‎02-22-2017 03:15 PM
Posts	12

Cloudera Community

Re: CDH 5.3.3 jobhistory removed on RPC call

Re: CDH 5.3.3 jobhistory removed on RPC call

CDH 5.3.3 jobhistory removed on RPC call