[jira] [Created] (OOZIE-2818) Can't overwrite oozie.action.max.output.data on a per-workflow basis

[Peter Cseh (JIRA)]

Peter Cseh created OOZIE-2818:
-

 Summary: Can't overwrite oozie.action.max.output.data on a 
per-workflow basis
 Key: OOZIE-2818
 URL: https://issues.apache.org/jira/browse/OOZIE-2818
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Cseh


It's not possible to raise the limit of the output on a per-action basis. 
With the workflow:
{quote}



Action failed, error 
message\[$\{wf:errorMessage(wf:lastErrorNode())}]



$\{jobTracker}
$\{nameNode}


oozie.action.max.output.data
10


oozie.launcher.oozie.action.max.output.data
10


/user/admin/large_output.sh
  10
/user/admin/large_output.sh#large_output.sh
  






{quote}

In the localized files in the job.xml the value of this property gets 
overwritten:
{quote}
# cat 
/yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/job.xml
 |grep max.outp
oozie.launcher.oozie.action.max.output.data10programaticallyjob.xml
oozie.action.max.output.data2048programaticallyjob.xml
# cat 
/yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/action.xml
 |grep max.outp
oozie.launcher.oozie.action.max.output.data10programatically
oozie.action.max.output.data10programatically
{quote}


I could not find a reason for this behavior, so I think it's a bug.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2818) Can't overwrite oozie.action.max.output.data on a per-workflow basis

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2818:
--
Description: 
It's not possible to raise the limit of the output on a per-action basis. 
With the workflow:
{quote}



Action failed, error 
message\[$\{wf:errorMessage(wf:lastErrorNode())}]



$\{jobTracker}
$\{nameNode}


oozie.action.max.output.data
10


oozie.launcher.oozie.action.max.output.data
10


/user/admin/large_output.sh
  10
/user/admin/large_output.sh#large_output.sh
  






{quote}

In the localized files in the job.xml the value of this property gets 
overwritten:
{quote}
# cat 
/yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/job.xml
 |grep max.outp
oozie.launcher.oozie.action.max.output.data10programaticallyjob.xml
oozie.action.max.output.data2048programaticallyjob.xml
# cat 
/yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/action.xml
 |grep max.outp
oozie.launcher.oozie.action.max.output.data10programatically
oozie.action.max.output.data10programatically
{quote}


I could not find a reason for this behavior, so I think it's a bug.

The value is read from 
[ConfigurationService|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L175]
 and set in 
[createLauncherConf|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L986]
 in JavaActionExecutor. There could be a check to see if it's already set.

  was:
It's not possible to raise the limit of the output on a per-action basis. 
With the workflow:
{quote}



Action failed, error 
message\[$\{wf:errorMessage(wf:lastErrorNode())}]



$\{jobTracker}
$\{nameNode}


oozie.action.max.output.data
10


oozie.launcher.oozie.action.max.output.data
10


/user/admin/large_output.sh
  10
/user/admin/large_output.sh#large_output.sh
  






{quote}

In the localized files in the job.xml the value of this property gets 
overwritten:
{quote}
# cat 
/yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/job.xml
 |grep max.outp
oozie.launcher.oozie.action.max.output.data10programaticallyjob.xml
oozie.action.max.output.data2048programaticallyjob.xml
# cat 
/yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/action.xml
 |grep max.outp
oozie.launcher.oozie.action.max.output.data10programatically
oozie.action.max.output.data10programatically
{quote}


I could not find a reason for this behavior, so I think it's a bug.


