Attila, AFAIK, these properties are in my core-site.xml except for last
one, mapreduce.framework.name is in mapred-site.xml. I'll have to double
check on the proxyuser.root.hosts as I believe my service runs with user
oozie not root and get back to you.

On Tue, Feb 6, 2018 at 3:49 PM, Attila Sasvari <asasv...@cloudera.com>
wrote:

> +1 (binding)
>
> - Verified MD5 hash, signature, rat_report, release log are OK
> - Built Oozie against Hadoop 2.7.5 (did not build against other Hadoop
> versions this time)
> - Installed Oozie sharelib
> - Some example workflows I submitted to a 1-node Hadoop 2.7.5 (running in
> pseudo distributed mode for tests) succeeded: ( aggregator bundle
> coord-input-logic cron cron-schedule custom-main datelist-java-main demo
> distcp hadoop-el hcatalog java-main map-reduce no-op pig shell sla sqoop
> sqoop-freeform ssh streaming subwf )
> - Verified basic functionality of the Web UI (version, Job DAG, Job logs)
>
>
> Artem, have you specified conf/hadoop-conf/core-site.xml with all the
> details Oozie needs to communicate with a Hadoop cluster?
>
> In my local environment, I use a pseudo Hadoop 2.7.5. My
> conf/hadoop-conf/core-site.xml is as follows:
> <?xml version="1.0" encoding="UTF-8"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!--
> Licensed under the Apache License, Version 2.0 (the "License");
> you may not use this file except in compliance with the License.
> You may obtain a copy of the License at
> http://www.apache.org/licenses/LICENSE-2.0
> Unless required by applicable law or agreed to in writing, software
> See the License for the specific language governing permissions and
> limitations under the License. See accompanying LICENSE file.
> -->
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
>   <property>
>     <name>fs.defaultFS</name>
>     <value>hdfs://localhost:9000</value>
>   </property>
>   <property>
>     <name>hadoop.proxyuser.root.hosts</name>
>     <value>*</value>
>   </property>
>   <property>
>     <name>hadoop.proxyuser.root.groups</name>
>     <value>*</value>
>   </property>
>     <property>
>         <name>mapreduce.framework.name</name>
>         <value>yarn</value>
>     </property>
> </configuration>
>
>
> On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits <artemerv...@gmail.com>
> wrote:
>
> > jdk: 1.8.0_161
> > hadoop: 2.7.5
> > md5: OK
> > curl http://localhost:11000/oozie/v1/admin/status
> > {"systemMode":"NORMAL"}
> >
> > curl http://localhost:11000/oozie/v2/admin/status
> > {"systemMode":"NORMAL"}
> >
> >
> > I also got in oozie-ops.log
> >
> >   STARTUP MSG: Oozie BUILD_VERSION [4.3.1] compiled by [oozie] on
> > [2018.02.06-16:30:43GMT]
> >   STARTUP MSG:       revision [unavailable]@[unavailable]
> >
> > so perhaps we may want to add but not critical OOZIE-2004, OOZIE-3083,
> > OOZIE-3152.
> >
> >  submitted a job and got but that is most likely my environment.
> Otherwise
> > +1
> >
> > 2018-02-06 18:09:37,635  WARN ActionStartXCommand:523 - SERVER[
> > hadoop.example.com] USER[vagrant] GROUP[-] TOKEN[] APP[python-wf]
> > JOB[0000000-180206180622504-oozie-oozi-W]
> > ACTION[0000000-180206180622504-oozie-oozi-W@python-node] Error starting
> > action [python-node]. ErrorType [ERROR], ErrorCode
> > [UnsupportedOperationException], Message [UnsupportedOperationException:
> > Accessing local file system is not allowed]
> > org.apache.oozie.action.ActionExecutorException:
> > UnsupportedOperationException: Accessing local file system is not allowed
> > at
> > org.apache.oozie.action.ActionExecutor.convertException(Acti
> > onExecutor.java:446)
> > at
> > org.apache.oozie.action.hadoop.JavaActionExecutor.submitLaun
> > cher(JavaActionExecutor.java:1204)
> > at
> > org.apache.oozie.action.hadoop.JavaActionExecutor.start(Java
> > ActionExecutor.java:1386)
> > at
> > org.apache.oozie.command.wf.ActionStartXCommand.execute(Acti
> > onStartXCommand.java:234)
> > at
> > org.apache.oozie.command.wf.ActionStartXCommand.execute(Acti
> > onStartXCommand.java:65)
> > at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> > at
> > org.apache.oozie.service.CallableQueueService$CompositeCalla
> > ble.call(CallableQueueService.java:332)
> > at
> > org.apache.oozie.service.CallableQueueService$CompositeCalla
> > ble.call(CallableQueueService.java:261)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > at
> > org.apache.oozie.service.CallableQueueService$CallableWrappe
> > r.run(CallableQueueService.java:179)
> > at
> > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> > Executor.java:1149)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> > lExecutor.java:624)
> > at java.lang.Thread.run(Thread.java:748)
> > Caused by: java.lang.UnsupportedOperationException: Accessing local file
> > system is not allowed
> > at
> > org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalF
> > ileSystem.java:48)
> > at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSys
> > tem.java:47)
> > at org.apache.hadoop.fs.FileSystem.createFileSystem(
> FileSystem.java:2667)
> > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:93)
> > at org.apache.hadoop.fs.FileSystem$Cache.getInternal(
> FileSystem.java:2701)
> > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2683)
> > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:372)
> > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:171)
> > at
> > org.apache.oozie.service.ShareLibService.updateShareLib(Shar
> > eLibService.java:554)
> > at
> > org.apache.oozie.service.ShareLibService.getShareLibJars(Sha
> > reLibService.java:366)
> > at
> > org.apache.oozie.service.ShareLibService.getSystemLibJars(Sh
> > areLibService.java:432)
> > at
> > org.apache.oozie.action.hadoop.JavaActionExecutor.addSystemS
> > hareLibForAction(JavaActionExecutor.java:756)
> > at
> > org.apache.oozie.action.hadoop.JavaActionExecutor.addAllShar
> > eLibs(JavaActionExecutor.java:853)
> > at
> > org.apache.oozie.action.hadoop.JavaActionExecutor.setLibFile
> > sArchives(JavaActionExecutor.java:844)
> > at
> > org.apache.oozie.action.hadoop.JavaActionExecutor.submitLaun
> > cher(JavaActionExecutor.java:1095)
> > ... 11 more
> > 2018-02-06 18:09:37,661  WARN ActionStartXCommand:523 - SERVER[
> > hadoop.example.com] USER[vagrant] GROUP[-] TOKEN[] APP[python-wf]
> > JOB[0000000-180206180622504-oozie-oozi-W]
> > ACTION[0000000-180206180622504-oozie-oozi-W@python-node] Setting Action
> > Status to [DONE]
> >
> >
> >
> > On Tue, Feb 6, 2018 at 7:42 AM, Gézapeti Cseh <gezap...@apache.org>
> wrote:
> >
> > > Hi,
> > >
> > > I have created a build for Oozie 4.3.1, candidate 4.
> > >
> > > It includes all the changes in rc3 plus OOZIE-2888 to fix sharelib
> > > creation with Hadoop 2.7.5. and possibly other newer versions.
> > >
> > > Keys to verify the signature of the release artifact are available at
> > >   http://www.apache.org/dist/oozie/KEYS
> > >
> > > Please download, test, and try it out:
> > >
> > > http://people.apache.org/~gezapeti/oozie-4.3.1-rc4/
> > >
> > > The release, md5 signature, gpg signature, and rat report can be found
> at
> > > the above address.
> > >
> > > Vote closes on 02/12/2018 11:59 PM CET.
> > >
> >
>
>
>
> --
> --
> Attila Sasvari
> Software Engineer
> <http://www.cloudera.com/>
>

Reply via email to