Re: [VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-09 Thread Peter Cseh 
Thanks everyone for the testing and votes!
Based on our wiki page, the usual timeframe for the vote is 72 hours.
I've announced this vote longer so it includes a weekend as many of the
votes for earlier RCs came in on weekends.
I don't have the time to finish the release today and the vote ends on
Monday anyways, so I think I'll wait until the deadline before announcing
the result.

I'll make the vote period shorter next time.
Thanks,
gp

On Thu, Feb 8, 2018 at 5:49 AM, Rohini Palaniswamy 
wrote:

> +1 (binding)
>
> - Verified md5, signature, release log and rat report
> - Ran all the unit tests and they are good.
> - Created distro with bin/mkdistro.sh -DskipTests -Puber -Phadoop-2
> - Checked the UI and executed a simple workflow
> - Verified that the tomcat is now 6.0.53
>
> Looks like the vote ends on Feb 12 which is 7 days and is very long. Isn't
> it usually 72 hours excluding weekends and holidays?
>
> Regards,
> Rohini
>
> On Wed, Feb 7, 2018 at 1:35 PM, Robert Kanter 
> wrote:
>
> > Here's what I did:
> > - Verified md5
> > - Verified signature (gpg)
> > - Looked at rat report
> > - Looked at release log
> > - Verified Tomcat is version 6.0.53
> > - Built Oozie against Hadoop 2.7.2, using an empty local maven repo
> > - Ran a few of the examples, clicked around the UI, tried various CLI
> > commands, looked at the REST output, launcher log output, etc
> >
> >
> > +1
> >
> > On Tue, Feb 6, 2018 at 7:24 PM, Artem Ervits 
> > wrote:
> >
> > > 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 
> > > 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:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >   
> > > > fs.defaultFS
> > > > hdfs://localhost:9000
> > > >   
> > > >   
> > > > hadoop.proxyuser.root.hosts
> > > > *
> > > >   
> > > >   
> > > > hadoop.proxyuser.root.groups
> > > > *
> > > >   
> > > > 
> > > > mapreduce.framework.name
> > > > yarn
> > > > 
> > > > 
> > > >
> > > >
> > > > On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits 
> > > > 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[000-180206180622504-oozie-oozi-W]
> > > > > ACTION[000-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

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-07 Thread Rohini Palaniswamy 
+1 (binding)

- Verified md5, signature, release log and rat report
- Ran all the unit tests and they are good.
- Created distro with bin/mkdistro.sh -DskipTests -Puber -Phadoop-2
- Checked the UI and executed a simple workflow
- Verified that the tomcat is now 6.0.53

Looks like the vote ends on Feb 12 which is 7 days and is very long. Isn't
it usually 72 hours excluding weekends and holidays?

Regards,
Rohini

On Wed, Feb 7, 2018 at 1:35 PM, Robert Kanter  wrote:

> Here's what I did:
> - Verified md5
> - Verified signature (gpg)
> - Looked at rat report
> - Looked at release log
> - Verified Tomcat is version 6.0.53
> - Built Oozie against Hadoop 2.7.2, using an empty local maven repo
> - Ran a few of the examples, clicked around the UI, tried various CLI
> commands, looked at the REST output, launcher log output, etc
>
>
> +1
>
> On Tue, Feb 6, 2018 at 7:24 PM, Artem Ervits 
> wrote:
>
> > 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 
> > 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:
> > > 
> > > 
> > > 
> > > 
> > > 
> > >   
> > > fs.defaultFS
> > > hdfs://localhost:9000
> > >   
> > >   
> > > hadoop.proxyuser.root.hosts
> > > *
> > >   
> > >   
> > > hadoop.proxyuser.root.groups
> > > *
> > >   
> > > 
> > > mapreduce.framework.name
> > > yarn
> > > 
> > > 
> > >
> > >
> > > On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits 
> > > 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[000-180206180622504-oozie-oozi-W]
> > > > ACTION[000-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

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-07 Thread Robert Kanter 
Here's what I did:
- Verified md5
- Verified signature (gpg)
- Looked at rat report
- Looked at release log
- Verified Tomcat is version 6.0.53
- Built Oozie against Hadoop 2.7.2, using an empty local maven repo
- Ran a few of the examples, clicked around the UI, tried various CLI
commands, looked at the REST output, launcher log output, etc


+1

On Tue, Feb 6, 2018 at 7:24 PM, Artem Ervits  wrote:

> 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 
> 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:
> > 
> > 
> > 
> > 
> > 
> >   
> > fs.defaultFS
> > hdfs://localhost:9000
> >   
> >   
> > hadoop.proxyuser.root.hosts
> > *
> >   
> >   
> > hadoop.proxyuser.root.groups
> > *
> >   
> > 
> > mapreduce.framework.name
> > yarn
> > 
> > 
> >
> >
> > On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits 
> > 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[000-180206180622504-oozie-oozi-W]
> > > ACTION[000-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

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-06 Thread Artem Ervits 
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 
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:
> 
> 
> 
> 
> 
>   
> fs.defaultFS
> hdfs://localhost:9000
>   
>   
> hadoop.proxyuser.root.hosts
> *
>   
>   
> hadoop.proxyuser.root.groups
> *
>   
> 
> mapreduce.framework.name
> yarn
> 
> 
>
>
> On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits 
> 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[000-180206180622504-oozie-oozi-W]
> > ACTION[000-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
> >

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-06 Thread Attila Sasvari 
+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:





  
fs.defaultFS
hdfs://localhost:9000
  
  
hadoop.proxyuser.root.hosts
*
  
  
hadoop.proxyuser.root.groups
*
  

mapreduce.framework.name
yarn




On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits  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[000-180206180622504-oozie-oozi-W]
> ACTION[000-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[000-180206180622504-oozie-oozi-W]
>

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-06 Thread Artem Ervits 
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[000-180206180622504-oozie-oozi-W]
ACTION[000-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(ActionExecutor.java:446)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1204)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1386)
at
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
at
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
at org.apache.oozie.command.XCommand.call(XCommand.java:287)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:332)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:261)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:179)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.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(RawLocalFileSystem.java:48)
at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.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(ShareLibService.java:554)
at
org.apache.oozie.service.ShareLibService.getShareLibJars(ShareLibService.java:366)
at
org.apache.oozie.service.ShareLibService.getSystemLibJars(ShareLibService.java:432)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.addSystemShareLibForAction(JavaActionExecutor.java:756)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.addAllShareLibs(JavaActionExecutor.java:853)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.setLibFilesArchives(JavaActionExecutor.java:844)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(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[000-180206180622504-oozie-oozi-W]
ACTION[000-180206180622504-oozie-oozi-W@python-node] Setting Action
Status to [DONE]



On Tue, Feb 6, 2018 at 7:42 AM, Gézapeti Cseh  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.
>

[VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-06 Thread Gézapeti Cseh 
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.