Build failed in Jenkins: oozie-trunk-find-patches-available #84389
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84389/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson6000795515233664558.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84390
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84390/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson4954136431004343059.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- 0:00:01 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:02 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:03 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:04 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:05 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:05 --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84391
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84391/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson4323846490344150917.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84392
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84392/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson5022293849983985592.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84393
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84393/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson7784662792062240701.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:01 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:02 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:03 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:04 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:05 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:05 --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84394
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84394/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson4237927053783119969.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84395
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84395/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson6761657375833121542.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84396
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84396/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson6032666878778445131.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84397
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84397/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson3862631005508273246.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84398
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84398/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson8257531231336778669.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:01 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:02 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:03 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:04 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:05 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:06 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:07 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:08 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:09 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:10 --:--:-- 0
0 00 00 0 0 0 --:--:-- 0:00:10 --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84399
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84399/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson3841148924375349549.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure
Build failed in Jenkins: oozie-trunk-find-patches-available #84400
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84400/
--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
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 1c668054190aee9991b2ea20cf48e1f5b494806f
(refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 1c668054190aee9991b2ea20cf48e1f5b494806f
git rev-list 1c668054190aee9991b2ea20cf48e1f5b494806f # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash
/tmp/hudson1988190972953760939.sh
mkdir: cannot create directory
'https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/bin/tmp':
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 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
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 #84401
See https://builds.apache.org/job/oozie-trunk-find-patches-available/84401/
[jira] [Updated] (OOZIE-2028) Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true
[ https://issues.apache.org/jira/browse/OOZIE-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeep Vishwakarma updated OOZIE-2028: --- Attachment: OOZIE-2028-v5.patch Separate patch for fixing test case Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true Key: OOZIE-2028 URL: https://issues.apache.org/jira/browse/OOZIE-2028 Project: Oozie Issue Type: Sub-task Components: workflow Affects Versions: trunk Reporter: Jaydeep Vishwakarma Assignee: Jaydeep Vishwakarma Attachments: OOZIE-2028-v0.patch, OOZIE-2028-v1.patch, OOZIE-2028-v2.patch, OOZIE-2028-v3.patch, OOZIE-2028-v4.patch, OOZIE-2028-v5.patch, OOZIE-2028-v5.patch 1. Coord action re-run will take an addition optional flag -failed which re-run only the failed nodes. This will re-run the existing workflow with RERUN_FAIL_NODES=true. But this will also honour coord concurrency. 2. Coord action re-run with no -failed option will use the existing feature of launching new workflow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2028) Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true
[ https://issues.apache.org/jira/browse/OOZIE-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeep Vishwakarma updated OOZIE-2028: --- Attachment: OOZIE-2028-v5.patch Separate patch for fixing test cases. Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true Key: OOZIE-2028 URL: https://issues.apache.org/jira/browse/OOZIE-2028 Project: Oozie Issue Type: Sub-task Components: workflow Affects Versions: trunk Reporter: Jaydeep Vishwakarma Assignee: Jaydeep Vishwakarma Attachments: OOZIE-2028-v0.patch, OOZIE-2028-v1.patch, OOZIE-2028-v2.patch, OOZIE-2028-v3.patch, OOZIE-2028-v4.patch, OOZIE-2028-v5.patch, OOZIE-2028-v5.patch 1. Coord action re-run will take an addition optional flag -failed which re-run only the failed nodes. This will re-run the existing workflow with RERUN_FAIL_NODES=true. But this will also honour coord concurrency. 2. Coord action re-run with no -failed option will use the existing feature of launching new workflow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2028) Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true
[ https://issues.apache.org/jira/browse/OOZIE-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeep Vishwakarma updated OOZIE-2028: --- Attachment: (was: OOZIE-2028-v5.patch) Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true Key: OOZIE-2028 URL: https://issues.apache.org/jira/browse/OOZIE-2028 Project: Oozie Issue Type: Sub-task Components: workflow Affects Versions: trunk Reporter: Jaydeep Vishwakarma Assignee: Jaydeep Vishwakarma Attachments: OOZIE-2028-v0.patch, OOZIE-2028-v1.patch, OOZIE-2028-v2.patch, OOZIE-2028-v3.patch, OOZIE-2028-v4.patch, OOZIE-2028-v5.patch 1. Coord action re-run will take an addition optional flag -failed which re-run only the failed nodes. This will re-run the existing workflow with RERUN_FAIL_NODES=true. But this will also honour coord concurrency. 2. Coord action re-run with no -failed option will use the existing feature of launching new workflow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2028) Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true
[
https://issues.apache.org/jira/browse/OOZIE-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14242495#comment-14242495
]
Hadoop QA commented on OOZIE-2028:
--
Testing JIRA OOZIE-2028
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 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 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: 1560
.Tests failed: 1
.Tests errors: 0
.The patch failed the following testcases:
.
testMessage_withMixedStatus(org.apache.oozie.command.coord.TestAbandonedCoordChecker)
{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/2138/
Coord action rerun with -failed option should rerun existing workflow with
RERUN_FAIL_NODES=true
Key: OOZIE-2028
URL: https://issues.apache.org/jira/browse/OOZIE-2028
Project: Oozie
Issue Type: Sub-task
Components: workflow
Affects Versions: trunk
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma
Attachments: OOZIE-2028-v0.patch, OOZIE-2028-v1.patch,
OOZIE-2028-v2.patch, OOZIE-2028-v3.patch, OOZIE-2028-v4.patch,
OOZIE-2028-v5.patch
1. Coord action re-run will take an addition optional flag -failed which
re-run only the failed nodes. This will re-run the existing workflow with
RERUN_FAIL_NODES=true. But this will also honour coord concurrency.
2. Coord action re-run with no -failed option will use the existing feature
of launching new workflow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Build failed in Jenkins: oozie-trunk-precommit-build #2138
See https://builds.apache.org/job/oozie-trunk-precommit-build/2138/changes Changes: [shwethags] OOZIE-2028 Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true (jaydeepvishwakarma via shwethags) -- [...truncated 11027 lines...] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools --- [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools --- [INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml [WARNING] The following patterns were never triggered in this artifact exclusion filter: o '*:*:pom:*' [INFO] Copying files to https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools [WARNING] Assembly file: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools is not a regular file (it may be a directory). It cannot be attached to the project build for installation or deployment. [INFO] [INFO] [INFO] Building Apache Oozie MiniOozie 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-mini --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-mini --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-mini --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini --- [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml [INFO] [INFO] [INFO] Building Apache Oozie Distro 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-distro --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-distro --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-distro --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro --- [INFO] Executing tasks main: [get] Getting: http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin/apache-tomcat-6.0.41.tar.gz [get] To: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads/tomcat-6.0.41.tar.gz
Re: Review Request 28637: OOZIE-2030 Configuration properties from global section is not getting set in Hadoop job conf when using sub-workflow action in Oozie workflow.xml
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28637/#review64788 --- core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java https://reviews.apache.org/r/28637/#comment107555 I think it actually makes sense and whatever I thought might conflict would be ok. Could you still add a config oozie.launcher.only.job.copy.actionconf (or some better name) as bother server and action level config with default value as true, so that we can turn it off in production if some unexpected conflict rises. If only few users encounter issue we can ask them to override at action level and if there is a major issue can turn it off at server level itself. core/src/main/java/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.java https://reviews.apache.org/r/28637/#comment107556 Based on the code in LiteWorkflowAppParser.handleGlobal, eConf.getChild(configuration, ns) should contain the global configuration. Instead of parsing global and jobxml again, you could just use that. I think the cleaner way to do this would be to not touch ActionExecutors at all. Should parse and store global configuration in WorkflowInstance once and add it to each action configuration and also initialize global configuration of sub WorkflowInstance created with it. Currently the global section and its job.xml is parsed for each action which is really bad for latency. This would also take care of propagating it to nested sub-workflows. If the sub-workflow had global configuration then that should be merged while parsing itself to the parent global config initialized. - Rohini Palaniswamy On Dec. 8, 2014, 7:20 a.m., shwethags wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28637/ --- (Updated Dec. 8, 2014, 7:20 a.m.) Review request for oozie. Bugs: OOZIE-2030 https://issues.apache.org/jira/browse/OOZIE-2030 Repository: oozie-git Description --- 1. Propagate properties from configuration and job-xml from parent workflow to sub-workflow. Currently, its propagated as workflow properties, but they are required in action conf 2. For java actions, add properties from configuration and job-xml to launcher job Diffs - core/src/main/java/org/apache/oozie/action/ActionExecutor.java ff836fb core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java fed1d7a core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java f207d74 core/src/main/java/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.java bda34b5 core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java 18de48a core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 48166a5 core/src/test/java/org/apache/oozie/action/oozie/TestSubWorkflowActionExecutor.java 0d7e926 examples/src/main/apps/subwf/job.xml PRE-CREATION examples/src/main/apps/subwf/workflow.xml 9873a50 Diff: https://reviews.apache.org/r/28637/diff/ Testing --- UTs and end to end test Thanks, shwethags
parsing xml in mapreduce using oozie
Hi, I am trying to run the Mapreduce job that does xml parsing(Jaxbparser is used) and produces flat file. I am using Mahout XMLINPUTFORMAT. When I run my progam in command line it works fine(hadoop jar abc.jar input poutput ) But if i try to run on oozie it is throwing error that both starting and ending tag should be specified. I want to add this configuration to oozie *xmlinput.start and xmlinput.start * where should I need to specify above mentioned properties and how can u please help me i spend almost a week of time but dint get any help over the net eagerly waiting for the reply Thanks in Advance, Deepu
[jira] [Commented] (OOZIE-2079) Notify when a coordinator action status becomes RUNNING
[ https://issues.apache.org/jira/browse/OOZIE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14243552#comment-14243552 ] Ryota Egashira commented on OOZIE-2079: --- +1, test case failure seems unrelated. Notify when a coordinator action status becomes RUNNING --- Key: OOZIE-2079 URL: https://issues.apache.org/jira/browse/OOZIE-2079 Project: Oozie Issue Type: Bug Components: core Affects Versions: trunk, 4.0.1 Reporter: Venkat Ramachandran Assignee: Mohammad Kamrul Islam Attachments: OOZIE-2079.1.patch, OOZIE-2079.2.patch When a coordinator-action is materialized with WAITING status, Oozie calls the oozie.coord.action.notification.url as expected, but it does not when the coordinator-action status changes to RUNNING. It appears that CoordActionStartXCommand.execute() (CoordActionStartXCommand.java) method does not invoke a CoordActionNotificationXCommand(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OOZIE-2091) About oozie coordinator trigger mechanism
sunmeng created OOZIE-2091: -- Summary: About oozie coordinator trigger mechanism Key: OOZIE-2091 URL: https://issues.apache.org/jira/browse/OOZIE-2091 Project: Oozie Issue Type: Improvement Components: coordinator Reporter: sunmeng Hello everyone, I am a software engineer, worked IFLYTEK, IFLYTEK is Asia Pacific's leading intelligent voice listed companies. I work in the cloud computing sector, I found the coordinator oozie trigger mechanism datasets trigger conditions can not meet all of our company, so I added a trigger condition, shell scripts triggered. I modified the coordinator xml syntax compatible with two trigger modes, an increase of , when the coordinator will call the specified shell script, when the script returns true, coordinator will run the task of the current time. You give me somesuggestions it, this trigger mode you agree with it? Thank you! Thank you Robert Kanter reply me and give me suggestions，it's really adding the ability to trigger coordinators based on the output (true or false) of a shell script，I do not want to instead of waiting for data to be available in HDFS，I want to Compatible with both trigger mode for coordinator in order to meet all of the trigger conditions of business。I will quickly use the correct code format and make a new version of the coordinator schema。 thanks 孙盟 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (44 issues) Subscriber: ooziedaily Key Summary OOZIE-2090 wf:lastErrorNode does not take into account transient errors with retries https://issues.apache.org/jira/browse/OOZIE-2090 OOZIE-2088 Exponential retries for transient failures https://issues.apache.org/jira/browse/OOZIE-2088 OOZIE-2079 Notify when a coordinator action status becomes RUNNING https://issues.apache.org/jira/browse/OOZIE-2079 OOZIE-2076 Sharelib usage improvement https://issues.apache.org/jira/browse/OOZIE-2076 OOZIE-2060 Incorrect documentation of Java action config XML filename https://issues.apache.org/jira/browse/OOZIE-2060 OOZIE-2055 PauseTransitService does not proceed forward if any job has issue https://issues.apache.org/jira/browse/OOZIE-2055 OOZIE-2051 Allows multiple default action configuration files per action https://issues.apache.org/jira/browse/OOZIE-2051 OOZIE-2044 ssh action succeed with a not exists command which should be fail. https://issues.apache.org/jira/browse/OOZIE-2044 OOZIE-2030 Configuration properties from global section is not getting set in Hadoop job conf when using sub-workflow action in Oozie workflow.xml https://issues.apache.org/jira/browse/OOZIE-2030 OOZIE-1980 Sql error should not fail coord job https://issues.apache.org/jira/browse/OOZIE-1980 OOZIE-1977 Display patch analysis issues https://issues.apache.org/jira/browse/OOZIE-1977 OOZIE-1936 Queuedump command should display queue information for all server. https://issues.apache.org/jira/browse/OOZIE-1936 OOZIE-1931 Admin command to print all locks held by server(s) https://issues.apache.org/jira/browse/OOZIE-1931 OOZIE-1927 Use StoreStatusFilter for WorkflowsJobGetJPAExecutor https://issues.apache.org/jira/browse/OOZIE-1927 OOZIE-1922 MemoryLocksService fails if lock is acquired multiple times in same thread and released https://issues.apache.org/jira/browse/OOZIE-1922 OOZIE-1918 ActionXCommand refactoring for code reuse https://issues.apache.org/jira/browse/OOZIE-1918 OOZIE-1889 Convert NamedNativeQueries to JPQL https://issues.apache.org/jira/browse/OOZIE-1889 OOZIE-1884 ZKJobsConcurrencyService.checkJobIdForServer fails if jobs length 7 https://issues.apache.org/jira/browse/OOZIE-1884 OOZIE-1876 use pom properties rather than specific version numbers in the pom files of hbaselibs, hcataloglibs, sharelib, etc https://issues.apache.org/jira/browse/OOZIE-1876 OOZIE-1860 Oozie job mapper launch fails due to null value returned from action file https://issues.apache.org/jira/browse/OOZIE-1860 OOZIE-1855 TestPriorityDelayQueue#testPoll failed intermittently in Jenkins https://issues.apache.org/jira/browse/OOZIE-1855 OOZIE-1829 URIHandlerService doesn't support URI schemes with query strings but no path segment https://issues.apache.org/jira/browse/OOZIE-1829 OOZIE-1816 LogInfo uses action name instead of id https://issues.apache.org/jira/browse/OOZIE-1816 OOZIE-1810 Workflow cannot get into Failed state when kill control node cannot resolve variable in message https://issues.apache.org/jira/browse/OOZIE-1810 OOZIE-1802 Support workflow action log https://issues.apache.org/jira/browse/OOZIE-1802 OOZIE-1793 Improve find bugs reporting for Oozie https://issues.apache.org/jira/browse/OOZIE-1793 OOZIE-1782 Workflow path not found is thrown as SC_UNAUTHORIZED https://issues.apache.org/jira/browse/OOZIE-1782 OOZIE-1779 Add parent-id as a filter option https://issues.apache.org/jira/browse/OOZIE-1779 OOZIE-1705 Enable gc logs and print thread id in logs https://issues.apache.org/jira/browse/OOZIE-1705 OOZIE-1688 New configuration to specify server-server authentication type. https://issues.apache.org/jira/browse/OOZIE-1688 OOZIE-1676 Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers https://issues.apache.org/jira/browse/OOZIE-1676 OOZIE-1654 Fix typo (inteval to interval) https://issues.apache.org/jira/browse/OOZIE-1654 OOZIE-1638 Action retry does not use default retry max count. https://issues.apache.org/jira/browse/OOZIE-1638 OOZIE-1636 OOZIE_SYS table engine should be innodb https://issues.apache.org/jira/browse/OOZIE-1636 OOZIE-1624 Exclusion pattern for sharelib. https://issues.apache.org/jira/browse/OOZIE-1624 OOZIE-1599 Cache the list of available timezones from the admin servlet https://issues.apache.org/jira/browse/OOZIE-1599 OOZIE-1579 Add basic HTTP auth to Oozie CLI https://issues.apache.org/jira/browse/OOZIE-1579 OOZIE-1376 Extending Oozie ACLs like
[jira] [Commented] (OOZIE-2091) About oozie coordinator trigger mechanism
[ https://issues.apache.org/jira/browse/OOZIE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14243837#comment-14243837 ] ASF GitHub Bot commented on OOZIE-2091: --- GitHub user sunmeng007 opened a pull request: https://github.com/apache/oozie/pull/10 OOZIE-2091:add shell scripts trigger coordinators and compatible with th... ...e dataset trigger modeHello everyone, I am a software engineer, worked IFLYTEK, IFLYTEK is Asia Pacific's leading intelligent voice listed companies. I work in the cloud computing sector, I found the coordinator oozie trigger mechanism datasets trigger conditions can not meet all of our company, so I added a trigger condition, shell scripts triggered. I modified the coordinator xml syntax compatible with two trigger modes, an increase of , when the coordinator will call the specified shell script, when the script returns true, coordinator will run the task of the current time. You give me somesuggestions it, this trigger mode you agree with it? Thank you! Thank you Robert Kanter reply me and give me suggestions，it's really adding the ability to trigger coordinators based on the output (true or false) of a shell script，I do not want to instead of waiting for data to be available in HDFS，I want to Compatible with both trigger mode for coordinator in order to meet all of the trigger conditions of business。I will quickly use the correct code format and make a new version of the coordinator schema。 thanks 孙盟 You can merge this pull request into a Git repository by running: $ git pull https://github.com/sunmeng007/oozie-1 OOZIE-2091 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/oozie/pull/10.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #10 commit ad2346c919d1c712fe240c78fcf39aed2b9726a8 Author: mengsun meng...@iflytek.com Date: 2014-12-12T07:53:38Z OOZIE-2091:add shell scripts trigger coordinators and compatible with the dataset trigger mode About oozie coordinator trigger mechanism - Key: OOZIE-2091 URL: https://issues.apache.org/jira/browse/OOZIE-2091 Project: Oozie Issue Type: Improvement Components: coordinator Reporter: sunmeng Original Estimate: 120h Remaining Estimate: 120h Hello everyone, I am a software engineer, worked IFLYTEK, IFLYTEK is Asia Pacific's leading intelligent voice listed companies. I work in the cloud computing sector, I found the coordinator oozie trigger mechanism datasets trigger conditions can not meet all of our company, so I added a trigger condition, shell scripts triggered. I modified the coordinator xml syntax compatible with two trigger modes, an increase of , when the coordinator will call the specified shell script, when the script returns true, coordinator will run the task of the current time. You give me somesuggestions it, this trigger mode you agree with it? Thank you! Thank you Robert Kanter reply me and give me suggestions，it's really adding the ability to trigger coordinators based on the output (true or false) of a shell script，I do not want to instead of waiting for data to be available in HDFS，I want to Compatible with both trigger mode for coordinator in order to meet all of the trigger conditions of business。I will quickly use the correct code format and make a new version of the coordinator schema。 thanks 孙盟 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