> Can't overwrite oozie.action.max.output.data on a per-workflow basis
> 
>
> Key: OOZIE-2818
> URL: https://issues.apache.org/jira/browse/OOZIE-2818
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>
> It's not possible to raise the limit of the output on a per-action basis. 
> With the workflow:
> {quote}
> 
> 
> 
> Action failed, error 
> message\[$\{wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> $\{jobTracker}
> $\{nameNode}
> 
> 
> oozie.action.max.output.data
> 10
> 
> 
> oozie.launcher.oozie.action.max.output.data
> 10
> 
> 
> /user/admin/large_output.sh
>   10
> /user/admin/large_output.sh#large_output.sh
>   
> 
> 
> 
> 
> 
> 
> {quote}
> In the localized files in the job.xml the value of this property gets 
> overwritten:
> {quote}
> # cat 
> /yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/job.xml
>  |grep max.outp
> oozie.launcher.oozie.action.max.output.data10programaticallyjob.xml
> oozie.action.max.output.data2048programaticallyjob.xml
> # cat 
> /yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/action.xml
>  

[jira] [Commented] (OOZIE-2818) Can't overwrite oozie.action.max.output.data on a per-workflow basis

[Matyas Orhidi (JIRA)]

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

Matyas Orhidi commented on OOZIE-2818:
--

This did not work either:

{code}

  


oozie.action.max.output.data
2


oozie.launcher.oozie.action.max.output.data
2


  


Action failed, error 
message[${wf:errorMessage(wf:lastErrorNode())}]



${jobTracker}
${nameNode}
/user/admin/large_output.sh
  10
/user/admin/large_output.sh#large_output.sh
  






{code}

> Can't overwrite oozie.action.max.output.data on a per-workflow basis
> 
>
> Key: OOZIE-2818
> URL: https://issues.apache.org/jira/browse/OOZIE-2818
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>
> It's not possible to raise the limit of the output on a per-action basis. 
> With the workflow:
> {quote}
> 
> 
> 
> Action failed, error 
> message\[$\{wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> $\{jobTracker}
> $\{nameNode}
> 
> 
> oozie.action.max.output.data
> 10
> 
> 
> oozie.launcher.oozie.action.max.output.data
> 10
> 
> 
> /user/admin/large_output.sh
>   10
> /user/admin/large_output.sh#large_output.sh
>   
> 
> 
> 
> 
> 
> 
> {quote}
> In the localized files in the job.xml the value of this property gets 
> overwritten:
> {quote}
> # cat 
> /yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/job.xml
>  |grep max.outp
> oozie.launcher.oozie.action.max.output.data10programaticallyjob.xml
> oozie.action.max.output.data2048programaticallyjob.xml
> # cat 
> /yarn/nm/usercache/admin/appcache/application_1489145190857_0001/container_1489145190857_0001_01_02/action.xml
>  |grep max.outp
> oozie.launcher.oozie.action.max.output.data10programatically
> oozie.action.max.output.data10programatically
> {quote}
> I could not find a reason for this behavior, so I think it's a bug.
> The value is read from 
> [ConfigurationService|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L175]
>  and set in 
> [createLauncherConf|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L986]
>  in JavaActionExecutor. There could be a check to see if it's already set.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2819) Make Oozie REST API accept multibyte characters via client side xml

[Attila Sasvari (JIRA)]

Attila Sasvari created OOZIE-2819:
-

 Summary: Make Oozie REST API accept multibyte characters via 
client side xml
 Key: OOZIE-2819
 URL: https://issues.apache.org/jira/browse/OOZIE-2819
 Project: Oozie
  Issue Type: Bug
Reporter: Attila Sasvari


Submitted Pig action with client side xml failed via proxy submission when it 
contained multibyte characters.

{code}
curl -i  -X POST -d @/tmp/pig.xml -H 'Content-Type: application/XML; 
charset=UTF-8' 'http://'localhost':11000/oozie/v1/jobs?jobtype=pig&action=start'
{code}

Where
{code}
$ hdfs dfs -cat /tmp/encoding/input.txt
松
林檎
松
{code}

{code}
$ cat /tmp/pig.xml 


fs.default.name
hdfs://localhost:8020/


mapred.job.tracker
localhost:8032


user.name
hdfs


oozie.pig.script



oozie.pig.script.params.size
0


oozie.pig.script.options.size
0


oozie.libpath
hdfs:///user/oozie/share/lib


oozie.use.system.libpath
true


oozie.proxysubmission
true


{code}

In the Oozie launcher log, I could see
{code}
lines = LOAD 'hdfs:///tmp/encoding/input.txt' USING PigStorage('\n') AS 
line;test = FILTER lines BY line == '~';STORE test INTO 
'hdfs:///tmp/encoding/output' USING PigStorage('\n');
{code}
was used instead of the intended 松



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-find-patches-available #152673

[Apache Jenkins Server]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision c8748d221f8265c16e37383e8b3f1572bb613083 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c8748d221f8265c16e37383e8b3f1572bb613083
 > git rev-list c8748d221f8265c16e37383e8b3f1572bb613083 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson8400618391349575905.sh
mkdir: cannot create directory 
':
 File exists
  % 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 --:--:-- --:--:-- --:--:-- 0100 
491040 491040 0  59293  0 --:--:-- --:--:-- --:--:-- 59232
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : oozie-trunk-find-patches-available #152674

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #152675

[Apache Jenkins Server]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision c8748d221f8265c16e37383e8b3f1572bb613083 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c8748d221f8265c16e37383e8b3f1572bb613083
 > git rev-list c8748d221f8265c16e37383e8b3f1572bb613083 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson705598417428565072.sh
mkdir: cannot create directory 
':
 File exists
  % 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 --:--:-- --:--:-- --:--:-- 0100 
 103k0  103k0 0   104k  0 --:--:-- --:--:-- --:--:--  104k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : oozie-trunk-find-patches-available #152676

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-precommit-build #3680

[Apache Jenkins Server]

See 


--
Started by user rkanter
[EnvInject] - Loading node environment variables.
Building remotely on H10 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision c8748d221f8265c16e37383e8b3f1572bb613083 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c8748d221f8265c16e37383e8b3f1572bb613083
 > git rev-list c8748d221f8265c16e37383e8b3f1572bb613083 # timeout=10
[oozie-trunk-precommit-build] $ /bin/bash /tmp/hudson747914834944725272.sh
rm: cannot remove 'distro/downloads/*': No such file or directory
rm: invalid option -- '.'
Try 'rm --help' for more information.

Testing JIRA OOZIE-2750

  % 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 --:--:-- --:--:-- --:--:-- 0100 
 125k0  125k0 0   169k  0 --:--:-- --:--:-- --:--:--  169k
OOZIE-2750 is not "Patch Available".  Exiting.

Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?

[jira] [Commented] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2750:
--

Testing JIRA OOZIE-2750

Cleaning local git workspace

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3681

[Apache Jenkins Server]

See 


--
Started by user rkanter
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision c8748d221f8265c16e37383e8b3f1572bb613083 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c8748d221f8265c16e37383e8b3f1572bb613083
 > git rev-list c8748d221f8265c16e37383e8b3f1572bb613083 # timeout=10
[oozie-trunk-precommit-build] $ /bin/bash /tmp/hudson9196329114428853557.sh
rm: cannot remove 'distro/downloads/*': No such file or directory
rm: invalid option -- '.'
Try 'rm --help' for more information.

Testing JIRA OOZIE-2750

  % 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 --:--:-- --:--:-- --:--:-- 0100 
 128k0  128k0 0   170k  0 --:--:-- --:--:-- --:--:--  170k
OOZIE-2750 is not "Patch Available".  Exiting.

Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: Test reports were found 
but none of them are new. Did tests run? 
For example, 

 is 2 days 21 hr old

[jira] [Commented] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2750:
--

Testing JIRA OOZIE-2750

Cleaning local git workspace

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Robert Kanter (JIRA)]

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

Robert Kanter reassigned OOZIE-2750:


Assignee: Robert Kanter  (was: Grant Sohn)

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Robert Kanter (JIRA)]

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

Robert Kanter reassigned OOZIE-2750:


Assignee: Grant Sohn  (was: Robert Kanter)

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2750:
--

[~gsohn], please leave this as "Patch Available".  Jenkins only runs when it's 
at that status.

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Grant Sohn (JIRA)]

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

Grant Sohn updated OOZIE-2750:
--
Attachment: OOZIE-2750.6.patch

found another typo.

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch, OOZIE-2750.6.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2807) Oozie gets RM delegation token even for checking job status

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-2807:
---
Attachment: OOZIE-2807-4.patch

