date:20180606

[jira] Subscription: Oozie Patch Available

2018-06-06 Thread jira

Issue Subscription
Filter: Oozie Patch Available (102 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3275  [docs] Update AG_Install.twiki with Access Control List 
documentation
https://issues.apache.org/jira/browse/OOZIE-3275
OOZIE-3274  Remove slf4j
https://issues.apache.org/jira/browse/OOZIE-3274
OOZIE-3270   Upgrade Derby to 10.14.1.0
https://issues.apache.org/jira/browse/OOZIE-3270
OOZIE-3265  properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to 
appear together
https://issues.apache.org/jira/browse/OOZIE-3265
OOZIE-3260  [sla] Remove stale item above max retries on JPA related errors 
from in-memory SLA map
https://issues.apache.org/jira/browse/OOZIE-3260
OOZIE-3256  refactor OozieCLI class
https://issues.apache.org/jira/browse/OOZIE-3256
OOZIE-3249  [tools] Instrumentation log parser
https://issues.apache.org/jira/browse/OOZIE-3249
OOZIE-3233  Remove DST shift from the coordinator job's end time
https://issues.apache.org/jira/browse/OOZIE-3233
OOZIE-3218  Oozie Sqoop action with command splits the select clause into 
multiple parts due to delimiter being space
https://issues.apache.org/jira/browse/OOZIE-3218
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-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3193  Applications are not killed when submitted via subworkflow
https://issues.apache.org/jira/browse/OOZIE-3193
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3160  PriorityDelayQueue put()/take() can cause significant CPU load due 
to busy waiting
https://issues.apache.org/jira/browse/OOZIE-3160
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3109  Escape log-streaming's HTML-specific characters
https://issues.apache.org/jira/browse/OOZIE-3109
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-3061  Kill only those child jobs which are not already killed
https://issues.apache.org/jira/browse/OOZIE-3061
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  [examples] Fix Findbugs warnings
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
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-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/br

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Peter Cseh (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503911#comment-16503911
 ] 

Peter Cseh commented on OOZIE-3274:
---

So it looks like we can't even instantiate Xtestcase without slf4j. That covers 
every test where we use a MiniCluster of any sort.
We could try to pull in slf4j only in test scope to avoid this, but it's 
worrying at least :)


> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.rebased.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503909#comment-16503909
 ] 

Hadoop QA commented on OOZIE-3274:
--

PreCommit-OOZIE-Build started


> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.rebased.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

FINAL REMINDER: Apache EU Roadshow 2018 in Berlin next week!

2018-06-06 Thread sharan


Hello Apache Supporters and Enthusiasts

This is a final reminder that our Apache EU Roadshow will be held in 
Berlin next week on 13th and 14th June 2018. We will have 28 different 
sessions running over 2 days that cover some great topics. So if you are 
interested in Microservices, Internet of Things (IoT), Cloud, Apache 
Tomcat or Apache Http Server then we have something for you.


https://foss-backstage.de/sessions/apache-roadshow

We will be co-located with FOSS Backstage, so if you are interested in 
topics such as incubator, the Apache Way, open source governance, legal, 
trademarks or simply open source communities then there will be 
something there for you too.  You can attend any of talks, presentations 
and workshops from the Apache EU Roadshow or FOSS Backstage.


You can find details of the combined Apache EU Roadshow and FOSS 
Backstage conference schedule below:


https://foss-backstage.de/schedule?day=2018-06-13

Ticket prices go up on 8th June 2018 and we have a last minute discount 
code that anyone can use before the deadline:


15% discount code: ASF15_discount
valid until June 7, 23:55 CET

You can register at the following link:

https://foss-backstage.de/tickets

Our Apache booth and lounge will be open from 11th - 14th June for 
meetups, hacking or to simply relax between sessions. And we will be 
posting regular updates on social media throughout next week so please 
follow us on Twitter @ApacheCon


Thank you for your continued support and we look forward to seeing you 
in Berlin!


Thanks
Sharan Foga, VP Apache Community Development

http://apachecon.com/

PLEASE NOTE: You are receiving this message because you are subscribed 
to a user@ or dev@ list of one or more Apache Software Foundation projects.

[jira] [Commented] (OOZIE-3233) Remove DST shift from the coordinator job's end time

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503645#comment-16503645
 ] 

Hadoop QA commented on OOZIE-3233:
--


