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