> Oozie gets RM delegation token even for checking job status
> ---
>
> Key: OOZIE-2807
> URL: https://issues.apache.org/jira/browse/OOZIE-2807
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2807-1.patch, OOZIE-2807-2.patch, 
> OOZIE-2807-3.patch, OOZIE-2807-4.patch
>
>
> We had one user submitting way too many workflows with single hive query - 
> ~3600 workflows running concurrently. Surprisingly Oozie held up well without 
> issues.
> But [~daryn] from our hadoop team saw that the amount of delegation tokens 
> fetched by Oozie was very high compared to actual number of jobs submitted 
> and was stressing RM with the calls and also pushing it close to its memory 
> limits. This is because we are fetching the delegation token every time we 
> create a JobClient instead of only during job submission.
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java#L503-L519
> So for one job we fetch
> 1) 1 token during submission
> 2) 1 token every 5 minutes when we check status of job
> 3) 1 token after the job ends to retrieve status.
> 4) 1 token if we are killing the job.
> So for a job running for 11 minutes, we would have fetched the token 4 times. 
> May be more in other cases like mapreduce where we check for end of launcher 
> and child job.
> Only 1 out of the token (used in the job submission) will be cancelled after 
> job completes. Other tokens are kind of leaked and will only be cleaned up by 
> RM after the expiry period (24 hrs is default). This can make RM go out of 
> memory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2807) Oozie gets RM delegation token even for checking job status

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2807:


Liked Robert's suggestions. addRMDelegationToken method will be only place for 
adding tokens. Would be easier to track duplicate additions. Updated the patch.

> Oozie gets RM delegation token even for checking job status
> ---
>
> Key: OOZIE-2807
> URL: https://issues.apache.org/jira/browse/OOZIE-2807
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2807-1.patch, OOZIE-2807-2.patch, 
> OOZIE-2807-3.patch, OOZIE-2807-4.patch
>
>
> We had one user submitting way too many workflows with single hive query - 
> ~3600 workflows running concurrently. Surprisingly Oozie held up well without 
> issues.
> But [~daryn] from our hadoop team saw that the amount of delegation tokens 
> fetched by Oozie was very high compared to actual number of jobs submitted 
> and was stressing RM with the calls and also pushing it close to its memory 
> limits. This is because we are fetching the delegation token every time we 
> create a JobClient instead of only during job submission.
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java#L503-L519
> So for one job we fetch
> 1) 1 token during submission
> 2) 1 token every 5 minutes when we check status of job
> 3) 1 token after the job ends to retrieve status.
> 4) 1 token if we are killing the job.
> So for a job running for 11 minutes, we would have fetched the token 4 times. 
> May be more in other cases like mapreduce where we check for end of launcher 
> and child job.
> Only 1 out of the token (used in the job submission) will be cancelled after 
> job completes. Other tokens are kind of leaked and will only be cleaned up by 
> RM after the expiry period (24 hrs is default). This can make RM go out of 
> memory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-1887) Remove the utils dir

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1887:
--

