I think you need to get them across cluster
On 5 Sep 2014 13:28, "Manjunath N" <[email protected]> wrote:

> Yes I have restarted the machine after changing the property values. I
> have set these properties on namenode.hadoop.com machine where I have
> installed oozie and also where my namenode is running. Rest of the machines
> in the cluster do not have the oozie changes.
>
> -----Original Message-----
> From: Nitin Pawar [mailto:[email protected]]
> Sent: Friday, September 05, 2014 1:07 PM
> To: [email protected]
> Subject: Re: oozie is not allowed to impersonate oozie
>
> Just checking you have set these values on all of your nodes and restarted
> the hadoop cluster
>
>
> On Fri, Sep 5, 2014 at 12:58 PM, Manjunath N <[email protected]>
> wrote:
>
> > Hi,
> >
> > Apache Hadoop version 1.2.1
> > Apache Oozie version 4.0.1
> >
> > Thanks for the quick reply. I am using Apache Hadoop 1.2.1. I have
> > installed both oozie server and oozie client on the namenode machine
> > and I am trying to run the examples shipped with oozie 4.0.1
> >
> > I modified both core-site.xml and oozie-site.xml as below and reran
> > the job still I am getting same exception.
> >
> > core-site.xml:
> >  <property>
> >          <name>hadoop.proxyuser.oozie.hosts</name>
> >          <value>namenode.hadoop.com</value>
> >  </property>
> >  <property>
> >          <name>hadoop.proxyuser.oozie.groups</name>
> >          <value>hadoop</value>
> >  </property>
> >
> >  Oozie-site.xml
> >      <property>
> >
> <name>oozie.service.ProxyUserService.proxyuser.oozie.hosts</name>
> >          <value> namenode.hadoop.com </value>
> >      </property>
> >
> >      <property>
> >
> <name>oozie.service.ProxyUserService.proxyuser.oozie.groups</name>
> >          <value> hadoop </value>
> >      </property>
> >
> > Regards,
> > Manjunath
> > -----Original Message-----
> > From: Nitin Pawar [mailto:[email protected]]
> > Sent: Friday, September 05, 2014 12:46 PM
> > To: [email protected]
> > Subject: Re: oozie is not allowed to impersonate oozie
> >
> > also instead of giving wildcard, can you try specifying actually
> > correct names in there for users group and hosts
> >
> >
> > On Fri, Sep 5, 2014 at 12:44 PM, Nitin Pawar <[email protected]>
> > wrote:
> >
> > > what version of hadoop are you using?
> > >
> > > Thanks,
> > > Nitin
> > >
> > >
> > > On Fri, Sep 5, 2014 at 12:34 PM, Manjunath N
> > > <[email protected]>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> I have 5 node Hadoop cluster. I am trying to run workflow jobs
> > >> through oozie but I am getting  this exception "oozie is not
> > >> allowed to impersonate oozie". Any help is greatly appreciated.
> > >>
> > >> I have a user "oozie" who is in Hadoop group. I am running oozie
> > >> server as oozie user. I have examples folder copied to HDFS cluster
> > >> under /user/oozie/examples. Now when I try to run the oozie job I
> > >> am getting the above error. I have also tried running as hduser who
> > >> is a Hadoop user after copying examples folder under his home
> > >> directory but I am getting same exception "oozie is not allowed to
> > >> impersonate
> > hduser"
> > >>
> > >> Here is my config:
> > >>
> > >> core-site.xml:
> > >> <property>
> > >>         <name>hadoop.proxyuser.oozie.hosts</name>
> > >>         <value>*</value>
> > >> </property>
> > >> <property>
> > >>         <name>hadoop.proxyuser.oozie.groups</name>
> > >>         <value>*</value>
> > >> </property>
> > >>
> > >> Oozie-site.xml
> > >> <property>
> > >>
> >  <name>oozie.service.ProxyUserService.proxyuser.oozie.hosts</name>
> > >>         <value>*</value>
> > >>     </property>
> > >>
> > >>     <property>
> > >>
> >  <name>oozie.service.ProxyUserService.proxyuser.oozie.groups</name>
> > >>         <value>*</value>
> > >>     </property>
> > >>
> > >> Thanks & Regards,
> > >> Manjunath
> > >>
> > >>
> > >> ________________________________
> > >> The information contained in this e-mail and any accompanying
> > >> documents may contain information that is confidential or otherwise
> > >> protected from disclosure. If you are not the intended recipient of
> > >> this message, please immediately alert the sender by reply e-mail
> > >> and
> > then delete this message.
> > >> Any dissemination, distribution or other use of the contents of
> > >> this message by anyone other than the intended recipient is
> > >> strictly
> > prohibited.
> > >> R Systems has taken every reasonable precaution to minimize the
> > >> risk, but is not liable for any damage you may sustain as a result
> > >> of any virus in this e-mail. You should carry out your own virus
> > >> checks before opening the e-mail or attachment.
> > >>
> > >
> > >
> > >
> > > --
> > > Nitin Pawar
> > >
> >
> >
> >
> > --
> > Nitin Pawar
> >
> > The information contained in this e-mail and any accompanying
> > documents may contain information that is confidential or otherwise
> > protected from disclosure. If you are not the intended recipient of
> > this message, please immediately alert the sender by reply e-mail and
> then delete this message.
> > Any dissemination, distribution or other use of the contents of this
> > message by anyone other than the intended recipient is strictly
> prohibited.
> > R Systems has taken every reasonable precaution to minimize the risk,
> > but is not liable for any damage you may sustain as a result of any
> > virus in this e-mail. You should carry out your own virus checks
> > before opening the e-mail or attachment.
> >
>
>
>
> --
> Nitin Pawar
>
> The information contained in this e-mail and any accompanying documents
> may contain information that is confidential or otherwise protected from
> disclosure. If you are not the intended recipient of this message, please
> immediately alert the sender by reply e-mail and then delete this message.
> Any dissemination, distribution or other use of the contents of this
> message by anyone other than the intended recipient is strictly prohibited.
> R Systems has taken every reasonable precaution to minimize the risk, but
> is not liable for any damage you may sustain as a result of any virus in
> this e-mail. You should carry out your own virus checks before opening the
> e-mail or attachment.
>

Reply via email to