[jira] [Updated] (OOZIE-3156) SSH action status turns OK wrongly when failed to connect to host

[TIAN XING (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

TIAN XING updated OOZIE-3156:
-
Remaining Estimate: 1h
 Original Estimate: 1h

> SSH action status turns OK wrongly when failed to connect to host
> -
>
> Key: OOZIE-3156
> URL: https://issues.apache.org/jira/browse/OOZIE-3156
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.0.0, 4.1.0, 4.2.0, 4.3.0
>Reporter: TIAN XING
> Fix For: 4.3.0
>
> Attachments: ssh-check-bug.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When {{check()}} method of {{SshActionExecutor}} gets invoked, oozie will ssh 
> connect to the host and check whether action shell pid is still there (by 
> checking the returned value of command `{{ssh $hostIp ps -p $pid}}` ) to 
> determine whether the action is running or not.
> However, there are cases where oozie fails to connect to the host during 
> action status check (e.g., the host is under heavy load, or network is bad 
> etc.).
> In such cases, the return value of the command `{{ssh $hostIp ps -p $pid}}` 
> will be 255 (ssh command exits with the exit status of the remote command or 
> with 255 if an error occurred.).
> According the current logic of method {{getActionStatus()}} in 
> {{SshActionExecutor}}, the action status will be determined as OK which may 
> not be correct. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OOZIE-3156) SSH action status turns OK wrongly when failed to connect to host

[TIAN XING (JIRA)]

TIAN XING created OOZIE-3156:


 Summary: SSH action status turns OK wrongly when failed to connect 
to host
 Key: OOZIE-3156
 URL: https://issues.apache.org/jira/browse/OOZIE-3156
 Project: Oozie
  Issue Type: Bug
  Components: action
Affects Versions: 4.3.0, 4.2.0, 4.1.0, 4.0.0
Reporter: TIAN XING
 Fix For: 4.3.0
 Attachments: ssh-check-bug.patch

When {{check()}} method of {{SshActionExecutor}} gets invoked, oozie will ssh 
connect to the host and check whether action shell pid is still there (by 
checking the returned value of command `{{ssh $hostIp ps -p $pid}}` ) to 
determine whether the action is running or not.

However, there are cases where oozie fails to connect to the host during action 
status check (e.g., the host is under heavy load, or network is bad etc.).

In such cases, the return value of the command `{{ssh $hostIp ps -p $pid}}` 
will be 255 (ssh command exits with the exit status of the remote command or 
with 255 if an error occurred.).

According the current logic of method {{getActionStatus()}} in 
{{SshActionExecutor}}, the action status will be determined as OK which may not 
be correct. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (102 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3121  bump all maven plugins to latest versions
https://issues.apache.org/jira/browse/OOZIE-3121
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues.apache.org/jira/browse/OOZIE-3105
OOZIE-3094  fix for grammar mistake
https://issues.apache.org/jira/browse/OOZIE-3094
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3085  Improve logging in ActionExecutors
https://issues.apache.org/jira/browse/OOZIE-3085
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2973  Make sure Oozie works with Hadoop 3 
https://issues.apache.org/jira/browse/OOZIE-2973
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues.apache.org/jira/browse/OOZIE-2829
OOZIE-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues.apache.org/jira/browse/OOZIE-2826
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (111 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3129  Fix test TestConfigurationService.testOozieConfig
https://issues-test.apache.org/jira/browse/OOZIE-3129
OOZIE-3127  Remove redundant check for user
https://issues-test.apache.org/jira/browse/OOZIE-3127
OOZIE-3126  Add option to allow list of users to access system config
https://issues-test.apache.org/jira/browse/OOZIE-3126
OOZIE-3121  bump all maven plugins to latest versions
https://issues-test.apache.org/jira/browse/OOZIE-3121
OOZIE-3118  fix for error: self-closing element not allowed
https://issues-test.apache.org/jira/browse/OOZIE-3118
OOZIE-3117  fix for warning: no @throws for
https://issues-test.apache.org/jira/browse/OOZIE-3117
OOZIE-3116  fix for warning: no description for @throws
https://issues-test.apache.org/jira/browse/OOZIE-3116
OOZIE-3115  fix for javadoc warning: empty  tag
https://issues-test.apache.org/jira/browse/OOZIE-3115
OOZIE-3113  Retry for ZK lock release
https://issues-test.apache.org/jira/browse/OOZIE-3113
OOZIE-3112  SparkConfigrationService overwrites properties provided via 
--properties-file option in SparkAction
https://issues-test.apache.org/jira/browse/OOZIE-3112
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues-test.apache.org/jira/browse/OOZIE-3105
OOZIE-3094  fix for grammar mistake
https://issues-test.apache.org/jira/browse/OOZIE-3094
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues-test.apache.org/jira/browse/OOZIE-3091
OOZIE-3083  Make improved version Info backward compatible
https://issues-test.apache.org/jira/browse/OOZIE-3083
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues-test.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues-test.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues-test.apache.org/jira/browse/OOZIE-3062
OOZIE-3002  address findbugs errors in client lib
https://issues-test.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues-test.apache.org/jira/browse/OOZIE-2975
OOZIE-2973  Make sure Oozie works with Hadoop 3 
https://issues-test.apache.org/jira/browse/OOZIE-2973
OOZIE-2969  Drop support for Java 1.7
https://issues-test.apache.org/jira/browse/OOZIE-2969
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues-test.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues-test.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues-test.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues-test.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues-test.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues-test.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues-test.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues-test.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues-test.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues-test.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues-test.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues-test.apache.org/jira/browse/OOZIE-2914
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues-test.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues-test.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues-test.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful

Re: Review Request 64029: OOZIE-2339 Provide an API for writing jobs based on the XSD schemas

[Robert Kanter via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/64029/#review195200
---




.gitignore
Line 10 (original), 13 (patched)


This can be in a followup JIRA if you want (in which case, please file it), 
but we should add an example or two to the oozie-examples of a workflow using 
the jobs-api.



client/src/main/java/org/apache/oozie/cli/ApiJarFactory.java
Lines 1 (patched)


Missing license header.  Also add it for any other files missing it.



client/src/main/java/org/apache/oozie/cli/ApiJarFactory.java
Lines 17 (patched)


There's no comments anywhere.  Some high level javadocs on each of the new 
classes would be helpful.  Also for any public user-facing methods.  And some 
basic comments on anything unclear or complicated.



client/src/main/java/org/apache/oozie/cli/ApiJarFactory.java
Lines 68-73 (patched)


Oozie's copyStream already has a method that does this.  If you 
don't want to pull in oozie-core, there should be some similar methods in 
Commons-IO



client/src/main/java/org/apache/oozie/cli/OozieCLI.java
Line 61 (original), 65 (patched)


No * imports



client/src/main/java/org/apache/oozie/cli/OozieCLI.java
Lines 123-125 (patched)


We should think more about the names for these commands.



client/src/main/java/org/apache/oozie/client/OozieClient.java
Line 40 (original), 42 (patched)


No *



client/src/main/java/org/apache/oozie/client/OozieClient.java
Lines 711 (patched)


This should be a constant



core/src/main/java/org/apache/oozie/servlet/BaseJobsServlet.java
Lines 118 (patched)


This should be a constant.

Also, what happens if this is not set?  You'll end up with a path 
/application_ which I don't think we want to do.

Also, I don't think we should do application_.  That 
might get confusion with Yarn APP IDs, which look like 
application__.  Perhaps gen_app_ instead of 
application?



core/src/main/java/org/apache/oozie/servlet/BaseJobsServlet.java
Lines 120 (patched)


I don't think "default" is the right word here.  Maybe "... setting to 
generated path"



core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java
Lines 21-24 (original), 21-24 (patched)


No *



core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java
Line 49 (original), 53 (patched)


No *



core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java
Lines 117 (patched)


IIRC, APP_PATH, COORDINATOR_APP_PATH, and BUNDLE_APP_PATH can all actually 
take an arbitrarily named XML file.  For example, you can set it to 
hdfs://host:8020/user/rkanter/my-wf/foo.xml instead of 
hdfs://host:8020/user/rkanter/my-wf/ and Oozie will use foo.xml instead 
of workflow.xml.  Someone may even just do 
hdfs://host:8020/user/rkanter/my-wf/workflow.xml.  We need to be 
careful to check for that any not always append 
/workflow|coordinator|bundle.xml.



core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java
Lines 152 (patched)


This should be a more "oozie-sounding" property name.  i.e. 
"oozie.something.something.etc" and not simply "GENERATED_XML"



core/src/main/resources/oozie-default.xml
Lines 3312-3322 (patched)


Or would we be better off putting these under a special directory under 
each user's home dir?  For example 
/user/rkanter/oozie-generated-workflows

With the current way, we're going to store all users' generated workflows 
under the oozie user's home dir, which means that all users need access to this 
directory.  I think that's probably okay, but it's a little funny.  If we put 
these under each user's home dir, there's no problem.



core/src/main/resources/oozie-default.xml
Lines 3313 (patched)


Starting this with oozie.client makes it looks like a config 
property for the Oozie Client, which it's not.  Maybe 
oozie.jobs-api.application.generated.path or something like that?



core/src/test/java/org/apache/oozie/client/TestOozieCLI.java
Line 

Re: [VOTE] Release Oozie 5.0.0-beta1 (candidate 1)

[Robert Kanter]

Here's what I did:
- Verified md5
- Verified signature (gpg)
- Built Oozie against Hadoop 2.7.2
- Ran a few of the examples, clicked around the UI, tried various CLI
commands, looked at the REST output
- Verified that OOZIE-3083 is fixed
- I also saw the issue Kinga found in OOZIE-3155, and I agree that's not a
blocker for the beta, but I've made it "critical" for GA as that would be
good to fix

+1 (binding)

thanks
- Robert


On Wed, Jan 10, 2018 at 9:06 AM, Julia Kinga Marton 
wrote:

> Hi,
>
> I made some testing on the RC, and it seems OK.
>
> What I checked:
> - md5
> - gpg signature
> - rat report
> - built Oozie against Hadoop-2.6.0
> - ran a few examples (wf and coordinator), clicked the Web UI, ran some CLI
> commands
>
> I found a small issue related the Job DAG (OOZIE-3155
> ), but I don`t consider
> it a blocker.
>
> +1 from my side (non-binding)
>
> Best regards,
> Kinga
>
> On Tue, Jan 9, 2018 at 5:53 PM, Attila Sasvári 
> wrote:
>
> > It is release candidate 1.
> >
> > On Tue, Jan 9, 2018 at 5:50 PM, Attila Sasvári 
> > wrote:
> >
> > > Hi,
> > >
> > > I have created a build for Oozie 5.0.0-beta1, release candidate 0.
> > >
> > > This release introduces major changes:
> > > - moving launcher from MapReduce AM to Oozie AM,
> > > - dropped support for Hadoop 1.x,
> > > - added new 1.0 workflow schemas,
> > > - switching from Tomcat to embedded Jetty,
> > > - completely rewritten graph generator,
> > > - local sharelib,
> > > - JDK 8 support.
> > >
> > > It also includes OOZIE-3083.
> > >
> > > 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/~asasvari/oozie-5.0.0-beta1-rc1/
> > >
> > > The release, md5 signature, gpg signature, and rat report can all be
> > found
> > > at the above address.
> > >
> > > The vote is open until Friday, January 12, 2018 at 18:00 CEST.
> > >
> > > Thanks,
> > > Attila Sasvari
> > >
> >
>

[jira] [Updated] (OOZIE-3155) Job DAG is not refreshed when a job is finished

[Robert Kanter (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-3155:
-
Priority: Critical  (was: Minor)

> Job DAG is not refreshed when a job is finished
> ---
>
> Key: OOZIE-3155
> URL: https://issues.apache.org/jira/browse/OOZIE-3155
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: trunk, 5.0.0b1
>Reporter: Julia Kinga Marton
>Priority: Critical
> Fix For: 5.0.0
>
> Attachments: Screen Shot 2018-01-10 at 16.23.28.png
>
>
> When opening a Job DAG when the job is still in progress, the DAG is OK, but 
> when the job will finish, this diagram is not refreshed.
> Steps to reproduce: 
> - submit a workflow (e.g. the subwf from the examples) - the wf should not 
> end very quickly, to have time to catch it when it is still running
> - check the Job DAG when the job is still running
> - wait for the job to finish
> - check again the Job DAG -> is the same with the running one
> Note: if check it in a new tab, is OK, and also a browser refresh will solve 
> it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-3155) Job DAG is not refreshed when a job is finished

[Robert Kanter (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-3155:
-
Affects Version/s: 5.0.0b1
Fix Version/s: 5.0.0

> Job DAG is not refreshed when a job is finished
> ---
>
> Key: OOZIE-3155
> URL: https://issues.apache.org/jira/browse/OOZIE-3155
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: trunk, 5.0.0b1
>Reporter: Julia Kinga Marton
>Priority: Critical
> Fix For: 5.0.0
>
> Attachments: Screen Shot 2018-01-10 at 16.23.28.png
>
>
> When opening a Job DAG when the job is still in progress, the DAG is OK, but 
> when the job will finish, this diagram is not refreshed.
> Steps to reproduce: 
> - submit a workflow (e.g. the subwf from the examples) - the wf should not 
> end very quickly, to have time to catch it when it is still running
> - check the Job DAG when the job is still running
> - wait for the job to finish
> - check again the Job DAG -> is the same with the running one
> Note: if check it in a new tab, is OK, and also a browser refresh will solve 
> it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Attila Sasvari]

Many thanks Satish!

- Verified that hashes are OK
- release log, rat report look good
- start / stop Oozie / install sharelib works
- Using a pseudo hadoop 2.6.0, all the example workflows, coordinators,
bundles succeeded I submitted succeeded.  I have not tested hcatalog, hive
and hive 2 example workflows.
- Web UI displays graph, correct version, submitted workflows,
coordinators, bundles and theirs details (except logs)

I ran into one issue:
- Retrieving Workflow Job logs did not work for me (via Oozie CLI / Web UI
/ curl); it should be fixed. Some hints:
  . curl "http://localhost:11000/oozie/v2/job/040-
180110111647214-oozie-asas-W?show=log" gave 200 OK with no response.
However, related log entries were present in logs/oozie.log.
  . I debugged log streaming a bit: logPath in XLogStreamer was set to
${oozie.log.dir}. After I changed it to the proper log directory via my
debugger, I was able to fetch workflow job logs. XLogService initialises
this with logUtil.getLogPath() in extractInfoForLogWebService(). I tried to
to pass oozie.log.dir as a system property in CATALINA_OPTS but it did not
work.

Best regards,
Attila

ps: I have not tested Oozie in HA mode, Oozie in secured environment, SLA
notifications via JMS, manual purge, each and every admin command,
authorization, etc. Oozie tests should cover all main areas.

On Mon, Jan 8, 2018 at 7:33 AM, Satish Saley  wrote:

> Hi,
>
> I have created a build for Oozie 4.3.1, candidate 0.
>
> It includes all the changes decided earlier except OOZIE-3018 and
> OOZIE-3072. OOZIE-3018 makes changes to SchemaCheckerService which we are
> not picking. OOZIE-3072 makes changes to files created in OOZIE-1770.
>
> 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/~satishsaley/oozie-4.3.1-rc0
>
> The release, md5 signature, gpg signature, and rat report can all
> be found at the above address.
>
> Vote closes on 01/15/2018 11:59 PM PT.
>
> Satish Saley

Re: [VOTE] Release Oozie 5.0.0-beta1 (candidate 1)

[Julia Kinga Marton]

Hi,

I made some testing on the RC, and it seems OK.

What I checked:
- md5
- gpg signature
- rat report
- built Oozie against Hadoop-2.6.0
- ran a few examples (wf and coordinator), clicked the Web UI, ran some CLI
commands

I found a small issue related the Job DAG (OOZIE-3155
), but I don`t consider
it a blocker.

+1 from my side (non-binding)

Best regards,
Kinga

On Tue, Jan 9, 2018 at 5:53 PM, Attila Sasvári  wrote:

> It is release candidate 1.
>
> On Tue, Jan 9, 2018 at 5:50 PM, Attila Sasvári 
> wrote:
>
> > Hi,
> >
> > I have created a build for Oozie 5.0.0-beta1, release candidate 0.
> >
> > This release introduces major changes:
> > - moving launcher from MapReduce AM to Oozie AM,
> > - dropped support for Hadoop 1.x,
> > - added new 1.0 workflow schemas,
> > - switching from Tomcat to embedded Jetty,
> > - completely rewritten graph generator,
> > - local sharelib,
> > - JDK 8 support.
> >
> > It also includes OOZIE-3083.
> >
> > 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/~asasvari/oozie-5.0.0-beta1-rc1/
> >
> > The release, md5 signature, gpg signature, and rat report can all be
> found
> > at the above address.
> >
> > The vote is open until Friday, January 12, 2018 at 18:00 CEST.
> >
> > Thanks,
> > Attila Sasvari
> >
>

[jira] [Created] (OOZIE-3155) Job DAG is not refreshed when a job is finished

[Julia Kinga Marton (JIRA)]

Julia Kinga Marton created OOZIE-3155:
-

 Summary: Job DAG is not refreshed when a job is finished
 Key: OOZIE-3155
 URL: https://issues.apache.org/jira/browse/OOZIE-3155
 Project: Oozie
  Issue Type: Bug
  Components: client
Affects Versions: trunk
Reporter: Julia Kinga Marton
Priority: Minor
 Attachments: Screen Shot 2018-01-10 at 16.23.28.png

When opening a Job DAG when the job is still in progress, the DAG is OK, but 
when the job will finish, this diagram is not refreshed.

Steps to reproduce: 
- submit a workflow (e.g. the subwf from the examples) - the wf should not end 
very quickly, to have time to catch it when it is still running
- check the Job DAG when the job is still running
- wait for the job to finish
- check again the Job DAG -> is the same with the running one

Note: if check it in a new tab, is OK, and also a browser refresh will solve it.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Peter Cseh]

Thanks Satish for creating the rc!

1) md5, gpg, rat report checks out, distro builds.
2) submitted some examples onto a pseudodistributed Hadoop cluster, they
looked fine.

+1 (non-binding)


On Mon, Jan 8, 2018 at 7:33 AM, Satish Saley  wrote:

> Hi,
>
> I have created a build for Oozie 4.3.1, candidate 0.
>
> It includes all the changes decided earlier except OOZIE-3018 and
> OOZIE-3072. OOZIE-3018 makes changes to SchemaCheckerService which we are
> not picking. OOZIE-3072 makes changes to files created in OOZIE-1770.
>
> 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/~satishsaley/oozie-4.3.1-rc0
>
> The release, md5 signature, gpg signature, and rat report can all
> be found at the above address.
>
> Vote closes on 01/15/2018 11:59 PM PT.
>
> Satish Saley
>



-- 
Peter Cseh
Software Engineer