[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (0 issues) Subscriber: ooziedaily You may edit this subscription at: https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=16327filterId=12325939
[jira] [Created] (OOZIE-2030) Configuration properties from global section is not getting set in Hadoop job conf when using sub-workflow action in Oozie workflow.xml
Peeyush Bishnoi created OOZIE-2030: -- Summary: Configuration properties from global section is not getting set in Hadoop job conf when using sub-workflow action in Oozie workflow.xml Key: OOZIE-2030 URL: https://issues.apache.org/jira/browse/OOZIE-2030 Project: Oozie Issue Type: Bug Components: action Reporter: Peeyush Bishnoi Fix For: 4.0.1, 4.0.0 When submitting Oozie workflow with sub-workflow action and with global section, configuration properties defined in global section is not getting set in launched Hadoop job conf. But when we use Pig or MR action in workflow.xml, configuration properties from global section set properly into Hadoop job conf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2019) SLA miss processed on server2 not send email
[
https://issues.apache.org/jira/browse/OOZIE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohini Palaniswamy updated OOZIE-2019:
--
Fix Version/s: 4.1.0
+1 Pending jenkins
SLA miss processed on server2 not send email
Key: OOZIE-2019
URL: https://issues.apache.org/jira/browse/OOZIE-2019
Project: Oozie
Issue Type: Bug
Reporter: Purshotam Shah
Assignee: Purshotam Shah
Fix For: 4.1.0
Attachments: OOZIE-2019-V1.patch
It's because of below function. When we try to load config string from DB and
recreate event action map, it doesn't create event map properly.
StringTokenizer(slaConfig, },); has issue. It tries to tokenized on ,
and },.
a.slaConfig={alert_contact=hadoo...@oozie.com},{alert_events=START_MET,DURATION_MISS,END_MET},;
Will become
alert_events=START_MET
alert_contact=hadoo...@oozie.com.
Fix is used to use String.split().
{code}
private void slaConfigStringToMap() {
if (slaConfig != null) {
StringTokenizer st = new StringTokenizer(slaConfig, },);
while (st.hasMoreTokens()) {
String token = st.nextToken();
String[] pair = token.split(=);
if (pair.length == 2) {
slaConfigMap.put(pair[0].substring(1), pair[1]);
}
}
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-1385) Make Uber Mode the default
[ https://issues.apache.org/jira/browse/OOZIE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-1385: - Attachment: OOZIE-1385.patch Here's a patch. I've verified that the launcher does actually run in uber mode. Make Uber Mode the default -- Key: OOZIE-1385 URL: https://issues.apache.org/jira/browse/OOZIE-1385 Project: Oozie Issue Type: Bug Affects Versions: trunk Reporter: Robert Kanter Assignee: Robert Kanter Fix For: trunk Attachments: OOZIE-1385.patch Once we sort out the Uber mode for the launcher job issues, we should make it the default to take advantage of the speed-up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2019) SLA miss processed on server2 not send email
[
https://issues.apache.org/jira/browse/OOZIE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14167350#comment-14167350
]
Hadoop QA commented on OOZIE-2019:
--
Testing JIRA OOZIE-2019
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1537
.Tests failed: 1
.Tests errors: 0
.The patch failed the following testcases:
. testCoordinatorActionEvent(org.apache.oozie.event.TestEventGeneration)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2030/
SLA miss processed on server2 not send email
Key: OOZIE-2019
URL: https://issues.apache.org/jira/browse/OOZIE-2019
Project: Oozie
Issue Type: Bug
Reporter: Purshotam Shah
Assignee: Purshotam Shah
Fix For: 4.1.0
Attachments: OOZIE-2019-V1.patch
It's because of below function. When we try to load config string from DB and
recreate event action map, it doesn't create event map properly.
StringTokenizer(slaConfig, },); has issue. It tries to tokenized on ,
and },.
a.slaConfig={alert_contact=hadoo...@oozie.com},{alert_events=START_MET,DURATION_MISS,END_MET},;
Will become
alert_events=START_MET
alert_contact=hadoo...@oozie.com.
Fix is used to use String.split().
{code}
private void slaConfigStringToMap() {
if (slaConfig != null) {
StringTokenizer st = new StringTokenizer(slaConfig, },);
while (st.hasMoreTokens()) {
String token = st.nextToken();
String[] pair = token.split(=);
if (pair.length == 2) {
slaConfigMap.put(pair[0].substring(1), pair[1]);
}
}
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Build failed in Jenkins: oozie-trunk-precommit-build #2030
See https://builds.apache.org/job/oozie-trunk-precommit-build/2030/changes Changes: [rkanter] OOZIE-2017 On startup, StatusTransitService can transition Coordinators that were in PREPSUSPENDED to RUNNING (rkanter) [purushah] OOZIE-2023 Job rerun can stuck in prep [rkanter] ammending release-log for OOZIE-2017 [ryota.egashira] OOZIE-2026 fix synchronization in SLACalculatorMemory.addJobStatus to avoid duplicated SLA message (ryota) -- [...truncated 10123 lines...] [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] [INFO] [INFO] Building Apache Oozie Tools 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-tools --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-tools --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-tools --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-tools --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools --- [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools --- [INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml [WARNING] The following patterns were never triggered in this artifact exclusion filter: o '*:*:pom:*' [INFO] Copying files to https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools [WARNING] Assembly file: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools is not a regular file (it may be a directory). It cannot be attached to the project build for installation or deployment. [INFO] [INFO] [INFO] Building Apache Oozie MiniOozie 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-mini --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-mini --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-mini --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini --- [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml [INFO] [INFO] [INFO] Building Apache Oozie Distro 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:resources
Jenkins build is back to normal : oozie-trunk-precommit-build #2031
See https://builds.apache.org/job/oozie-trunk-precommit-build/2031/
[jira] [Commented] (OOZIE-1385) Make Uber Mode the default
[
https://issues.apache.org/jira/browse/OOZIE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14167442#comment-14167442
]
Hadoop QA commented on OOZIE-1385:
--
Testing JIRA OOZIE-1385
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1536
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2031/
Make Uber Mode the default
--
Key: OOZIE-1385
URL: https://issues.apache.org/jira/browse/OOZIE-1385
Project: Oozie
Issue Type: Bug
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
Fix For: trunk
Attachments: OOZIE-1385.patch
Once we sort out the Uber mode for the launcher job issues, we should make it
the default to take advantage of the speed-up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
