Change NN and JobTracker dynamically during runtime

2016-12-01 Thread mdk-swandha
Hi, I have a use case like this - in a multi cluster (hadoop cluster) environment if I would like to send a job/oozie workflow to a desired cluster during runtime, how can this be done. I see that there is JavaActionExecutor class which read NN and JobTracker in createBaseHadoopConf method All H

Re: Change NN and JobTracker dynamically during runtime

2016-12-05 Thread mdk-swandha
he load balancer can choose the JT or NN node runtime, > e.g. on a round robin basis. > > Regards, > > Andras > > -- > Andras PIROS > Software Engineer > <http://www.cloudera.com/> > > On Thu, Dec 1, 2016 at 9:29 PM, mdk-swandha > wrote: > > > Hi, &

Re: Change NN and JobTracker dynamically during runtime

2016-12-05 Thread mdk-swandha
here runtime routing to different JT / NN > instances via Oozie (and not e.g. coming from a load balancer setting > configured runtime) is better? > > Thanks, > > Andras > > -- > Andras PIROS > Software Engineer > <http://www.cloudera.com/> > > On Mon, De

Re: Change NN and JobTracker dynamically during runtime

2016-12-07 Thread mdk-swandha
to write this in my service. Please inform me if you anything is not clear in my use case. Thanks. On Mon, Dec 5, 2016 at 11:57 AM, mdk-swandha wrote: > You mean I have to set env variables for each job/workflow execution and > then it will be picked up by Oozie. And I should set them

Job Submission to Cross Cluster Fails

2017-03-06 Thread mdk-swandha
Hi, I have the following configuration: Cluster 1: Job Submission through Hue (hue1) to Cluster 1 (NN1 and RM1) via Oozie works. Cluster 2: Job Submission through Hue (hue2) to Cluster 2 (NN2 and RM2) via Oozie works. As Oozie is cluster agnostic - now I have tweaked my Hue code to submit job t

Re: Job Submission to Cross Cluster Fails

2017-03-10 Thread mdk-swandha
gned to work against multiple clusters, but I don't know if it > can be done via Hue. > > gp > > On Mon, Mar 6, 2017 at 8:49 PM, mdk-swandha > wrote: > > > Hi, > > > > I have the following configuration: > > > > Cluster 1: > > Job Submission