Testing JIRA OOZIE-3233

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 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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(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 [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {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/spark].
. {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/hcatalog].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {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 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: 2146
.{color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommand#testNone
.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 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/615/



> Remove DST shift from the coordinator job's end time
> 
>
> Key: OOZIE-3233
> URL: https://issues.apache.org/jira/browse/OOZIE-3233
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3233-001.patch
>
>
> With the fix of OOZIE-2726 a small functionality change is included for the 
> following scenario:
>  * between the start and end date there is one DST start
>  * the nominal time of the last action should be maximum 1h before the end 
> time.
>  * this last action will not be created after the OOZIE-2726, because of the 
> DST correction, the nominal time will exceed the end time. 
> The documentation says that "t_he Oozie processing timezone is used to 
> resolve coordinator jobs start/*end times* ..._".
> I think that we should not include functionality changes with test fixtures, 
> so I would remove the DST correction from the end time: 
> [https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java#L461]
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Success: OOZIE-3233 PreCommit Build #615

2018-06-06 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-3233
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/615/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.72 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [core].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2365 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3233

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 line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(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 [docs].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +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/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
+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: 2146
Tests failed at first run:
TestCoordActionInputCheckXCommand#testNone
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/615/

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 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13157155/comment/16503645","id":"16503645","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=hadoopqa&avatarId=10393"},"dis

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503512#comment-16503512
 ] 

Hadoop QA commented on OOZIE-3274:
--


Testing JIRA OOZIE-3274

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:red}-1{color} the patch contains 3 line(s) with 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: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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(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:orange}0{color} There are [12] new bugs found in total that would be 
nice to have fixed.
. {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{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:orange}0{color} There are [12] new bugs found in [server] that would 
be nice to have fixed.
. You can find the FindBugs diff here: server/findbugs-new.html
. {color:green}+1{color} There are no new bugs found in [docs].
. {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/pig].
. {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/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/sqoop].
. {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/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{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: 552
.Tests failed: 6
.Tests errors: 392

.The patch failed the following testcases:

scratchDir_Is_Created_When_Setup_Called_And_ScratchDir_Did_Not_Exist(org.apache.oozie.server.TestJspHandler)
scratchDir_Is_Reused_When_Setup_Called_And_ScratchDir_Existed(org.apache.oozie.server.TestJspHandler)
scratchDir_Cannot_Be_Created_When_Setup_Called_And_ScratchDir_Did_Not_Exist(org.apache.oozie.server.TestJspHandler)
testYarnUnregisterFails(org.apache.oozie.action.hadoop.TestLauncherAM)
testUpdateActionDataFailsWithActionError(org.apache.oozie.action.hadoop.TestLauncherAM)
testActionPrepareFails(org.apache.oozie.action.hadoop.TestLauncherAM)

.Tests failing with errors:
initializationError(org.apache.oozie.example.TestLocalOozieExample)
initializationError(org.apache.oozie.util.TestZKUtilsWithSecurity)
initializationError(org.apache.oozie.test.TestParallelJPAOperationRetries)
initializationError(org.apache.oozie.test.TestWorkflow)
initializationError(org.apache.oozie.test.TestWorkflowRetries)
initializationError(org.apache.oozie.util.TestTimestampedMessageParser)
initializationError(org.apache.oozie.command.bundle.TestBundleRerunXCommand)
initializationError(org.apache.oozie.jms.TestJMSJobEventListener)
initializationError(org.apache.oozie.executor.jpa.TestCoordActionsActiveCountJPAExecutor)
initializationError(org.apache.oozie.executor.jpa.TestCoordActionGetForStartJPAExecutor)
initializationError(org.apache.oozie.command.coord.TestPastActionsTimeOut)
initializationError(org.apache.oozie.command.coord.TestCoordKillXCommand)
initializationError(org.apache.oozie.executor.jpa.TestCoordJobGetActionsRunningJPAExecutor)
initializationError(org.apache.oozie.command.coord.TestCoordRerunXCommand)
initializationError(org.apache.oozie.TestCoordinatorEngineStreamLog)
initializationError(org.apache.oozie.coord.TestCoordUtils)
initializationError(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser)
initializationError(org.apache.oozie.util.db.TestSLAD

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Denes Bodo (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503510#comment-16503510
 ] 

Denes Bodo commented on OOZIE-3274:
---

[~bpgergo] sorry for the late reaction. I think using slf4j in client is okay 
with slf4j-simple implementation. Otherwise hadoop's KerberosAuthenticator miss 
the log appender configuration.

> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.rebased.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread JIRA



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503500#comment-16503500
 ] 

Péter Gergő Barna commented on OOZIE-3274:
--

[~gezapeti], thanks for looking into this. First patch was something that would 
indicate what is this issue about.

This new patch should work for master branch.

> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.rebased.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3233) Remove DST shift from the coordinator job's end time

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503495#comment-16503495
 ] 

Hadoop QA commented on OOZIE-3233:
--

PreCommit-OOZIE-Build started


> Remove DST shift from the coordinator job's end time
> 
>
> Key: OOZIE-3233
> URL: https://issues.apache.org/jira/browse/OOZIE-3233
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3233-001.patch
>
>
> With the fix of OOZIE-2726 a small functionality change is included for the 
> following scenario:
>  * between the start and end date there is one DST start
>  * the nominal time of the last action should be maximum 1h before the end 
> time.
>  * this last action will not be created after the OOZIE-2726, because of the 
> DST correction, the nominal time will exceed the end time. 
> The documentation says that "t_he Oozie processing timezone is used to 
> resolve coordinator jobs start/*end times* ..._".
> I think that we should not include functionality changes with test fixtures, 
> so I would remove the DST correction from the end time: 
> [https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java#L461]
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503496#comment-16503496
 ] 

Hadoop QA commented on OOZIE-3274:
--

PreCommit-OOZIE-Build started


> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.rebased.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3274) Remove slf4j

2018-06-06 Thread JIRA



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

Péter Gergő Barna updated OOZIE-3274:
-
Attachment: OOZIE-3274.rebased.patch

> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.rebased.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3274) Remove slf4j

2018-06-06 Thread JIRA



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

Péter Gergő Barna updated OOZIE-3274:
-
Attachment: (was: OOZIE-3274.patch)

> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.rebased.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3233) Remove DST shift from the coordinator job's end time

2018-06-06 Thread Julia Kinga Marton (JIRA)



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

Julia Kinga Marton updated OOZIE-3233:
--
Attachment: OOZIE-3233-001.patch

> Remove DST shift from the coordinator job's end time
> 
>
> Key: OOZIE-3233
> URL: https://issues.apache.org/jira/browse/OOZIE-3233
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3233-001.patch
>
>
> With the fix of OOZIE-2726 a small functionality change is included for the 
> following scenario:
>  * between the start and end date there is one DST start
>  * the nominal time of the last action should be maximum 1h before the end 
> time.
>  * this last action will not be created after the OOZIE-2726, because of the 
> DST correction, the nominal time will exceed the end time. 
> The documentation says that "t_he Oozie processing timezone is used to 
> resolve coordinator jobs start/*end times* ..._".
> I think that we should not include functionality changes with test fixtures, 
> so I would remove the DST correction from the end time: 
> [https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java#L461]
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503425#comment-16503425
 ] 

Hadoop QA commented on OOZIE-1393:
--


Testing JIRA OOZIE-1393

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 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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(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 [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {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/distcp].
. {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/streaming].
. {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/oozie].
. {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/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {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 [docs].
. {color:green}+1{color} There are no new bugs found in [server].
{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: 2146
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
.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 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/613/



> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393-005.patch, 
> OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 PM.png, Screen Shot 
> 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionEx

Success: OOZIE-1393 PreCommit Build #613

2018-06-06 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-1393
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/613/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.72 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2365 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-1393

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 line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(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 [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +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 [docs].
 +1 There are no new bugs found in [server].
+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: 2146
Tests failed at first run:
TestCoordActionsKillXCommand#testActionKillCommandDate
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/613/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  31850 0  100  3185  0   3373 --:--:-- --:--:-- --:--:--  
3373{"self":"https://issues.apache.org/jira/rest/api/2/issue/12649490/comment/16503425","id":"16503425","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=hadoopqa&ava

Re: Review Request 66930: OOZIE-2791 ShareLib installation may fail on busy Hadoop clusters

2018-06-06 Thread András Piros via Review Board


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




tools/src/main/java/org/apache/oozie/tools/OozieSharelibCLI.java
Lines 337-341 (patched)


Extract parameters to local variables for better readability.



tools/src/test/java/org/apache/oozie/tools/TestConcurrentCopyFromLocal.java
Lines 35 (patched)


When we have `JUnit4Runner` (have we?) we can use `@Rule public 
TemporaryFolder tmpFolder;` instead.



tools/src/test/java/org/apache/oozie/tools/TestConcurrentCopyFromLocal.java
Lines 43 (patched)


Best is to inject necessary, stateful components into 
`TestOozieSharelibCLIHelper` (need to find a better name...) constructor.



tools/src/test/java/org/apache/oozie/tools/TestConcurrentCopyFromLocal.java
Lines 51 (patched)


Best is to inject necessary, stateful components into 
`TestOozieSharelibCLIHelper` (need to find a better name...) constructor, and 
call e.g. `services.destroy()` explicitly here.



tools/src/test/java/org/apache/oozie/tools/TestConcurrentCopyFromLocal.java
Lines 55 (patched)


I don't get from the unit test name alone what it's supposed to test and 
what is the expectation.



tools/src/test/java/org/apache/oozie/tools/TestCopyTaskCallable.java
Lines 42 (patched)


When we have `JUnit4Runner` (have we?) we can use `@Rule public 
TemporaryFolder tmpFolder;` instead.



tools/src/test/java/org/apache/oozie/tools/TestCopyTaskCallable.java
Lines 44 (patched)


Best is to inject necessary, stateful components into 
`TestOozieSharelibCLIHelper` (need to find a better name...) constructor.



tools/src/test/java/org/apache/oozie/tools/TestCopyTaskCallable.java
Lines 57 (patched)


Best is to inject necessary, stateful components into 
`TestOozieSharelibCLIHelper` (need to find a better name...) constructor, and 
call e.g. `services.destroy()` explicitly here.



tools/src/test/java/org/apache/oozie/tools/TestCopyTaskCallable.java
Lines 61 (patched)


Same as above - please provide a more describing name.

It would be great to have different unit test cases with and without an own 
`ExecutorService`, testing with a single thread / many concurrent threads, and 
covering the previously failing functionality as well.



tools/src/test/java/org/apache/oozie/tools/TestCopyTaskCallable.java
Lines 64-65 (patched)


Copying more files per thread can also be a different test case.



tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLI.java
Line 51 (original), 39 (patched)


When we have `JUnit4Runner` (have we?) we can use `@Rule public 
TemporaryFolder tmpFolder;` instead.



tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLI.java
Lines 41 (patched)


Best is to inject necessary, stateful components into 
`TestOozieSharelibCLIHelper` (need to find a better name...) constructor.



tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLI.java
Lines 58 (patched)


Best is to inject necessary, stateful components into 
`TestOozieSharelibCLIHelper` (need to find a better name...) constructor, and 
call e.g. `services.destroy()` explicitly here.



tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLIHelper.java
Lines 35 (patched)


`OozieSharelibFileOperations` is a better name. It's not a test class, and 
I don't like the words `Helper`, `Util`, and the like as class or method names.



tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLIHelper.java
Lines 38-40 (patched)


Would have all these as `private final`, and injected via constructor.



tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLIHelper.java
Lines 81-90 (patched)


Would rather inject a `FileSystem` instance from the outside and `init()` 
it from the caller class' `setUp()` method.



tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLIHelper.java
Lines 92-103 (patched)


Would rather inject a `Services` instance from the outside and `init()` it 
from the

[jira] [Commented] (OOZIE-2791) ShareLib installation may fail on busy Hadoop clusters

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503350#comment-16503350
 ] 

Hadoop QA commented on OOZIE-2791:
--


Testing JIRA OOZIE-2791

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:red}-1{color} the patch contains 1 line(s) longer than 132 
characters
.{color:green}+1{color} the patch adds/modifies 5 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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(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 [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {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 [docs].
. {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/pig].
. {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/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/sqoop].
. {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/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{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: 2151
{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/PreCommit-OOZIE-Build/612/



> ShareLib installation may fail on busy Hadoop clusters
> --
>
> Key: OOZIE-2791
> URL: https://issues.apache.org/jira/browse/OOZIE-2791
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2791-003.patch, OOZIE-2791-004.patch, 
> OOZIE-2791-005.patch, OOZIE-2791-006.patch, OOZIE-2791-007.patch, 
> OOZIE-2791-01.patch, OOZIE-2791-02.patch
>
>
> On a busy Hadoop cluster it can happen that users cannot install properly  
> Oozie ShareLib.
> Example on a Hadoop 2.4.0 pseudo cluster sharelib installion with a  
> concurrency number set high (to simulate a busy cluster):
> {code}
> oozie-setup.sh sharelib create -fs hdfs://localhost:9000 -locallib 
> oozie-sharelib-*.tar.gz -concurrency 150
> {code}
> You can see a lot of errors (failed copy tasks) on the output:
> {code}
> Running 464 copy tasks on 150 threads
> Error: Copy task failed with exception
> Stack trace for the error was (for debug purposes):
> --
> org.apache.hadoop.ipc.RemoteException(java.io.IOException): File 
> /user/asasvari/share/lib/lib_20170207105926/distcp/hadoop-distcp-2.4.0.jar 
> could only be replicated to 0 nodes instead of minReplication (=1).  There 
> are 1 datanode(s) running and no node(s) are excluded in this operation.
>   at 
> org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget(BlockManager.java:1430)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2684)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.jav

Failed: OOZIE-2791 PreCommit Build #612

2018-06-06 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-2791
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/612/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/streaming].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2363 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-2791

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 contains 1 line(s) longer than 132 characters
+1 the patch adds/modifies 5 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(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 [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +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 [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +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/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+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: 2151
+1 DISTRO
+1 distro tarball builds with the patch 


-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/612/

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 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13040921/comment/16503350","id":"16503350","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/useravat

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503290#comment-16503290
 ] 

Hadoop QA commented on OOZIE-1393:
--

PreCommit-OOZIE-Build started


> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393-005.patch, 
> OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 PM.png, Screen Shot 
> 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo (JIRA)



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

Denes Bodo updated OOZIE-1393:
--
Attachment: OOZIE-1393-005.patch

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393-005.patch, 
> OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 PM.png, Screen Shot 
> 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503250#comment-16503250
 ] 

Denes Bodo commented on OOZIE-1393:
---

Sure, thanks. I am on it already.

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 
> 2018-05-22 at 7.35.36 PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3277) Check for star imports in patches in pre-commit

2018-06-06 Thread Peter Cseh (JIRA)

Peter Cseh created OOZIE-3277:
-

 Summary: Check for star imports in patches in pre-commit
 Key: OOZIE-3277
 URL: https://issues.apache.org/jira/browse/OOZIE-3277
 Project: Oozie
  Issue Type: Improvement
  Components: build
Reporter: Peter Cseh


We don't like to have star imports like {{import java.util.*;}} in our codebase 
yet there is no automatic check for it in the pre-commit hook. 
We should add one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Andras Piros (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503247#comment-16503247
 ] 

Andras Piros commented on OOZIE-1393:
-

Thanks for the contribution [~dionusos]! Failing test seems unrelated. Can you 
please work on {{DG_EmailActionExtension.twiki}} so that each modified line 
fits into 132 characters? Otherwise, the patch looks now really promising. 
Thanks!

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 
> 2018-05-22 at 7.35.36 PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3275) [docs] Update AG_Install.twiki with Access Control List documentation

2018-06-06 Thread Peter Cseh (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503242#comment-16503242
 ] 

Peter Cseh commented on OOZIE-3275:
---

I don't understand what does "system property" means in the context of a HTTP 
submission.

[~orova], can you add suggestions on how to make changes from a user standpoint?

> [docs] Update AG_Install.twiki with Access Control List documentation
> -
>
> Key: OOZIE-3275
> URL: https://issues.apache.org/jira/browse/OOZIE-3275
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3275.001.patch
>
>
> It's hard to find a detailed description about ACL based authorization setup. 
> Let's extend {{AG_Install.twiki}} and have some.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503239#comment-16503239
 ] 

Hadoop QA commented on OOZIE-1393:
--


Testing JIRA OOZIE-1393

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:red}-1{color} the patch contains 1 line(s) longer than 132 
characters
.{color:green}+1{color} the patch 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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(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 [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {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/distcp].
. {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/streaming].
. {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/oozie].
. {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/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {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 [docs].
. {color:green}+1{color} There are no new bugs found in [server].
{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: 2146
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
.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: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/611/



> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 
> 2018-05-22 at 7.35.36 PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExec

Failed: OOZIE-1393 PreCommit Build #611

2018-06-06 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-1393
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/611/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.72 MB...]
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2363 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-1393

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 contains 1 line(s) longer than 132 characters
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(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 [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +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 [docs].
 +1 There are no new bugs found in [server].
+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: 2146
Tests failed at first run:
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-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/611/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  32080 0  100  3208  0   3858 --:--:-- --:--:-- --:--:--  
3855{"self":"https://issues.apache.org/jira/rest/api/2/issue/12649490/comment/16503239","id":"16503239","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=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active

[jira] [Commented] (OOZIE-2791) ShareLib installation may fail on busy Hadoop clusters

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503230#comment-16503230
 ] 

Hadoop QA commented on OOZIE-2791:
--

PreCommit-OOZIE-Build started


> ShareLib installation may fail on busy Hadoop clusters
> --
>
> Key: OOZIE-2791
> URL: https://issues.apache.org/jira/browse/OOZIE-2791
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2791-003.patch, OOZIE-2791-004.patch, 
> OOZIE-2791-005.patch, OOZIE-2791-006.patch, OOZIE-2791-007.patch, 
> OOZIE-2791-01.patch, OOZIE-2791-02.patch
>
>
> On a busy Hadoop cluster it can happen that users cannot install properly  
> Oozie ShareLib.
> Example on a Hadoop 2.4.0 pseudo cluster sharelib installion with a  
> concurrency number set high (to simulate a busy cluster):
> {code}
> oozie-setup.sh sharelib create -fs hdfs://localhost:9000 -locallib 
> oozie-sharelib-*.tar.gz -concurrency 150
> {code}
> You can see a lot of errors (failed copy tasks) on the output:
> {code}
> Running 464 copy tasks on 150 threads
> Error: Copy task failed with exception
> Stack trace for the error was (for debug purposes):
> --
> org.apache.hadoop.ipc.RemoteException(java.io.IOException): File 
> /user/asasvari/share/lib/lib_20170207105926/distcp/hadoop-distcp-2.4.0.jar 
> could only be replicated to 0 nodes instead of minReplication (=1).  There 
> are 1 datanode(s) running and no node(s) are excluded in this operation.
>   at 
> org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget(BlockManager.java:1430)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2684)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:584)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:440)
>   at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585)
>   at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2013)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2009)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
>   at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2007)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1410)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1363)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:206)
>   at com.sun.proxy.$Proxy9.addBlock(Unknown Source)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:190)
>   at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:103)
>   at com.sun.proxy.$Proxy9.addBlock(Unknown Source)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:361)
>   at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(DFSOutputStream.java:1439)
>   at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1261)
>   at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:525)
> --
> ...
> {code}
> You can see file is created but it's size is 0.
> {code}
> -rw-r--r--   3 asasvari supergroup  0 2017-02-07 10:59 
> share/lib/lib_20170207105926/distcp/hadoop-distcp-2.4.0.jar
> {code}
> This behaviour is clearly wrong. 
> In case of such an exception, we should retry copying or rollback changes. We 
> should also consider throttling HDFS requests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-2791) ShareLib installation may fail on busy Hadoop clusters

2018-06-06 Thread Julia Kinga Marton (JIRA)



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

Julia Kinga Marton updated OOZIE-2791:
--
Attachment: OOZIE-2791-007.patch

> ShareLib installation may fail on busy Hadoop clusters
> --
>
> Key: OOZIE-2791
> URL: https://issues.apache.org/jira/browse/OOZIE-2791
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2791-003.patch, OOZIE-2791-004.patch, 
> OOZIE-2791-005.patch, OOZIE-2791-006.patch, OOZIE-2791-007.patch, 
> OOZIE-2791-01.patch, OOZIE-2791-02.patch
>
>
> On a busy Hadoop cluster it can happen that users cannot install properly  
> Oozie ShareLib.
> Example on a Hadoop 2.4.0 pseudo cluster sharelib installion with a  
> concurrency number set high (to simulate a busy cluster):
> {code}
> oozie-setup.sh sharelib create -fs hdfs://localhost:9000 -locallib 
> oozie-sharelib-*.tar.gz -concurrency 150
> {code}
> You can see a lot of errors (failed copy tasks) on the output:
> {code}
> Running 464 copy tasks on 150 threads
> Error: Copy task failed with exception
> Stack trace for the error was (for debug purposes):
> --
> org.apache.hadoop.ipc.RemoteException(java.io.IOException): File 
> /user/asasvari/share/lib/lib_20170207105926/distcp/hadoop-distcp-2.4.0.jar 
> could only be replicated to 0 nodes instead of minReplication (=1).  There 
> are 1 datanode(s) running and no node(s) are excluded in this operation.
>   at 
> org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget(BlockManager.java:1430)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2684)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:584)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:440)
>   at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585)
>   at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2013)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2009)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
>   at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2007)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1410)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1363)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:206)
>   at com.sun.proxy.$Proxy9.addBlock(Unknown Source)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:190)
>   at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:103)
>   at com.sun.proxy.$Proxy9.addBlock(Unknown Source)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:361)
>   at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(DFSOutputStream.java:1439)
>   at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1261)
>   at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:525)
> --
> ...
> {code}
> You can see file is created but it's size is 0.
> {code}
> -rw-r--r--   3 asasvari supergroup  0 2017-02-07 10:59 
> share/lib/lib_20170207105926/distcp/hadoop-distcp-2.4.0.jar
> {code}
> This behaviour is clearly wrong. 
> In case of such an exception, we should retry copying or rollback changes. We 
> should also consider throttling HDFS requests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 66930: OOZIE-2791 ShareLib installation may fail on busy Hadoop clusters

2018-06-06 Thread Kinga Marton via Review Board


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

(Updated June 6, 2018, 12:34 p.m.)


Review request for oozie, András Piros and Peter Cseh.


Changes
---

review fix


Repository: oozie-git


Description
---

On a busy Hadoop cluster it can happen that users cannot install properly 
Oozie ShareLib.


Diffs (updated)
-

  tools/src/main/java/org/apache/oozie/tools/OozieSharelibCLI.java dce1c559 
  tools/src/test/java/org/apache/oozie/tools/TestBlockSizeCalculator.java 
PRE-CREATION 
  tools/src/test/java/org/apache/oozie/tools/TestConcurrentCopyFromLocal.java 
PRE-CREATION 
  tools/src/test/java/org/apache/oozie/tools/TestCopyTaskCallable.java 
PRE-CREATION 
  tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLI.java ccad273b 
  tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLIHelper.java 
PRE-CREATION 


Diff: https://reviews.apache.org/r/66930/diff/5/

Changes: https://reviews.apache.org/r/66930/diff/4-5/


Testing
---

Tested manually


Thanks,

Kinga Marton

[jira] [Commented] (OOZIE-3260) [sla] Remove stale item above max retries on JPA related errors from in-memory SLA map

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503170#comment-16503170
 ] 

Hadoop QA commented on OOZIE-3260:
--


Testing JIRA OOZIE-3260

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 adds/modifies 2 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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(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 [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {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/distcp].
. {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/streaming].
. {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/oozie].
. {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/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {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 [docs].
. {color:green}+1{color} There are no new bugs found in [server].
{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: 2148
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
.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 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/610/



> [sla] Remove stale item above max retries on JPA related errors from 
> in-memory SLA map
> --
>
> Key: OOZIE-3260
> URL: https://issues.apache.org/jira/browse/OOZIE-3260
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, core, workflow
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3260.001.patch, OOZIE-3260.002.patch
>
>
> Despite having implemented OOZIE-3134, there are still cases where 
> {{SLACalculatorMemory#slaMap}} and database contents still get out of sync. 
> Some possibilities including but not limited to:
>  * database contents of {{SLA_SUMMARY}} table have been purged manually from 
> DB
>  * no corresponding {{WF_JOBS}} or {{COORD_JOBS}} entries exist anymore in DB
>  * the {{WF_JOBS}} or {{COORD_JOBS}} instance that is being tracked by the 
> {{SLACalcStatus}} instances inside {{SLACalculatorMemory#slaMap}} is not yet 
> persisted to database when the SLA entry is already processed by 
> {{SLACalculatorMemory.HistoryPurgeWorker}}. Depending on e.g. how many 
> coordinator actions are being materialized, it can very well happen that 
> {{SLACalcStatus}} entries inserted to the in-memory map will be processed 
> before their corresponding {{CoordActionBean}} entries are yet to be 
> persisted to database
> In those rare cases, we see {{JPAExecutorException}} instances like:
> {noformat}
> 2017-10-09 17:00:18,185 DEBUG openjpa

Success: OOZIE-3260 PreCommit Build #610

2018-06-06 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-3260
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/610/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.72 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2365 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3260

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 line longer than 132
+1 the patch adds/modifies 2 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(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 [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +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 [docs].
 +1 There are no new bugs found in [server].
+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: 2148
Tests failed at first run:
TestCoordActionsKillXCommand#testActionKillCommandDate
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/610/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  31850 0  100  3185  0   3726 --:--:-- --:--:-- --:--:--  
3725{"self":"https://issues.apache.org/jira/rest/api/2/issue/13162142/comment/16503170","id":"16503170","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=hadoopqa&ava

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503147#comment-16503147
 ] 

Denes Bodo commented on OOZIE-1393:
---

[~andras.piros] thanks for the reapply, it worked.

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 
> 2018-05-22 at 7.35.36 PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3275) [docs] Update AG_Install.twiki with Access Control List documentation

2018-06-06 Thread Andras Piros (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503129#comment-16503129
 ] 

Andras Piros commented on OOZIE-3275:
-

[~gezapeti] can you please review? Thanks!

> [docs] Update AG_Install.twiki with Access Control List documentation
> -
>
> Key: OOZIE-3275
> URL: https://issues.apache.org/jira/browse/OOZIE-3275
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3275.001.patch
>
>
> It's hard to find a detailed description about ACL based authorization setup. 
> Let's extend {{AG_Install.twiki}} and have some.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Andras Piros (JIRA)



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

Andras Piros updated OOZIE-1393:

Attachment: OOZIE-1393-004.patch

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 
> 2018-05-22 at 7.35.36 PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Andras Piros (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503127#comment-16503127
 ] 

Andras Piros commented on OOZIE-1393:
-

[~dionusos] this is strange, your patch could be applied locally. Re-uploading, 
maybe this helps.

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 
> 2018-05-22 at 7.35.36 PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503126#comment-16503126
 ] 

Hadoop QA commented on OOZIE-1393:
--

PreCommit-OOZIE-Build started


> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 
> 2018-05-22 at 7.35.36 PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3275) [docs] Update AG_Install.twiki with Access Control List documentation

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503125#comment-16503125
 ] 

Hadoop QA commented on OOZIE-3275:
--


Testing JIRA OOZIE-3275

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 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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(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 [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {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 [docs].
. {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/pig].
. {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/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/sqoop].
. {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/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{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: 2146
{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/PreCommit-OOZIE-Build/609/



> [docs] Update AG_Install.twiki with Access Control List documentation
> -
>
> Key: OOZIE-3275
> URL: https://issues.apache.org/jira/browse/OOZIE-3275
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3275.001.patch
>
>
> It's hard to find a detailed description about ACL based authorization setup. 
> Let's extend {{AG_Install.twiki}} and have some.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3275 PreCommit Build #609

2018-06-06 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-3275
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/609/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/streaming].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2366 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3275

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 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
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(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 [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +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 [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +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/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+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: 2146
+1 DISTRO
+1 distro tarball builds with the patch 


-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/609/

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 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13164405/comment/16503125","id":"16503125","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/usera

[jira] [Commented] (OOZIE-3260) [sla] Remove stale item above max retries on JPA related errors from in-memory SLA map

2018-06-06 Thread Andras Piros (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503095#comment-16503095
 ] 

Andras Piros commented on OOZIE-3260:
-

Thanks [~gezapeti] for the review!

Unfortunately there is no such guarantee, this change only removes stale 
{{SLACalculatorMemory#slaMap}} entries after a preconfigured number of retries.

To have such guarantees, we have to:
* [*remove deprecated {{SLAEventBean}}*|OOZIE-2364] along w/ any logic in favor 
of {{SLARegistrationBean}} and {{SLASummaryBean}}. 
* [*refactor {{SLACalculatorMemory}}*|OOZIE-3276]:
** to have {{slaMap}} be consistent w/ basic workflow, coordinator, or bundle 
entries anytime, meaning in case these haven't been persisted yet or have 
already been deleted, no SLA update should be performed
** rework also the public interfaces of {{SLACalculator}} not to have 
{{slaMap}} or {{historySet}} exposed to outside world
** modify {{SLACalculatorMemory}} to have {{slaMap}} and {{historySet}} updates 
in parallel

> [sla] Remove stale item above max retries on JPA related errors from 
> in-memory SLA map
> --
>
> Key: OOZIE-3260
> URL: https://issues.apache.org/jira/browse/OOZIE-3260
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, core, workflow
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3260.001.patch, OOZIE-3260.002.patch
>
>
> Despite having implemented OOZIE-3134, there are still cases where 
> {{SLACalculatorMemory#slaMap}} and database contents still get out of sync. 
> Some possibilities including but not limited to:
>  * database contents of {{SLA_SUMMARY}} table have been purged manually from 
> DB
>  * no corresponding {{WF_JOBS}} or {{COORD_JOBS}} entries exist anymore in DB
>  * the {{WF_JOBS}} or {{COORD_JOBS}} instance that is being tracked by the 
> {{SLACalcStatus}} instances inside {{SLACalculatorMemory#slaMap}} is not yet 
> persisted to database when the SLA entry is already processed by 
> {{SLACalculatorMemory.HistoryPurgeWorker}}. Depending on e.g. how many 
> coordinator actions are being materialized, it can very well happen that 
> {{SLACalcStatus}} entries inserted to the in-memory map will be processed 
> before their corresponding {{CoordActionBean}} entries are yet to be 
> persisted to database
> In those rare cases, we see {{JPAExecutorException}} instances like:
> {noformat}
> 2017-10-09 17:00:18,185 DEBUG openjpa.jdbc.SQL: SERVER[HOST]  conn 1584126245> [0 ms] spent
> 2017-10-09 17:00:18,185 ERROR org.apache.oozie.sla.SLACalculatorMemory: 
> SERVER[tplhc01c001.iuser.iroot.adidom.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[438-170916014916144-oozie-oozi-C@556] ACTION[-] Exception in SLA 
> processing for job [438-170916014916144-oozie-oozi-C@556]
> org.apache.oozie.executor.jpa.JPAExecutorException: E0604: Job does not exist 
> [select w.eventProcessed from SLASummaryBean w where w.jobId = :id]
> at 
> org.apache.oozie.executor.jpa.SLASummaryQueryExecutor.getSingleValue(SLASummaryQueryExecutor.java:161)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateJobSla(SLACalculatorMemory.java:480)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateAllSlaStatus(SLACalculatorMemory.java:601)
> {noformat}
> Solution here is to track the number of times the {{SLACalcStatus}} entry has 
> not been processed successfully, and when a preconfigured 
> {{oozie.sla.service.SLAService.maximum.retry.count}} is reached, remove any 
> {{SLACalculatorMemory#slaMap}} entries that are causing those 
> {{JPAExecutorException}} instances, to not cause huge logfiles. The items to 
> be logged don't exist, anyways.
> It's still possible that multiple {{CoordActionBean}} instances being 
> inserted won't have {{SLACalcStatus}} entries inside 
> {{SLACalculatorMemory#slaMap}} by the time written to database, and thus, no 
> SLA will be tracked. In those rare cases, preconfigured maximum retry count 
> can be extended.
> Note that current implementation of 
> [*{{SLACalculatorMemory#updateJobSla()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java#L238-L242]
>  already removes the stale {{SLACalcStatus}} entry. The new functionality 
> here is to introduce {{SLACalcStatus#retryCount}}, and extend the 
> {{JPAExecutorException}} {{ErrorCode}}s of interest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3276) Refactor SLACalculatorMemory

2018-06-06 Thread Andras Piros (JIRA)

Andras Piros created OOZIE-3276:
---

 Summary: Refactor SLACalculatorMemory
 Key: OOZIE-3276
 URL: https://issues.apache.org/jira/browse/OOZIE-3276
 Project: Oozie
  Issue Type: Improvement
  Components: core
Affects Versions: 5.0.0
Reporter: Andras Piros


There are times when {{SLACalculatorMemory#slaMap}}, or 
{{SLACalculatorMemory#historySet}} contains stale information causing weird 
{{Exception}}s like the ones handled by OOZIE-3260.

Let's refactor {{SLACalculatorMemory}}:
* to have {{slaMap}} be consistent w/ basic workflow, coordinator, or bundle 
entries anytime, meaning in case these haven't been persisted yet or have 
already been deleted, no SLA update should be performed
* rework also the public interfaces of {{SLACalculator}} not to have {{slaMap}} 
or {{historySet}} exposed to outside world
* modify {{SLACalculatorMemory}} to have {{slaMap}} and {{historySet}} updates 
in parallel



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3260) [sla] Remove stale item above max retries on JPA related errors from in-memory SLA map

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503074#comment-16503074
 ] 

Hadoop QA commented on OOZIE-3260:
--

PreCommit-OOZIE-Build started


> [sla] Remove stale item above max retries on JPA related errors from 
> in-memory SLA map
> --
>
> Key: OOZIE-3260
> URL: https://issues.apache.org/jira/browse/OOZIE-3260
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, core, workflow
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3260.001.patch, OOZIE-3260.002.patch
>
>
> Despite having implemented OOZIE-3134, there are still cases where 
> {{SLACalculatorMemory#slaMap}} and database contents still get out of sync. 
> Some possibilities including but not limited to:
>  * database contents of {{SLA_SUMMARY}} table have been purged manually from 
> DB
>  * no corresponding {{WF_JOBS}} or {{COORD_JOBS}} entries exist anymore in DB
>  * the {{WF_JOBS}} or {{COORD_JOBS}} instance that is being tracked by the 
> {{SLACalcStatus}} instances inside {{SLACalculatorMemory#slaMap}} is not yet 
> persisted to database when the SLA entry is already processed by 
> {{SLACalculatorMemory.HistoryPurgeWorker}}. Depending on e.g. how many 
> coordinator actions are being materialized, it can very well happen that 
> {{SLACalcStatus}} entries inserted to the in-memory map will be processed 
> before their corresponding {{CoordActionBean}} entries are yet to be 
> persisted to database
> In those rare cases, we see {{JPAExecutorException}} instances like:
> {noformat}
> 2017-10-09 17:00:18,185 DEBUG openjpa.jdbc.SQL: SERVER[HOST]  conn 1584126245> [0 ms] spent
> 2017-10-09 17:00:18,185 ERROR org.apache.oozie.sla.SLACalculatorMemory: 
> SERVER[tplhc01c001.iuser.iroot.adidom.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[438-170916014916144-oozie-oozi-C@556] ACTION[-] Exception in SLA 
> processing for job [438-170916014916144-oozie-oozi-C@556]
> org.apache.oozie.executor.jpa.JPAExecutorException: E0604: Job does not exist 
> [select w.eventProcessed from SLASummaryBean w where w.jobId = :id]
> at 
> org.apache.oozie.executor.jpa.SLASummaryQueryExecutor.getSingleValue(SLASummaryQueryExecutor.java:161)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateJobSla(SLACalculatorMemory.java:480)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateAllSlaStatus(SLACalculatorMemory.java:601)
> {noformat}
> Solution here is to track the number of times the {{SLACalcStatus}} entry has 
> not been processed successfully, and when a preconfigured 
> {{oozie.sla.service.SLAService.maximum.retry.count}} is reached, remove any 
> {{SLACalculatorMemory#slaMap}} entries that are causing those 
> {{JPAExecutorException}} instances, to not cause huge logfiles. The items to 
> be logged don't exist, anyways.
> It's still possible that multiple {{CoordActionBean}} instances being 
> inserted won't have {{SLACalcStatus}} entries inside 
> {{SLACalculatorMemory#slaMap}} by the time written to database, and thus, no 
> SLA will be tracked. In those rare cases, preconfigured maximum retry count 
> can be extended.
> Note that current implementation of 
> [*{{SLACalculatorMemory#updateJobSla()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java#L238-L242]
>  already removes the stale {{SLACalcStatus}} entry. The new functionality 
> here is to introduce {{SLACalcStatus#retryCount}}, and extend the 
> {{JPAExecutorException}} {{ErrorCode}}s of interest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3260) [sla] Remove stale item above max retries on JPA related errors from in-memory SLA map

2018-06-06 Thread Andras Piros (JIRA)



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

Andras Piros updated OOZIE-3260:

Attachment: OOZIE-3260.002.patch

> [sla] Remove stale item above max retries on JPA related errors from 
> in-memory SLA map
> --
>
> Key: OOZIE-3260
> URL: https://issues.apache.org/jira/browse/OOZIE-3260
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, core, workflow
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3260.001.patch, OOZIE-3260.002.patch
>
>
> Despite having implemented OOZIE-3134, there are still cases where 
> {{SLACalculatorMemory#slaMap}} and database contents still get out of sync. 
> Some possibilities including but not limited to:
>  * database contents of {{SLA_SUMMARY}} table have been purged manually from 
> DB
>  * no corresponding {{WF_JOBS}} or {{COORD_JOBS}} entries exist anymore in DB
>  * the {{WF_JOBS}} or {{COORD_JOBS}} instance that is being tracked by the 
> {{SLACalcStatus}} instances inside {{SLACalculatorMemory#slaMap}} is not yet 
> persisted to database when the SLA entry is already processed by 
> {{SLACalculatorMemory.HistoryPurgeWorker}}. Depending on e.g. how many 
> coordinator actions are being materialized, it can very well happen that 
> {{SLACalcStatus}} entries inserted to the in-memory map will be processed 
> before their corresponding {{CoordActionBean}} entries are yet to be 
> persisted to database
> In those rare cases, we see {{JPAExecutorException}} instances like:
> {noformat}
> 2017-10-09 17:00:18,185 DEBUG openjpa.jdbc.SQL: SERVER[HOST]  conn 1584126245> [0 ms] spent
> 2017-10-09 17:00:18,185 ERROR org.apache.oozie.sla.SLACalculatorMemory: 
> SERVER[tplhc01c001.iuser.iroot.adidom.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[438-170916014916144-oozie-oozi-C@556] ACTION[-] Exception in SLA 
> processing for job [438-170916014916144-oozie-oozi-C@556]
> org.apache.oozie.executor.jpa.JPAExecutorException: E0604: Job does not exist 
> [select w.eventProcessed from SLASummaryBean w where w.jobId = :id]
> at 
> org.apache.oozie.executor.jpa.SLASummaryQueryExecutor.getSingleValue(SLASummaryQueryExecutor.java:161)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateJobSla(SLACalculatorMemory.java:480)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateAllSlaStatus(SLACalculatorMemory.java:601)
> {noformat}
> Solution here is to track the number of times the {{SLACalcStatus}} entry has 
> not been processed successfully, and when a preconfigured 
> {{oozie.sla.service.SLAService.maximum.retry.count}} is reached, remove any 
> {{SLACalculatorMemory#slaMap}} entries that are causing those 
> {{JPAExecutorException}} instances, to not cause huge logfiles. The items to 
> be logged don't exist, anyways.
> It's still possible that multiple {{CoordActionBean}} instances being 
> inserted won't have {{SLACalcStatus}} entries inside 
> {{SLACalculatorMemory#slaMap}} by the time written to database, and thus, no 
> SLA will be tracked. In those rare cases, preconfigured maximum retry count 
> can be extended.
> Note that current implementation of 
> [*{{SLACalculatorMemory#updateJobSla()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java#L238-L242]
>  already removes the stale {{SLACalcStatus}} entry. The new functionality 
> here is to introduce {{SLACalcStatus#retryCount}}, and extend the 
> {{JPAExecutorException}} {{ErrorCode}}s of interest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503039#comment-16503039
 ] 

Denes Bodo edited comment on OOZIE-1393 at 6/6/18 9:35 AM:
---

[~andras.piros], this is interesting. This commit (same as on review board) is 
on 
{code}
commit 2fd0b66b5eb4edc1256a630da8fb37e7c4565800
Author: Andras Piros 
Date:   Mon Jun 4 16:16:05 2018 +0200

OOZIE-3156 Retry SSH action check when cannot connect to remote host 
(txsing via andras.piros)
{code}
remotes are:
{code}
origin  g...@github.com:apache/oozie.git (fetch)
origin  g...@github.com:apache/oozie.git (push)
{code}

I checked the logs: Jenkins checks out the 2fd0b66... commit at first. Then no 
details:
{code}
Applying patch

fatal: unrecognized input
fatal: unrecognized input
Patch failed to apply to head of branch
{code}
Cloning Oozie repo again, downloading the patch and applying is fluent locally. 
Do you have any idea?


was (Author: dionusos):
[~andras.piros], this is interesting. This commit (same as on review board) is 
on 
{code}
commit 2fd0b66b5eb4edc1256a630da8fb37e7c4565800
Author: Andras Piros 
Date:   Mon Jun 4 16:16:05 2018 +0200

OOZIE-3156 Retry SSH action check when cannot connect to remote host 
(txsing via andras.piros)
{code}
remotes are:
{code}
origin  g...@github.com:apache/oozie.git (fetch)
origin  g...@github.com:apache/oozie.git (push)
{code}

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 
> PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("ma

[jira] [Commented] (OOZIE-3275) [docs] Update AG_Install.twiki with Access Control List documentation

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503050#comment-16503050
 ] 

Hadoop QA commented on OOZIE-3275:
--

PreCommit-OOZIE-Build started


> [docs] Update AG_Install.twiki with Access Control List documentation
> -
>
> Key: OOZIE-3275
> URL: https://issues.apache.org/jira/browse/OOZIE-3275
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3275.001.patch
>
>
> It's hard to find a detailed description about ACL based authorization setup. 
> Let's extend {{AG_Install.twiki}} and have some.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3275) [docs] Update AG_Install.twiki with Access Control List documentation

2018-06-06 Thread Andras Piros (JIRA)



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

Andras Piros updated OOZIE-3275:

Attachment: OOZIE-3275.001.patch

> [docs] Update AG_Install.twiki with Access Control List documentation
> -
>
> Key: OOZIE-3275
> URL: https://issues.apache.org/jira/browse/OOZIE-3275
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3275.001.patch
>
>
> It's hard to find a detailed description about ACL based authorization setup. 
> Let's extend {{AG_Install.twiki}} and have some.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3275) [docs] Update AG_Install.twiki with Access Control List documentation

2018-06-06 Thread Andras Piros (JIRA)

Andras Piros created OOZIE-3275:
---

 Summary: [docs] Update AG_Install.twiki with Access Control List 
documentation
 Key: OOZIE-3275
 URL: https://issues.apache.org/jira/browse/OOZIE-3275
 Project: Oozie
  Issue Type: Improvement
  Components: docs
Affects Versions: 5.0.0
Reporter: Andras Piros
Assignee: Andras Piros


It's hard to find a detailed description about ACL based authorization setup. 
Let's extend {{AG_Install.twiki}} and have some.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503039#comment-16503039
 ] 

Denes Bodo commented on OOZIE-1393:
---

[~andras.piros], this is interesting. This commit (same as on review board) is 
on 
{code}
commit 2fd0b66b5eb4edc1256a630da8fb37e7c4565800
Author: Andras Piros 
Date:   Mon Jun 4 16:16:05 2018 +0200

OOZIE-3156 Retry SSH action check when cannot connect to remote host 
(txsing via andras.piros)
{code}
remotes are:
{code}
origin  g...@github.com:apache/oozie.git (fetch)
origin  g...@github.com:apache/oozie.git (push)
{code}

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 
> PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Andras Piros (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503031#comment-16503031
 ] 

Andras Piros commented on OOZIE-1393:
-

Thanks [~dionusos] for the contribution! Can you please upload to JIRA and 
ReviewBoard an updated patch that can be applied to current {{master}}? Thanks!

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 
> PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Denes Bodo (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503014#comment-16503014
 ] 

Denes Bodo commented on OOZIE-3274:
---

[~gezapeti] sure, we will do deeper tests. A quick check has done without slf4j 
jars and seems promising.

> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Peter Cseh (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503013#comment-16503013
 ] 

Peter Cseh commented on OOZIE-3274:
---

[~bpgergo], please rebase the patch

> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503004#comment-16503004
 ] 

Hadoop QA commented on OOZIE-3274:
--


Testing JIRA OOZIE-3274

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch




> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3274 PreCommit Build #608

2018-06-06 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-3274
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/608/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 767.81 KB...]
metrics-core


org.slf4j
slf4j-api





io.dropwizard.metrics
metrics-graphite


org.slf4j
slf4j-api






error: patch failed: core/pom.xml:61
error: core/pom.xml: patch does not apply
Checking patch examples/pom.xml...
Hunk #1 succeeded at 91 (offset 1 line).
error: while searching for:
guava


org.slf4j
jul-to-slf4j


org.slf4j
jcl-over-slf4j


com.fasterxml.jackson.core
jackson-databind


error: patch failed: examples/pom.xml:134
error: examples/pom.xml: patch does not apply
Checking patch hadooplibs/hadoop-auth-2/pom.xml...
error: hadooplibs/hadoop-auth-2/pom.xml: No such file or directory
Checking patch pom.xml...
error: while searching for:
persistence-api
1.0



org.slf4j
slf4j-simple
1.6.6



org.codehaus.jackson
jackson-mapper-asl

error: patch failed: pom.xml:352
error: pom.xml: patch does not apply
Checking patch sharelib/hcatalog/pom.xml...
Hunk #2 succeeded at 326 (offset -13 lines).
Checking patch sharelib/sqoop/pom.xml...
Hunk #1 succeeded at 77 (offset 1 line).
error: while searching for:
org.codehaus.jackson
jackson-mapper-asl


org.slf4j
slf4j-api





error: patch failed: sharelib/sqoop/pom.xml:179
error: sharelib/sqoop/pom.xml: patch does not apply
Patch failed to apply to head of branch

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100   1990 0  100   199  0253 --:--:-- --:--:-- --:--:--   
253100  17740  1575  100   199   2004253 --:--:-- --:--:-- --:--:--  
2003
{"self":"https://issues.apache.org/jira/rest/api/2/issue/13164151/comment/16503004","id":"16503004","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=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3274\n\nCleaning local git 
workspace\n\n\n\n{color:red}-1{color} Patch failed 
to apply to head of 
branch\n\n\n","updateAuthor":{"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=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 
QA","active":true,"timeZone":"Etc/UTC"},"created":"2018-06-06T08:45:20.249+","updated":"2018-06-06T08:45:20.249+"}
test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3274
Archiving artifacts
[Fast Archiver] Compressed 891.10 KB of artifacts by 82.6% relative to #606
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502996#comment-16502996
 ] 

Hadoop QA commented on OOZIE-3274:
--

PreCommit-OOZIE-Build started


> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OOZIE-3274) Remove slf4j

2018-06-06 Thread Peter Cseh (JIRA)



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

Peter Cseh reassigned OOZIE-3274:
-

Assignee: Péter Gergő Barna

> Remove slf4j
> 
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.patch
>
>
> Remove all slf4j jars from Oozie. 
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems 
> that all kinds of hadoop2 jobs are working fine.  Any comments are welcomed, 
> I would appreciate a response from the community on this. 
>  
> I know about this issue, which introduced slf4j as a dependency, I am not 
> sure if this is relevant any more. 
> https://issues.apache.org/jira/browse/OOZIE-1004
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3218) Oozie Sqoop action with command splits the select clause into multiple parts due to delimiter being space

2018-06-06 Thread Peter Cseh (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502972#comment-16502972
 ] 

Peter Cseh commented on OOZIE-3218:
---

This looks like a duplicate of OOZIE-2949. I don't really mind which one is 
committed as far as it fixes the issue.

Thanks for the contribution [~mbalakrishnan], I have left some comments on the 
reviewBorad, please fix them.

> Oozie Sqoop action with command splits the select clause into multiple parts 
> due to delimiter being space
> -
>
> Key: OOZIE-3218
> URL: https://issues.apache.org/jira/browse/OOZIE-3218
> Project: Oozie
>  Issue Type: Bug
>  Components: action, workflow
>Affects Versions: 3.3.2, 4.1.0, 4.2.0, 4.3.0, 5.0.0
> Environment: Hortonworks Hadoop HDP-2.6.4.x release 
>  oozie admin -version: Oozie server build version: 4.2.0.2.6.4.0-91
>Reporter: Mahesh Balakrishnan
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-3218-2.patch, OOZIE-3218-3.patch, OOZIE-3218.patch
>
>
> When running a Oozie Sqoop action which has command with {{--query}} in place 
> the query is split into multiple parts causing {{"Unrecognized argument:"}} 
> and in-turn fails.
> {code:xml}
> 
> ${resourceManager}
> ${nameNode}
> import --verbose --connect jdbc:mysql://test.openstacklocal/db 
> --query select * from abc where $CONDITIONS --username test --password test 
> --driver com.mysql.jdbc.Driver -m 1 
> 
> 
> {code}
>  
> Oozie Launcher logs:
> {noformat}
>  Sqoop command arguments :
>  import
>  --verbose
>  --connect
>  jdbc:mysql://test.openstacklocal/db
>  --query
>  "select
>  *
>  from
>  abc
>  where
>  $CONDITIONS"
>  --username
>  hive
>  --password
>  
>  --driver
>  com.mysql.jdbc.Driver
>  -m
>  1
>  Fetching child yarn jobs
>  tag id : oozie-a1bbe03a0983b9e822d12ae7bb269ee3
>  2791 [main] INFO org.apache.hadoop.yarn.client.RMProxy - Connecting to 
> ResourceManager at hdp263-3.openstacklocal/172.26.105.248:8050
>  Child yarn jobs are found - 
>  =
> >>> Invoking Sqoop command line now >>>
> 3172 [main] WARN org.apache.sqoop.tool.SqoopTool - $SQOOP_CONF_DIR has not 
> been set in the environment. Cannot check for additional configuration.
>  3172 [main] WARN org.apache.sqoop.tool.SqoopTool - $SQOOP_CONF_DIR has not 
> been set in the environment. Cannot check for additional configuration.
>  3218 [main] INFO org.apache.sqoop.Sqoop - Running Sqoop version: 
> 1.4.6.2.6.4.0-91
>  3218 [main] INFO org.apache.sqoop.Sqoop - Running Sqoop version: 
> 1.4.6.2.6.4.0-91
>  3287 [main] DEBUG org.apache.sqoop.tool.BaseSqoopTool - Enabled debug 
> logging.
>  3287 [main] DEBUG org.apache.sqoop.tool.BaseSqoopTool - Enabled debug 
> logging.
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Error parsing 
> arguments for import:
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Error parsing 
> arguments for import:
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: *
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: *
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: from
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: from
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: abc
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: abc
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: where
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: where
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: $CONDITIONS"
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: $CONDITIONS"
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: --username
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: --username
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: abc
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: abc
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: --password
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: --password
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: abc
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: abc
>  3288 [main] ERROR org.apache.sqoop.tool.BaseSqoopTool - Unrecognized 
> argument: --driver
>

Re: Review Request 67314: Oozie Sqoop action with command splits the select clause into multiple parts due to delimiter being space

2018-06-06 Thread Peter Cseh via Review Board


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




core/src/main/java/org/apache/oozie/action/hadoop/SqoopActionExecutor.java
Lines 95 (patched)


Is "contains" strong enough here?
I can think of two scenarios when it might screw up the parsin:
1) a table name contains a "-" character
2) a query like "select * where price > -3 and price < 0



core/src/main/java/org/apache/oozie/action/hadoop/SqoopActionExecutor.java
Lines 98 (patched)


This changes behavior (for the better I thnik :)) Please update the 
documentation as well.



sharelib/sqoop/src/test/java/org/apache/oozie/action/hadoop/TestSqoopActionExecutor.java
Lines 50 (patched)


Please add a test case where this select is quoted


- Peter Cseh


On May 25, 2018, 7:37 a.m., Denes Bodo wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67314/
> ---
> 
> (Updated May 25, 2018, 7:37 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Bugs: OOZIE-3218
> https://issues.apache.org/jira/browse/OOZIE-3218
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> When running a Oozie Sqoop action which has command with --query in place the 
> query is split into multiple parts causing "Unrecognized argument:" and 
> in-turn fails.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/SqoopActionExecutor.java 
> 69d5e7e 
>   
> sharelib/sqoop/src/test/java/org/apache/oozie/action/hadoop/TestSqoopActionExecutor.java
>  edfe0c7 
> 
> 
> Diff: https://reviews.apache.org/r/67314/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Denes Bodo
> 
>

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502946#comment-16502946
 ] 

Hadoop QA commented on OOZIE-1393:
--


Testing JIRA OOZIE-1393

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch




> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 
> PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502945#comment-16502945
 ] 

Denes Bodo commented on OOZIE-1393:
---

Screenshot about twiki fix is attached. Also here is the review board link: 
https://reviews.apache.org/r/67473/

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 
> PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1393 PreCommit Build #607

2018-06-06 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-1393
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/607/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 761.71 KB...]
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/main/resources
[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] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/main/resources
[INFO] Copying 3 resources
[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] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target/test-classes
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Some input files use or override a deprecated API.
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  1.589 s]
[INFO] Apache Oozie Client  SUCCESS [ 16.028 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 11.032 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  5.947 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  4.599 s]
[INFO] Apache Oozie Core .. SUCCESS [01:14 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  6.969 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.921 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  7.645 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  8.085 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.570 s]
[INFO] Apache Oozie Examples .. SUCCESS [  7.827 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [  9.429 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.020 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.020 s]
[INFO] Apache Oozie WebApp  SUCCESS [  7.495 s]
[INFO] Apache Oozie Tools . SUCCESS [ 11.674 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.557 s]
[INFO] Apache Oozie Server  SUCCESS [  9.799 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.012 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.536 s]
[INFO] 
[INFO] BUILD SUCCESS
[

Review Request 67473: EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo


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

Review request for oozie.


Bugs: OOZIE-1393
https://issues.apache.org/jira/browse/OOZIE-1393


Repository: oozie-git


Description
---

Oozie cannot use Google's SMTP server due to missing email property.


Diffs
-

  core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java 
f93b7ad 
  core/src/main/java/org/apache/oozie/sla/listener/SLAEmailEventListener.java 
6e863df 
  core/src/main/resources/oozie-default.xml b828c80 
  core/src/test/java/org/apache/oozie/action/email/TestEmailActionExecutor.java 
354176e 
  docs/src/site/twiki/DG_EmailActionExtension.twiki 588a413 


Diff: https://reviews.apache.org/r/67473/diff/1/


Testing
---

Live cluster test by @Mahesh Balakrishnan.


Thanks,

Denes Bodo

[jira] [Commented] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/OOZIE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502938#comment-16502938
 ] 

Hadoop QA commented on OOZIE-1393:
--

PreCommit-OOZIE-Build started


> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 
> PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo (JIRA)



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

Denes Bodo updated OOZIE-1393:
--
Attachment: Screen Shot 2018-06-06 at 9.53.05 AM.png

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 
> PM.png, Screen Shot 2018-06-06 at 9.53.05 AM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-1393) EmailActionExecutor - allow setting additional properties for the SMTP client

2018-06-06 Thread Denes Bodo (JIRA)



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

Denes Bodo updated OOZIE-1393:
--
Attachment: OOZIE-1393-004.patch

> EmailActionExecutor - allow setting additional properties for the SMTP client
> -
>
> Key: OOZIE-1393
> URL: https://issues.apache.org/jira/browse/OOZIE-1393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Kiran Nagasubramanian
>Assignee: Mahesh Balakrishnan
>Priority: Major
> Attachments: OOZIE-1393-002.patch, OOZIE-1393-003.patch, 
> OOZIE-1393-004.patch, OOZIE-1393.patch, Screen Shot 2018-05-22 at 7.35.36 
> PM.png
>
>
> I was trying out email action executor. I've made sure that I'd set all the 
> properties on oozie-site.xml and in the workflow definition too. Please find 
> below the details I set, the stack trace and some of my findings. Any advice 
> on how to resolve this would be really appreciated.
> Details set:
> host = smtp.gmail.com
> port = 587
> both to and from are gmail addresses...
> oozie.email.smtp.auth = true
> oozie.email.smtp.username = same as From address(Gmail ID)
> oozie.email.smtp.password = 
> Stack trace:
> 130520210251024-oozie-Kira-W@email-node] Error starting action [email-node]. 
> ErrorType [ERROR], ErrorCode [EM007], Message [EM007: Encountered an error 
> while sending the email message over SMTP.]
> org.apache.oozie.action.ActionExecutorException: EM007: Encountered an error 
> while sending the email message over SMTP.
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:181)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.validateAndMail(EmailActionExecutor.java:110)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.start(EmailActionExecutor.java:70)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:211)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:59)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)
> Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a 
> STARTTLS command first. qh4sm1420786pac.8 - gsmtp
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
>   at javax.mail.Transport.send0(Transport.java:169)
>   at javax.mail.Transport.send(Transport.java:98)
>   at 
> org.apache.oozie.action.email.EmailActionExecutor.email(EmailActionExecutor.java:177)
>   ... 11 more
> Findings:
> I was able to develop a standalone class using javax.mail and send emails 
> successfully...The only difference I could see is I'm setting the following 
> property additionally in my standalone test:
> props.put("mail.smtp.starttls.enable", "true");
> If I dont set this property, my standalone example also fails with the same 
> exception as Oozie does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

64 matches

Mail list logo