Testing JIRA OOZIE-1887

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{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{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 
[hadooplibs/hadoop-utils-2].
.{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/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
{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: 1891
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3682/

> Remove the utils dir
> 
>
> Key: OOZIE-1887
> URL: https://issues.apache.org/jira/browse/OOZIE-1887
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.0
>Reporter: Robert Kanter
>Assignee: Kevin Trieu
>  Labels: newbie
> Attachments: OOZIE-1887.001.patch
>
>
> We should remove the utils directory, it contains some sql files that haven't 
> been updated in 3 years and are no longer used in favor of the ooziedb.sh 
> script.  They may confuse users who assume they should be used.
> https://github.com/apache/oozie/tree/master/utils



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3682

[Apache Jenkins Server]

See 


--
[...truncated 1.33 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionStartXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionUpdateXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordKillXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionSkipXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/TransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/IgnoreTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/BulkJobsXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/RerunTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/KillTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/SuspendTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/StatusTransitXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/PreconditionException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/PauseTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/LocalOozieClient.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/test/EmbeddedServletContainer.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/decision/DecisionActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.ErrorType.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ssh/SshActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.RETRYPOLICY.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.JavaMailAuthenticator.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ControlNodeActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ForkActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/EndActionExecutor.html
 longer than 100 characters.

[jira] [Commented] (OOZIE-1887) Remove the utils dir

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-1887:
--

+1

> Remove the utils dir
> 
>
> Key: OOZIE-1887
> URL: https://issues.apache.org/jira/browse/OOZIE-1887
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.0
>Reporter: Robert Kanter
>Assignee: Kevin Trieu
>  Labels: newbie
> Attachments: OOZIE-1887.001.patch
>
>
> We should remove the utils directory, it contains some sql files that haven't 
> been updated in 3 years and are no longer used in favor of the ooziedb.sh 
> script.  They may confuse users who assume they should be used.
> https://github.com/apache/oozie/tree/master/utils



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (OOZIE-1887) Remove the utils dir

[Robert Kanter (JIRA)]

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

Robert Kanter reassigned OOZIE-1887:


Assignee: Robert Kanter  (was: Kevin Trieu)

> Remove the utils dir
> 
>
> Key: OOZIE-1887
> URL: https://issues.apache.org/jira/browse/OOZIE-1887
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>  Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-1887.001.patch
>
>
> We should remove the utils directory, it contains some sql files that haven't 
> been updated in 3 years and are no longer used in favor of the ooziedb.sh 
> script.  They may confuse users who assume they should be used.
> https://github.com/apache/oozie/tree/master/utils



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2820) more spelling errors in exceptions and logging

[Grant Sohn (JIRA)]

Grant Sohn created OOZIE-2820:
-

 Summary: more spelling errors in exceptions and logging
 Key: OOZIE-2820
 URL: https://issues.apache.org/jira/browse/OOZIE-2820
 Project: Oozie
  Issue Type: Bug
  Components: core
Reporter: Grant Sohn
Priority: Trivial


core/src/main/java/org/apache/oozie/servlet/JVMInfo.java: 
sb.append("  Deamon 
Threads=").append(threadMXBean.getDaemonThreadCount());

Deamon -> Daemon

core/src/main/java/org/apache/oozie/util/db/SqlStatement.java:
throw new RuntimeException("Need atleast 1 Table !!");
core/src/main/java/org/apache/oozie/util/db/SqlStatement.java:
throw new RuntimeException("Need atleast 1 Column !!");
atleast -> at least

core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java
INSTACE -> INSTANCE

core/src/main/java/org/apache/oozie/action/ssh/SshActionExecutor.java
UNKOWN_ERROR -> UNKNOWN_ERROR



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3683

[Apache Jenkins Server]

See 


--
[...truncated 1.30 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/BundleJobsGetNeedStartJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobGetJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/BundleJobsGetUnpausedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobGetJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionGetForInputCheckJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobGetActionForNominalTimeJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionRemoveJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionGetForExternalIdJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionQueryExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobGetActionsJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/BundleJobsDeleteJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobsCountNotForPurgeFromParentIdJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobsGetUnpausedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/SLASummaryQueryExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobsBasicInfoFromCoordParentIdJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobQueryExecutor.CoordJobQuery.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobsToBeMaterializedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobQueryExecutor.WorkflowJobQuery.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionsActiveCountJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordinatorJobGetForUserAppnameJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/BundleJobsGetPausedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowActionsGetForJobJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobGetForUserJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobsGetPausedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobGetActionsRunningJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowActionQueryExecutor.WorkflowActionQuery.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-

[jira] [Commented] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2750:
--

Testing JIRA OOZIE-2750

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 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{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{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/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
{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} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3683/

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch, OOZIE-2750.6.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3684

[Apache Jenkins Server]

See 


--
[...truncated 1.34 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ssh/SshActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.RETRYPOLICY.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.JavaMailAuthenticator.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ControlNodeActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ForkActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/EndActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/StartActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/JoinActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/KillActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/SqoopActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/Hive2Credentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HCatCredentialHelper.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/LauncherMapperHelper.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/Credentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/ShellActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/ScriptLanguageActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/PigActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HCatCredentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/JavaActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/CredentialException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/FsELFunctions.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/DistcpActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HadoopELFunctions.html
 longer than 

[jira] [Commented] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2750:
--

Testing JIRA OOZIE-2750

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 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{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{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 
[hadooplibs/hadoop-utils-2].
.{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/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
{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: 1891
.Tests failed: 6
.Tests errors: 3

.The patch failed the following testcases:

.  testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)

.Tests failing with errors:
.  testAddXIncludeFromStream(org.apache.oozie.util.TestXConfiguration)
.  testAddXIncludeFromReader(org.apache.oozie.util.TestXConfiguration)
.  testLoadDump(org.apache.oozie.tools.TestDBLoadDump)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3684/

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch, OOZIE-2750.6.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2817) Increase test case stability in pre-commit job

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2817:
--
Attachment: OOZIE-2817-002.patch

1) addressed some shellcheck errors. I think they could be fixed as part of an 
other jira completely. 
2) added list of flaky tests. Let's hope we'll have some when the patch is 
tested.

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2807) Oozie gets RM delegation token even for checking job status

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2807:
---

+1

> Oozie gets RM delegation token even for checking job status
> ---
>
> Key: OOZIE-2807
> URL: https://issues.apache.org/jira/browse/OOZIE-2807
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2807-1.patch, OOZIE-2807-2.patch, 
> OOZIE-2807-3.patch, OOZIE-2807-4.patch
>
>
> We had one user submitting way too many workflows with single hive query - 
> ~3600 workflows running concurrently. Surprisingly Oozie held up well without 
> issues.
> But [~daryn] from our hadoop team saw that the amount of delegation tokens 
> fetched by Oozie was very high compared to actual number of jobs submitted 
> and was stressing RM with the calls and also pushing it close to its memory 
> limits. This is because we are fetching the delegation token every time we 
> create a JobClient instead of only during job submission.
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java#L503-L519
> So for one job we fetch
> 1) 1 token during submission
> 2) 1 token every 5 minutes when we check status of job
> 3) 1 token after the job ends to retrieve status.
> 4) 1 token if we are killing the job.
> So for a job running for 11 minutes, we would have fetched the token 4 times. 
> May be more in other cases like mapreduce where we check for end of launcher 
> and child job.
> Only 1 out of the token (used in the job submission) will be cancelled after 
> job completes. Other tokens are kind of leaked and will only be cleaned up by 
> RM after the expiry period (24 hrs is default). This can make RM go out of 
> memory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3685

[Apache Jenkins Server]

See 


--
[...truncated 1.33 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionStartXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionUpdateXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordKillXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionSkipXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/TransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/IgnoreTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/BulkJobsXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/RerunTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/KillTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/SuspendTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/StatusTransitXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/PreconditionException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/PauseTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/LocalOozieClient.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/test/EmbeddedServletContainer.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/decision/DecisionActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.ErrorType.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ssh/SshActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.RETRYPOLICY.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.JavaMailAuthenticator.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ControlNodeActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ForkActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/EndActionExecutor.html
 longer than 100 characters.

[jira] [Commented] (OOZIE-2807) Oozie gets RM delegation token even for checking job status

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2807:
--

Testing JIRA OOZIE-2807

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{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{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 
[hadooplibs/hadoop-utils-2].
.{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/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
{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: 1891
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3685/

> Oozie gets RM delegation token even for checking job status
> ---
>
> Key: OOZIE-2807
> URL: https://issues.apache.org/jira/browse/OOZIE-2807
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2807-1.patch, OOZIE-2807-2.patch, 
> OOZIE-2807-3.patch, OOZIE-2807-4.patch
>
>
> We had one user submitting way too many workflows with single hive query - 
> ~3600 workflows running concurrently. Surprisingly Oozie held up well without 
> issues.
> But [~daryn] from our hadoop team saw that the amount of delegation tokens 
> fetched by Oozie was very high compared to actual number of jobs submitted 
> and was stressing RM with the calls and also pushing it close to its memory 
> limits. This is because we are fetching the delegation token every time we 
> create a JobClient instead of only during job submission.
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java#L503-L519
> So for one job we fetch
> 1) 1 token during submission
> 2) 1 token every 5 minutes when we check status of job
> 3) 1 token after the job ends to retrieve status.
> 4) 1 token if we are killing the job.
> So for a job running for 11 minutes, we would have fetched the token 4 times. 
> May be more in other cases like mapreduce where we check for end of launcher 
> and child job.
> Only 1 out of the token (used in the job submission) will be cancelled after 
> job completes. Other tokens are kind of leaked and will only be cleaned up by 
> RM after the expiry period (24 hrs is default). This can make RM go out of 
> memory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2807) Oozie gets RM delegation token even for checking job status

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2807:


Thank you Rohini and Robert for review. Committed to master.

> Oozie gets RM delegation token even for checking job status
> ---
>
> Key: OOZIE-2807
> URL: https://issues.apache.org/jira/browse/OOZIE-2807
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2807-1.patch, OOZIE-2807-2.patch, 
> OOZIE-2807-3.patch, OOZIE-2807-4.patch
>
>
> We had one user submitting way too many workflows with single hive query - 
> ~3600 workflows running concurrently. Surprisingly Oozie held up well without 
> issues.
> But [~daryn] from our hadoop team saw that the amount of delegation tokens 
> fetched by Oozie was very high compared to actual number of jobs submitted 
> and was stressing RM with the calls and also pushing it close to its memory 
> limits. This is because we are fetching the delegation token every time we 
> create a JobClient instead of only during job submission.
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java#L503-L519
> So for one job we fetch
> 1) 1 token during submission
> 2) 1 token every 5 minutes when we check status of job
> 3) 1 token after the job ends to retrieve status.
> 4) 1 token if we are killing the job.
> So for a job running for 11 minutes, we would have fetched the token 4 times. 
> May be more in other cases like mapreduce where we check for end of launcher 
> and child job.
> Only 1 out of the token (used in the job submission) will be cancelled after 
> job completes. Other tokens are kind of leaked and will only be cleaned up by 
> RM after the expiry period (24 hrs is default). This can make RM go out of 
> memory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (OOZIE-1887) Remove the utils dir

