[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (92 issues) Subscriber: ooziedaily Key Summary OOZIE-3573 Fix oozie-default.xml descriptions https://issues.apache.org/jira/browse/OOZIE-3573 OOZIE-3568 Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean https://issues.apache.org/jira/browse/OOZIE-3568 OOZIE-3567 Oozie ShellAction should support absolute bash file path https://issues.apache.org/jira/browse/OOZIE-3567 OOZIE-3560 IDEA shows have some error in index.jsp https://issues.apache.org/jira/browse/OOZIE-3560 OOZIE-3482 Fix bug in CoordSubmitXCommand#validateCoordinatorJob https://issues.apache.org/jira/browse/OOZIE-3482 OOZIE-3480 Add windowactionstatus metrics in DBLiteWorkflowStoreService https://issues.apache.org/jira/browse/OOZIE-3480 OOZIE-3461 CoordMaterializeTriggerService code cleanup https://issues.apache.org/jira/browse/OOZIE-3461 OOZIE-3449 Make spark-2 as the default profile https://issues.apache.org/jira/browse/OOZIE-3449 OOZIE-3447 Run test case in local : It shows oozie-hsqldb-orm.xml exception https://issues.apache.org/jira/browse/OOZIE-3447 OOZIE-3418 Upgrade to Guava 27 https://issues.apache.org/jira/browse/OOZIE-3418 OOZIE-3404 The env variable of SPARK_HOME needs to be set when running pySpark https://issues.apache.org/jira/browse/OOZIE-3404 OOZIE-3375 Can't use empty in coordinator https://issues.apache.org/jira/browse/OOZIE-3375 OOZIE-3367 Using && in EL expressions in oozie bundle.xml files generates parse errors https://issues.apache.org/jira/browse/OOZIE-3367 OOZIE-3366 Update workflow status and subworkflow status on suspend command https://issues.apache.org/jira/browse/OOZIE-3366 OOZIE-3364 Rerunning Oozie bundle jobs starts the coordinators in indeterminate order https://issues.apache.org/jira/browse/OOZIE-3364 OOZIE-3362 When killed, SSH action should kill the spawned processes on target host https://issues.apache.org/jira/browse/OOZIE-3362 OOZIE-3335 Cleanup parseFilter methods https://issues.apache.org/jira/browse/OOZIE-3335 OOZIE-3328 Create Hive compatibility action executor to run hive actions using beeline https://issues.apache.org/jira/browse/OOZIE-3328 OOZIE-3319 Log SSH action callback error output https://issues.apache.org/jira/browse/OOZIE-3319 OOZIE-3301 Update NOTICE file https://issues.apache.org/jira/browse/OOZIE-3301 OOZIE-3274 Remove slf4j https://issues.apache.org/jira/browse/OOZIE-3274 OOZIE-3266 Coord action rerun support RERUN_SKIP_NODES option https://issues.apache.org/jira/browse/OOZIE-3266 OOZIE-3256 refactor OozieCLI class https://issues.apache.org/jira/browse/OOZIE-3256 OOZIE-3254 [coordinator] LAST_ONLY and NONE execution modes: possible OutOfMemoryError when there are too many coordinator actions to materialize https://issues.apache.org/jira/browse/OOZIE-3254 OOZIE-3199 Let system property restriction configurable https://issues.apache.org/jira/browse/OOZIE-3199 OOZIE-3196 Authorization: restrict world readability by user https://issues.apache.org/jira/browse/OOZIE-3196 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 OOZIE-3137 Add support for log4j2 in HiveMain https://issues.apache.org/jira/browse/OOZIE-3137 OOZIE-3135 Configure log4j2 in SqoopMain https://issues.apache.org/jira/browse/OOZIE-3135 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-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-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2834 ParameterVerifier logging non-useful warning for workflow definition https://issues.apache.org/jira/browse/OOZIE-2834 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-2784 Include WEEK as a parameter in the Coordinator Expression Language Evaulator
[jira] [Commented] (OOZIE-3574) JavaAction create uncorrect fileSystem instance in addActionLibs method
[
https://issues.apache.org/jira/browse/OOZIE-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999683#comment-16999683
]
Junfan Zhang commented on OOZIE-3574:
-
Please check this bug. [~asalamon74]. I will upload patch laterly
> JavaAction create uncorrect fileSystem instance in addActionLibs method
> ---
>
> Key: OOZIE-3574
> URL: https://issues.apache.org/jira/browse/OOZIE-3574
> Project: Oozie
> Issue Type: Bug
>Reporter: Junfan Zhang
>Assignee: Junfan Zhang
>Priority: Major
>
> Code is
> [here|https://github.com/apache/oozie/blob/9c288fe5cea6f2fbbae76f720b9e215acdd07709/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L734].
> If actionlibPath scheme is different from appPath (like actionLibPath's
> scheme is s3a, but the appPath is hdfs), this will fail to execute
> {{fs.exist(actionLibsPath)}}. So i think Oozie should create fileSystem by
> actionLibsPath.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OOZIE-3574) JavaAction create uncorrect fileSystem instance in addActionLibs method
Junfan Zhang created OOZIE-3574:
---
Summary: JavaAction create uncorrect fileSystem instance in
addActionLibs method
Key: OOZIE-3574
URL: https://issues.apache.org/jira/browse/OOZIE-3574
Project: Oozie
Issue Type: Bug
Reporter: Junfan Zhang
Assignee: Junfan Zhang
Code is
[here|https://github.com/apache/oozie/blob/9c288fe5cea6f2fbbae76f720b9e215acdd07709/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L734].
If actionlibPath scheme is different from appPath (like actionLibPath's scheme
is s3a, but the appPath is hdfs), this will fail to execute
{{fs.exist(actionLibsPath)}}. So i think Oozie should create fileSystem by
actionLibsPath.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OOZIE-3572) Support workflow action running in different clusters?
[ https://issues.apache.org/jira/browse/OOZIE-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999667#comment-16999667 ] Junfan Zhang commented on OOZIE-3572: - *Other possibility would be to use a single Oozie server and specify other cluster's resurceManager for the jobs.* This may be a good idea. I will transform the Oozie and test to support multi-cluster scheduling of Workflow actions. If possible, I will update progress and meeting questions here. Thanks [~asalamon74] yours response. > Support workflow action running in different clusters? > -- > > Key: OOZIE-3572 > URL: https://issues.apache.org/jira/browse/OOZIE-3572 > Project: Oozie > Issue Type: Improvement >Reporter: Junfan Zhang >Priority: Major > > Currently in our production environment, there are more than 10 clusters, and > each cluster is deployed with Oozie server. This has caused difficulties in > operation and maintenance, and difficulty in expanding the workflow between > multiple clusters. > Does the community have plans to support actions running in different > clusters? > Or give me some suggestions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3573) Fix oozie-default.xml descriptions
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999387#comment-16999387
]
Hadoop QA commented on OOZIE-3573:
--
Testing JIRA OOZIE-3573
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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 star imports
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:red}-1{color} the patch does not add/modify any testcase
{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{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{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [webapp].
{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: 3199
.{color:orange}Tests failed at first run:{color}
TestLocalOozieClientCoord#testJobsOperations
TestJMSAccessorService#testConnectionRetry
TestBlockingInputStream#testFastWritingBlockingInputStream
TestPriorityDelayQueue#testPeek
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{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/PreCommit-OOZIE-Build/1272/
> Fix oozie-default.xml descriptions
> --
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
> Attachments: OOZIE-3573-001.patch, OOZIE-3573-002.patch
>
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Failed: OOZIE-3573 PreCommit Build #1272
Jira: https://issues.apache.org/jira/browse/OOZIE-3573
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1272/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 2.16 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[INFO] There are no new bugs found totally].
[TRACE] SpotBugs diffs checked and reports created
[TRACE] Summary file size is 2536 bytes
[TRACE] Full summary file size is 1525 bytes
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
removed
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5]
removed
Running test-patch task BACKWARDS_COMPATIBILITY
Running test-patch task TESTS
Running test-patch task DISTRO
Running test-patch task MODERNIZER
Running modernizer op=report
[TRACE] grep -c '.*ERROR.*Prefer'
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-clean.txt
[TRACE] Modernizer errors before patch: 51
[TRACE] grep -c '.*ERROR.*Prefer'
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-patch.txt
[TRACE] Modernizer errors after patch: 51
Testing JIRA OOZIE-3573
Cleaning local git workspace
+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any star imports
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
+1 There are no new bugs found in [fluent-job/fluent-job-api].
+1 There are no new bugs found in [docs].
+1 There are no new bugs found in [core].
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [sharelib/git].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/hcatalog].
+1 There are no new bugs found in [sharelib/distcp].
+1 There are no new bugs found in [tools].
+1 There are no new bugs found in [server].
+1 There are no new bugs found in [client].
+1 There are no new bugs found in [examples].
+1 There are no new bugs found in [webapp].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 3199
Tests failed at first run:
TestLocalOozieClientCoord#testJobsOperations
TestJMSAccessorService#testConnectionRetry
TestBlockingInputStream#testFastWritingBlockingInputStream
TestPriorityDelayQueue#testPeek
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch
+1 MODERNIZER
-1 Overall result, please check the reported -1(s)
The full output of the test-patch run is available at
https://builds.apache.org/job/PreCommit-OOZIE-Build/1272/
Adding comment to JIRA
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 35360 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100
35360 0 100 3536 0 2185 0:00:01 0:00:01 --:--:--
2184{"self":"https://issues.apache.org/jira/rest/api/2/issue/13275214/comment/16999387","id":"16999387","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoo
[jira] [Commented] (OOZIE-3573) Fix oozie-default.xml descriptions
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999303#comment-16999303
]
Adam Arvai commented on OOZIE-3573:
---
[~asalamon74] Thank you for your feedback. Yes, most of the change was because
of the formatting. I uploaded a 2nd patch only with real changes. Typos,
changed/new description. There is no value change.
> Fix oozie-default.xml descriptions
> --
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
> Attachments: OOZIE-3573-001.patch, OOZIE-3573-002.patch
>
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OOZIE-3573) Fix oozie-default.xml descriptions
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999299#comment-16999299
]
Hadoop QA commented on OOZIE-3573:
--
PreCommit-OOZIE-Build started
> Fix oozie-default.xml descriptions
> --
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
> Attachments: OOZIE-3573-001.patch, OOZIE-3573-002.patch
>
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OOZIE-3573) Fix oozie-default.xml descriptions
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Arvai updated OOZIE-3573:
--
Attachment: OOZIE-3573-002.patch
> Fix oozie-default.xml descriptions
> --
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
> Attachments: OOZIE-3573-001.patch, OOZIE-3573-002.patch
>
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean
[
https://issues.apache.org/jira/browse/OOZIE-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999296#comment-16999296
]
Andras Salamon commented on OOZIE-3568:
---
Have you tried to apply your patch to the master branch? I've got the following
error message:
{noformat}
$ git apply -p0 ~/Downloads/OOZIE-3568-004.patch
error:
core/src/test/java/org/apache/oozie/client/rest/TestCoordinatorActionBean.java:
No such file or directory
error:
core/src/test/java/org/apache/oozie/client/rest/TestCoordinatorJobBean.java: No
such file or directory
error:
core/src/test/java/org/apache/oozie/client/rest/TestWorkflowActionBean.java: No
such file or directory
error:
core/src/test/java/org/apache/oozie/client/rest/TestWorkflowJobBean.java: No
such file or directory {noformat}
It's definitely caused by the file renames. Maybe you need to use additional
options ({{-M}} ??) for git diff.
> Have large amount of log information “WARN messages [main] openjpa.MetaData”
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch,
> OOZIE-3568-003.patch, OOZIE-3568-004.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData”
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
> org.apache.oozie.client.rest.JsonWorkflowAction
> org.apache.oozie.client.rest.JsonCoordinatorJob
> org.apache.oozie.client.rest.JsonCoordinatorAction
> org.apache.oozie.client.rest.JsonBundleJob
> for example:
>
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OOZIE-3573) Fix oozie-default.xml descriptions
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Salamon updated OOZIE-3573:
--
Summary: Fix oozie-default.xml descriptions (was: Fix oozie-default.xml
nameNode.whitelist description)
> Fix oozie-default.xml descriptions
> --
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
> Attachments: OOZIE-3573-001.patch
>
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OOZIE-3573) Fix oozie-default.xml nameNode.whitelist description
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999282#comment-16999282
]
Andras Salamon commented on OOZIE-3573:
---
Thanks for the patch [~arvaiadam] it seems to me you have found other problems
in the file, like the additional value after the truststore password
description. I'll rename the Jira according to it.
The test failures also indicate that you've changed some default value which
caused lots of problems. I think in this change only descriptions should be
changed and not default values. (If you'd like to change a default value,
please describe it here and we can discuss it).
I've also realized that you've changed lots of formatting, line breaking, which
makes it difficult to find the important changes. Can you please upload a patch
which only contains the real changes.
> Fix oozie-default.xml nameNode.whitelist description
>
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
> Attachments: OOZIE-3573-001.patch
>
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean
[ https://issues.apache.org/jira/browse/OOZIE-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999260#comment-16999260 ] duan xiong commented on OOZIE-3568: --- [~asalamon74]. Hi, I think this patch is good. Maybe this patch can't handle rename file correct？ So can you tell me how to make a right patch for this issue? Thank you very much. > Have large amount of log information “WARN messages [main] openjpa.MetaData” > in jetty.log need to clean > --- > > Key: OOZIE-3568 > URL: https://issues.apache.org/jira/browse/OOZIE-3568 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: duan xiong >Assignee: duan xiong >Priority: Major > Fix For: 5.3.0 > > Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, > OOZIE-3568-003.patch, OOZIE-3568-004.patch > > > Have large amount of log information “WARN messages [main] openjpa.MetaData” > in jetty.out need to clean: > some not exists class need to enhanced in openjpa: > org.apache.oozie.client.rest.JsonWorkflowJob > org.apache.oozie.client.rest.JsonWorkflowAction > org.apache.oozie.client.rest.JsonCoordinatorJob > org.apache.oozie.client.rest.JsonCoordinatorAction > org.apache.oozie.client.rest.JsonBundleJob > for example: > > 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonBundleJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3573) Fix oozie-default.xml nameNode.whitelist description
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999257#comment-16999257
]
Hadoop QA commented on OOZIE-3573:
--
Testing JIRA OOZIE-3573
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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 star imports
.{color:red}-1{color} the patch contains 6 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{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{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [webapp].
{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: 3199
.Tests failed : 35
.Tests in error : 165
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [34] test failures in [core]. Listing
only the first [5] ones
{color:red}-1{color} [ERROR] There are [1] test failures in [examples]. Listing
only the first [5] ones
testLocalOozieExampleEnd:org.apache.oozie.example.TestLocalOozieExample
{color:red}-1{color} [ERROR] There are [155] test errors in [core]. Listing
only the first [5] ones
testJobDefinition:org.apache.oozie.TestDagEngine
testGetJobs:org.apache.oozie.TestDagEngine
testSubmit:org.apache.oozie.TestDagEngine
{color:red}-1{color} [ERROR] There are [6] test errors in [minitest]. Listing
only the first [5] ones
testParallelFsAndShellWorkflowCompletesSuccessfully:org.apache.oozie.test.TestWorkflow
testWorkflowWithStartAndEndCompletesSuccessfully:org.apache.oozie.test.TestWorkflow
testFsDecisionWorkflowCompletesSuccessfully:org.apache.oozie.test.TestWorkflow
{color:red}-1{color} [ERROR] There are [4] test errors in [sharelib]. Listing
only the first [5] ones
testGitRepoMustHaveScheme:org.apache.oozie.action.hadoop.TestGitMain
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestBlockingInputStream#testLimitedWritingBlockingInputStream
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{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/PreCommit-OOZIE-Build/1270/
> Fix oozie-default.xml nameNode.whitelist description
>
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-357
[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean
[
https://issues.apache.org/jira/browse/OOZIE-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999204#comment-16999204
]
Hadoop QA commented on OOZIE-3568:
--
Testing JIRA OOZIE-3568
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> Have large amount of log information “WARN messages [main] openjpa.MetaData”
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch,
> OOZIE-3568-003.patch, OOZIE-3568-004.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData”
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
> org.apache.oozie.client.rest.JsonWorkflowAction
> org.apache.oozie.client.rest.JsonCoordinatorJob
> org.apache.oozie.client.rest.JsonCoordinatorAction
> org.apache.oozie.client.rest.JsonBundleJob
> for example:
>
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the
> openjpa.MetaDataFactory configuration property could not be loaded by
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Failed: OOZIE-3568 PreCommit Build #1271
Jira: https://issues.apache.org/jira/browse/OOZIE-3568 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1271/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 902.17 KB...] [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ oozie-zookeeper-security-tests --- [INFO] No sources to compile [INFO] [INFO] --- modernizer-maven-plugin:1.8.0:modernizer (default-cli) @ oozie-zookeeper-security-tests --- [INFO] [INFO] Reactor Summary for Apache Oozie Main 5.3.0-SNAPSHOT: [INFO] [INFO] Apache Oozie Main .. SUCCESS [ 0.938 s] [INFO] Apache Oozie Fluent Job SUCCESS [ 0.076 s] [INFO] Apache Oozie Fluent Job API SUCCESS [ 6.840 s] [INFO] Apache Oozie Client SUCCESS [ 1.742 s] [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 1.196 s] [INFO] Apache Oozie Share Lib HCatalog SUCCESS [ 1.116 s] [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [ 0.307 s] [INFO] Apache Oozie Core .. SUCCESS [ 8.357 s] [INFO] Apache Oozie Share Lib Streaming ... SUCCESS [ 1.930 s] [INFO] Apache Oozie Share Lib Pig . SUCCESS [ 1.282 s] [INFO] Apache Oozie Share Lib Git . SUCCESS [ 1.758 s] [INFO] Apache Oozie Share Lib Hive SUCCESS [ 1.054 s] [INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 1.636 s] [INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [ 1.584 s] [INFO] Apache Oozie Examples .. SUCCESS [ 1.620 s] [INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 2.353 s] [INFO] Apache Oozie Share Lib . SUCCESS [ 0.019 s] [INFO] Apache Oozie Docs .. SUCCESS [ 0.036 s] [INFO] Apache Oozie WebApp SUCCESS [ 1.789 s] [INFO] Apache Oozie Tools . SUCCESS [ 1.356 s] [INFO] Apache Oozie MiniOozie . SUCCESS [ 1.237 s] [INFO] Apache Oozie Fluent Job Client . SUCCESS [ 0.799 s] [INFO] Apache Oozie Server SUCCESS [ 2.439 s] [INFO] Apache Oozie Distro SUCCESS [ 1.620 s] [INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [ 1.935 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 46.614 s [INFO] Finished at: 2019-12-18T14:19:17Z [INFO] EXITVALUE 0 [TRACE] Modernizer output in HEAD verified and saved Applying patch Checking patch core/pom.xml... Checking patch core/src/main/resources/META-INF/persistence.xml... Checking patch core/src/test/java/org/apache/oozie/client/rest/TestCoordinatorActionBean.java... error: core/src/test/java/org/apache/oozie/client/rest/TestCoordinatorActionBean.java: No such file or directory Checking patch core/src/test/java/org/apache/oozie/client/rest/TestCoordinatorJobBean.java... error: core/src/test/java/org/apache/oozie/client/rest/TestCoordinatorJobBean.java: No such file or directory Checking patch core/src/test/java/org/apache/oozie/client/rest/TestWorkflowActionBean.java... error: core/src/test/java/org/apache/oozie/client/rest/TestWorkflowActionBean.java: No such file or directory Checking patch core/src/test/java/org/apache/oozie/client/rest/TestWorkflowJobBean.java... error: core/src/test/java/org/apache/oozie/client/rest/TestWorkflowJobBean.java: No such file or directory Checking patch pom.xml... error: while searching for: **/JsonWorkflowJob.class, **/JsonWorkflowAction.class, **/JsonCoordinatorJob.class, **/JsonCoordinatorAction.class, **/JsonSLAEvent.class, **/JsonSLARegistrationEvent.class, **/JsonBundleJob.class, **/WorkflowJobBean.class, **/WorkflowActionBean.class, error: patch failed: pom.xml:560 error: pom.xml: patch does not apply Checking patch src/main/resources/META-INF/persistence.xml... error: src/main/resources/META-INF/persistence.xml: No such file or directory Checking patch src/test/ja
[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean
[ https://issues.apache.org/jira/browse/OOZIE-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999199#comment-16999199 ] Hadoop QA commented on OOZIE-3568: -- PreCommit-OOZIE-Build started > Have large amount of log information “WARN messages [main] openjpa.MetaData” > in jetty.log need to clean > --- > > Key: OOZIE-3568 > URL: https://issues.apache.org/jira/browse/OOZIE-3568 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: duan xiong >Assignee: duan xiong >Priority: Major > Fix For: 5.3.0 > > Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, > OOZIE-3568-003.patch, OOZIE-3568-004.patch > > > Have large amount of log information “WARN messages [main] openjpa.MetaData” > in jetty.out need to clean: > some not exists class need to enhanced in openjpa: > org.apache.oozie.client.rest.JsonWorkflowJob > org.apache.oozie.client.rest.JsonWorkflowAction > org.apache.oozie.client.rest.JsonCoordinatorJob > org.apache.oozie.client.rest.JsonCoordinatorAction > org.apache.oozie.client.rest.JsonBundleJob > for example: > > 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonBundleJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean
[ https://issues.apache.org/jira/browse/OOZIE-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] duan xiong updated OOZIE-3568: -- Attachment: OOZIE-3568-004.patch > Have large amount of log information “WARN messages [main] openjpa.MetaData” > in jetty.log need to clean > --- > > Key: OOZIE-3568 > URL: https://issues.apache.org/jira/browse/OOZIE-3568 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: duan xiong >Assignee: duan xiong >Priority: Major > Fix For: 5.3.0 > > Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, > OOZIE-3568-003.patch, OOZIE-3568-004.patch > > > Have large amount of log information “WARN messages [main] openjpa.MetaData” > in jetty.out need to clean: > some not exists class need to enhanced in openjpa: > org.apache.oozie.client.rest.JsonWorkflowJob > org.apache.oozie.client.rest.JsonWorkflowAction > org.apache.oozie.client.rest.JsonCoordinatorJob > org.apache.oozie.client.rest.JsonCoordinatorAction > org.apache.oozie.client.rest.JsonBundleJob > for example: > > 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonBundleJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class > "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@33909752; ignoring. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3573) Fix oozie-default.xml nameNode.whitelist description
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999161#comment-16999161
]
Hadoop QA commented on OOZIE-3573:
--
PreCommit-OOZIE-Build started
> Fix oozie-default.xml nameNode.whitelist description
>
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
> Attachments: OOZIE-3573-001.patch
>
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OOZIE-3572) Support workflow action running in different clusters?
[
https://issues.apache.org/jira/browse/OOZIE-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999153#comment-16999153
]
Andras Salamon commented on OOZIE-3572:
---
I don't think that Oozie supports such a multicluster environment.
There is a section in the
[https://github.com/apache/oozie/blob/master/docs/src/site/markdown/WorkflowFunctionalSpec.md]
documentation, which implies that a long time ago something similar was
possible:
{noformat}
2009SEP15
3.2.6 Removing support for sub-workflow in a different Oozie instance (removing
the 'oozie' element)
{noformat}
Other possibility would be to use a single Oozie server and specify other
cluster's resurceManager for the jobs. To be honest, I've tried it once but it
was not working so probably it's also not working out of the box.
> Support workflow action running in different clusters?
> --
>
> Key: OOZIE-3572
> URL: https://issues.apache.org/jira/browse/OOZIE-3572
> Project: Oozie
> Issue Type: Improvement
>Reporter: Junfan Zhang
>Priority: Major
>
> Currently in our production environment, there are more than 10 clusters, and
> each cluster is deployed with Oozie server. This has caused difficulties in
> operation and maintenance, and difficulty in expanding the workflow between
> multiple clusters.
> Does the community have plans to support actions running in different
> clusters?
> Or give me some suggestions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OOZIE-3573) Fix oozie-default.xml nameNode.whitelist description
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Arvai updated OOZIE-3573:
--
Attachment: OOZIE-3573-001.patch
> Fix oozie-default.xml nameNode.whitelist description
>
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
> Attachments: OOZIE-3573-001.patch
>
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (OOZIE-3573) Fix oozie-default.xml nameNode.whitelist description
[
https://issues.apache.org/jira/browse/OOZIE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Arvai reassigned OOZIE-3573:
-
Assignee: Adam Arvai
> Fix oozie-default.xml nameNode.whitelist description
>
>
> Key: OOZIE-3573
> URL: https://issues.apache.org/jira/browse/OOZIE-3573
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Adam Arvai
>Priority: Minor
>
> The nameNode.whitelist section in
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
> contains the following section:
> {noformat}
>
> oozie.service.HadoopAccessorService.nameNode.whitelist
>
>
> Whitelisted job tracker for Oozie service.
>
>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description
> fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OOZIE-3573) Fix oozie-default.xml nameNode.whitelist description
Andras Salamon created OOZIE-3573:
-
Summary: Fix oozie-default.xml nameNode.whitelist description
Key: OOZIE-3573
URL: https://issues.apache.org/jira/browse/OOZIE-3573
Project: Oozie
Issue Type: Bug
Affects Versions: trunk
Reporter: Andras Salamon
The nameNode.whitelist section in
[oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
contains the following section:
{noformat}
oozie.service.HadoopAccessorService.nameNode.whitelist
Whitelisted job tracker for Oozie service.
{noformat}
This is clearly a block-copy error, description is copied from the previous
{{jobTracker.whitelist}} section.
We should fix it, maybe it would be useful to check the other description
fields in the file as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OOZIE-3570) SSH Action execution command should add the mechanism of timeout
[
https://issues.apache.org/jira/browse/OOZIE-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998930#comment-16998930
]
Andras Salamon commented on OOZIE-3570:
---
Thanks [~zuston] for the explanation, I understand it now. I think such a
change should be tested thoroughly, since the ssh action unit tests are not
working.
> SSH Action execution command should add the mechanism of timeout
>
>
> Key: OOZIE-3570
> URL: https://issues.apache.org/jira/browse/OOZIE-3570
> Project: Oozie
> Issue Type: Bug
>Reporter: Junfan Zhang
>Assignee: Junfan Zhang
>Priority: Major
>
> *Phenomenon*
> Currently, In SSH action, When the remote machine is hung, execution command
> will waiting. This will cause the number of Oozie threads to be occupied,
> which will cause delays in scheduling other tasks.
> *Solution*
> SSH Action execution command should add timeout prefix. But the {{ssh -o
> ConnectTimeout=20}} is invalid
> {code:java}
> timeout 20s ssh xx
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