[Robert Kanter (JIRA)]

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

Robert Kanter reassigned OOZIE-1887:


Assignee: Kevin Trieu  (was: Robert Kanter)

> Remove the utils dir
> 
>
> Key: OOZIE-1887
> URL: https://issues.apache.org/jira/browse/OOZIE-1887
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.0
>Reporter: Robert Kanter
>Assignee: Kevin Trieu
>  Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-1887.001.patch
>
>
> We should remove the utils directory, it contains some sql files that haven't 
> been updated in 3 years and are no longer used in favor of the ooziedb.sh 
> script.  They may confuse users who assume they should be used.
> https://github.com/apache/oozie/tree/master/utils



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2750:
--

Test failures look unrelated.

+1

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch, OOZIE-2750.6.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3686

[Apache Jenkins Server]

See 


Changes:

[rkanter] OOZIE-1887 Remove the utils dir (kvntrieu via rkanter)

--
[...truncated 1.30 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/BundleJobsGetUnpausedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobGetJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionGetForInputCheckJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobGetActionForNominalTimeJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionRemoveJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionGetForExternalIdJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionQueryExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobGetActionsJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/BundleJobsDeleteJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobsCountNotForPurgeFromParentIdJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobsGetUnpausedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/SLASummaryQueryExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobsBasicInfoFromCoordParentIdJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobQueryExecutor.CoordJobQuery.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobsToBeMaterializedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobQueryExecutor.WorkflowJobQuery.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordActionsActiveCountJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordinatorJobGetForUserAppnameJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/BundleJobsGetPausedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowActionsGetForJobJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobGetForUserJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobsGetPausedJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/CoordJobGetActionsRunningJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowActionQueryExecutor.WorkflowActionQuery.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/executor/jpa/WorkflowJobsGetFromCoordParentIdJPAExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/org/apache/oozie/e

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2817:
--

Testing JIRA OOZIE-2817

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 7 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{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 [client].
.{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/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
{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} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3686/

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2817:
--

Let me kick this off again

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2821) Using Hadoop Archives for Oozie ShareLib

[Attila Sasvari (JIRA)]

Attila Sasvari created OOZIE-2821:
-

 Summary: Using Hadoop Archives for Oozie ShareLib
 Key: OOZIE-2821
 URL: https://issues.apache.org/jira/browse/OOZIE-2821
 Project: Oozie
  Issue Type: New Feature
Reporter: Attila Sasvari


Oozie ShareLib is a collection of lots of jar files that are required by Oozie 
actions. Right now, these jars are uploaded one by one with Oozie ShareLib 
installation. There can more hundreds of such jars, and many of them are pretty 
small, significantly smaller than a HDFS block size. Storing a large number of 
small files in HDFS is inefficient (for example due to the fact that there is 
an object maintained for each file in the NameNode's memory and blocks 
containing the small files might be much bigger then the actual files). When an 
action is executed, these jar files are copied to the distributed cache.

It  would worth to investigate the possibility of using [Hadoop 
archives|http://hadoop.apache.org/docs/r2.6.5/hadoop-mapreduce-client/hadoop-mapreduce-client-core/HadoopArchives.html]
 for handling  Oozie ShareLib files, because it could result in better 
utilisation of HDFS. 





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2821) Using Hadoop Archives for Oozie ShareLib

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2821:
--

Thanks for the interesting idea [~asasvari]!

The tricky thing here will be in creating the HAR files.  I dealt with a 
similar, though more problematic, issue with Yarn's Aggregated Log files in 
MAPREDUCE-6415, and some followups.  In a nutshell, the issue is that you end 
up with one small file per NM per Application, so on a large busy cluster, that 
adds up.  MAPREDUCE-6415 introduces a CLI tool that combines them into HAR 
files, so you get only one file per Application.  The tricky part is that it 
runs a Distributed Shell job which then runs MR jobs in local mode, one for 
each set of logs to process.  I don't think we want to run an MR job (local or 
otherwise) every time we install the sharelib.  AFAIK, the only way to create a 
HAR file is to run an MR job.  Maybe there's some other way?  Or perhaps it's 
enough to add a CLI argument to the sharelib upload script that will run an MR 
job to generate the HAR file after uploading the sharelib so users can decide 
if they want to run the MR job or not?

> Using Hadoop Archives for Oozie ShareLib
> 
>
> Key: OOZIE-2821
> URL: https://issues.apache.org/jira/browse/OOZIE-2821
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Attila Sasvari
>
> Oozie ShareLib is a collection of lots of jar files that are required by 
> Oozie actions. Right now, these jars are uploaded one by one with Oozie 
> ShareLib installation. There can more hundreds of such jars, and many of them 
> are pretty small, significantly smaller than a HDFS block size. Storing a 
> large number of small files in HDFS is inefficient (for example due to the 
> fact that there is an object maintained for each file in the NameNode's 
> memory and blocks containing the small files might be much bigger then the 
> actual files). When an action is executed, these jar files are copied to the 
> distributed cache.
> It  would worth to investigate the possibility of using [Hadoop 
> archives|http://hadoop.apache.org/docs/r2.6.5/hadoop-mapreduce-client/hadoop-mapreduce-client-core/HadoopArchives.html]
>  for handling  Oozie ShareLib files, because it could result in better 
> utilisation of HDFS. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (90 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2817  Increase test case stability in pre-commit job
https://issues.apache.org/jira/browse/OOZIE-2817
OOZIE-2816  Strip out the first command word from Sqoop action if its "sqoop"
https://issues.apache.org/jira/browse/OOZIE-2816
OOZIE-2813  Remove tabs and trailing whitespaces from oozie-defaul.xml
https://issues.apache.org/jira/browse/OOZIE-2813
OOZIE-2796  oozie.action.keep.action.dir not getting noticed
https://issues.apache.org/jira/browse/OOZIE-2796
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2785  Master is not compiling with hadoop-1 profile
https://issues.apache.org/jira/browse/OOZIE-2785
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2780  Upgrade hadoop-common version to 2.6.0
https://issues.apache.org/jira/browse/OOZIE-2780
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2769  Extend FS action to allow setrep on a file
https://issues.apache.org/jira/browse/OOZIE-2769
OOZIE-2753  Update Docs for Jetty Tomcat changes
https://issues.apache.org/jira/browse/OOZIE-2753
OOZIE-2751  LocalOozieClient is missing methods from OozieClient
https://issues.apache.org/jira/browse/OOZIE-2751
OOZIE-2746  Several tests failure in TestV2ValidateServlet.java
https://issues.apache.org/jira/browse/OOZIE-2746
OOZIE-2739  Remove property expansion pattern from ShellMain's log4j properties 
content
https://issues.apache.org/jira/browse/OOZIE-2739
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2733  change org.apache.hadoop.fs.permission.AccessControlException to 
org.apache.hadoop.security.AccessControlException
https://issues.apache.org/jira/browse/OOZIE-2733
OOZIE-2726  Flaky test due to daylight saving changes
https://issues.apache.org/jira/browse/OOZIE-2726
OOZIE-2718  Improve -dryrun for bundles
https://issues.apache.org/jira/browse/OOZIE-2718
OOZIE-2713  Provide an option to log out contents of the localized jar files
https://issues.apache.org/jira/browse/OOZIE-2713
OOZIE-2701  Oozie to support Multiple HCatalog URIs
https://issues.apache.org/jira/browse/OOZIE-2701
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693  SimpleHCatDependencyCache.removeMissingDependency can throw NPE
https://issues.apache.org/jira/browse/OOZIE-2693
OOZIE-2692  Oozie job submit doesn't report error message to user if there is 
any issue with job conf
https://issues.apache.org/jira/browse/OOZIE-2692
OOZIE-2684  Bad database schema error for WF_ACTIONS table
https://issues.apache.org/jira/browse/OOZIE-2684
OOZIE-2681  fix javadoc to compile on JDK8 again
https://issues.apache.org/jira/browse/OOZIE-2681
OOZIE-2670  Upgrade Hbase to 1.2
https://issues.apache.org/jira/browse/OOZIE-2670
OOZIE-2668  Status update and recovery problems when coord action and its 
children not in sync
https://issues.apache.org/jira/browse/OOZIE-2668
OOZIE-2662  DB migration fails if DB is too big
https://issues.apache.org/jira/browse/OOZIE-2662
OOZIE-2652  Skip trash while deleting hive table partition
https://issues.apache.org/jira/browse/OOZIE-2652
OOZIE-2650  Retry coord start on database exceptions
https://issues.apache.org/jira/browse/OOZIE-2650
OOZIE-2644  Skip queuing Notification Commands when there's nothing to notify
https://issues.apache.org/jira/browse/OOZIE-2644
OOZIE-2641  rerunning an oozie coordinator job stucks on waiting
https://issues.apache.org/jira/browse/OOZIE-2641
OOZIE-2629  Get OozieShareLibCLI to perform a final rename to destPath when 
creating a Sharelib
https://issues.apache.org/jira/browse/OOZIE-2629
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues.apache.org/jira/browse/OOZIE-2618
OOZIE-2608  Comma in oozie.service.JPAService.jdbc.password value results in 
authentication error
https://issues.apache.org/jira/browse/OOZIE-2608
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues.apache.org/jira/browse/OOZIE-2585
OOZIE-2573  dataset url  whic

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (86 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues-test.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues-test.apache.org/jira/browse/OOZIE-2618
OOZIE-2617  Read properties files in action configurations
https://issues-test.apache.org/jira/browse/OOZIE-2617
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues-test.apache.org/jira/browse/OOZIE-2616
OOZIE-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues-test.apache.org/jira/browse/OOZIE-2606
OOZIE-2589  CompletedActionXCommand priority param is of no effect
https://issues-test.apache.org/jira/browse/OOZIE-2589
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues-test.apache.org/jira/browse/OOZIE-2588
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues-test.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues-test.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues-test.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues-test.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues-test.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues-test.apache.org/jira/browse/OOZIE-2572
OOZIE-2571  Add scala.binary.version Maven property so that Scala 2.11 can be 
used
https://issues-test.apache.org/jira/browse/OOZIE-2571
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues-test.apache.org/jira/browse/OOZIE-2569
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues-test.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues-test.apache.org/jira/browse/OOZIE-2564
OOZIE-2552  Update ActiveMQ version for security and other fixes
https://issues-test.apache.org/jira/browse/OOZIE-2552
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues-test.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues-test.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues-test.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues-test.apache.org/jira/browse/OOZIE-2528
OOZIE-2521  Filter options are case sensitive for jobtye=bundle
https://issues-test.apache.org/jira/browse/OOZIE-2521
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues-test.apache.org/jira/browse/OOZIE-2518
OOZIE-2517  Add support for startCreatedTime and endCreatedTime filters for 
coord and bundles
https://issues-test.apache.org/jira/browse/OOZIE-2517
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues-test.apache.org/jira/browse/OOZIE-2513
OOZIE-2512  ShareLibservice returns incorrect path for jar
https://issues-test.apache.org/jira/browse/OOZIE-2512
OOZIE-2508  Documentation change for Coord action rerun [OOZIE-1735]
https://issues-test.apache.org/jira/browse/OOZIE-2508
OOZIE-2501  ZK reentrant lock doesn't work for few cases
https://issues-test.apache.org/jira/browse/OOZIE-2501
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues-test.apache.org/jira/browse/OOZIE-2500
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues-test.apache.org/jira/browse/OOZIE-2499
OOZIE-2498  Oozie CallerId configuration for downstream components 
https://issues-test.apache.org/jira/browse/OOZIE-2498
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues-test.apache.org/jira/browse/OOZIE-2495
OOZIE-2491  oozie acl cannot specify group,it does`t work
https://issues-test.apache.org/jira/browse/OOZIE-2491
OOZIE