Jenkins build is back to normal : oozie-trunk-precommit-build #3310

[Apache Jenkins Server]

See 

[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

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (78 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2679  Decrease HttpClient library versions due to Hadoop incompatibility
https://issues.apache.org/jira/browse/OOZIE-2679
OOZIE-2678  Oozie job -kill doesn't work with tez jobs
https://issues.apache.org/jira/browse/OOZIE-2678
OOZIE-2676  Make hadoop-2 as the default profile
https://issues.apache.org/jira/browse/OOZIE-2676
OOZIE-2674  Improve oozie commads documentation
https://issues.apache.org/jira/browse/OOZIE-2674
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-2661  Coordinator Action status not updated when workflow job SUSPENDED
https://issues.apache.org/jira/browse/OOZIE-2661
OOZIE-2658  --driver-class-path can overwrite the classpath in SparkMain
https://issues.apache.org/jira/browse/OOZIE-2658
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-2641  rerunning an oozie coordinator job stucks on waiting
https://issues.apache.org/jira/browse/OOZIE-2641
OOZIE-2634  Queue dump command message is confusing when the queue is empty
https://issues.apache.org/jira/browse/OOZIE-2634
OOZIE-2630  Oozie Coordinator EL Functions to get first day of the week/month
https://issues.apache.org/jira/browse/OOZIE-2630
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues.apache.org/jira/browse/OOZIE-2619
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-2616  Add Tez profile for Hive and Pig sharelibs
https://issues.apache.org/jira/browse/OOZIE-2616
OOZIE-2613  Upgrade hive version from 0.13.1 to 1.2.0
https://issues.apache.org/jira/browse/OOZIE-2613
OOZIE-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues.apache.org/jira/browse/OOZIE-2606
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues.apache.org/jira/browse/OOZIE-2585
OOZIE-2582  Populating external child Ids for action failures
https://issues.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues.apache.org/jira/browse/OOZIE-2573
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues.apache.org/jira/browse/OOZIE-2564
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues.apache.org/jira/browse/OOZIE-2534
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues.apache.org/jira/browse/OOZIE-2528
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues.apache.org/jira/browse/OOZIE-2518
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues.apache.org/jira/browse/OOZIE-2513
OOZIE-2501  ZK reentrant lock doesn't work for few cases
https://issues.apache.org/jira/browse/OOZIE-2501
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues.apache.org/jira/browse/OOZIE-2499
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues.apache.org/jira/browse/OOZIE-2495
OOZIE-2487  Unable to build distro on Java 8 (on Mac)
https://issues.apache.org/jira/browse/OOZIE-2487
OOZIE-2473  Connection pool for SMTP connection
https://issues.apache.org/jira/browse/OOZIE-2473
OOZIE-2461  Workflow, Coordinator and Bundle job querying should have last 
modified filter
https://issues.apache.org/jira/browse/OOZIE-2461
OOZIE-2458  'oozie-setup.sh sharelib create' should ensure uploaded jars are 
world readable
https://issues.apache.org/jira/browse/OOZIE-2458
OOZIE-2457  Oozie log parsing regex consume more than 90% cpu
https://issues.apache.org/jira/browse/OOZIE-2457
OOZIE-2427  With Kerberos enabled, the authentication failure for the 
javas

[jira] [Updated] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-2661:
---
Attachment: (was: OOZIE-2661-4.patch)

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch, OOZIE-2661-4.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

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

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch, OOZIE-2661-4.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2626) Oozie workflow processing becomes slow after the increase of rows in WF_JOBS and WF_ACTIONS tables when the metastore is running on SQL Server

[Fady K Sedrak (JIRA)]

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

Fady K Sedrak updated OOZIE-2626:
-
Attachment: diff.patch

> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when the metastore is running on SQL Server
> --
>
> Key: OOZIE-2626
> URL: https://issues.apache.org/jira/browse/OOZIE-2626
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, workflow
>Reporter: Fady K Sedrak
> Attachments: diff.patch
>
>
> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when running against SQL Server. A secondary index need 
> to be created against WF_JOBS (created_time), WF_ACTIONS (last_check_time & 
> pending) to avoid going for a full table scan when querying against these 
> fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2626) Oozie workflow processing becomes slow after the increase of rows in WF_JOBS and WF_ACTIONS tables when the metastore is running on SQL Server

[Fady K Sedrak (JIRA)]

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

Fady K Sedrak commented on OOZIE-2626:
--

Attached a patch

> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when the metastore is running on SQL Server
> --
>
> Key: OOZIE-2626
> URL: https://issues.apache.org/jira/browse/OOZIE-2626
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, workflow
>Reporter: Fady K Sedrak
> Attachments: diff.patch
>
>
> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when running against SQL Server. A secondary index need 
> to be created against WF_JOBS (created_time), WF_ACTIONS (last_check_time & 
> pending) to avoid going for a full table scan when querying against these 
> fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2626) Oozie workflow processing becomes slow after the increase of rows in WF_JOBS and WF_ACTIONS tables when the metastore is running on SQL Server

[Fady K Sedrak (JIRA)]

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

Fady K Sedrak commented on OOZIE-2626:
--

I tested different indexes on many of slow queries in my repro environment. I 
concluded that these 2 queries would improve the performance significantly. 

Query1:
 SELECT TOP 1 t0.id, t0.app_name, t0.status, t0.run, t0.user_name, 
t0.group_name, t0.created_time, t0.start_time, t0.last_modified_time, 
t0.end_time, t0.external_id, t0.parent_id FROM WF_JOBS t0 ORDER BY 
t0.created_time DESC
Recommended Index:
 CREATE NONCLUSTERED INDEX [nci_wi_WF_JOBS_3A82B3F6CFB2A06DB9FD] ON 
[dbo].[WF_JOBS]
 ([created_time] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, 
SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, 
ALLOW_PAGE_LOCKS = ON)
Statistics:
 Before:
 Table 'WF_JOBS'. Scan count 1, logical reads 31803, physical reads 256, 
read-ahead reads 31589, lob logical reads 0, lob physical reads 0, lob 
read-ahead reads 0.
 SQL Server Execution Times:
 CPU time = 281 ms, elapsed time = 216350 ms.
 After:
 Table 'WF_JOBS'. Scan count 1, logical reads 8, physical reads 0, read-ahead 
reads 24, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
 SQL Server Execution Times:
 CPU time = 0 ms, elapsed time = 0 ms.

Query 2:
 (@P0 bigint,@P1 varchar(8000),@P2 datetime2(7))SELECT t0.id FROM WF_ACTIONS t0 
WHERE (t0.pending = @P0 AND t0.status = @P1 AND t0.last_check_time < @P2)
Recommended Index:
 CREATE NONCLUSTERED INDEX [nci_wi_WF_ACTIONS_D23BAEF4FD5EEA2EBE76] ON 
[dbo].[WF_ACTIONS]
 (
[pending] ASC,
[status] ASC,
[last_check_time] ASC
 )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, 
DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)

Statistics:
 Before:
 Table 'WF_ACTIONS'. Scan count 1, logical reads 81894, physical reads 1330, 
read-ahead reads 79172, lob logical reads 0, lob physical reads 0, lob 
read-ahead reads 0.
 SQL Server Execution Times:
 CPU time = 875 ms, elapsed time = 652591 ms.
 After:
 Table 'WF_ACTIONS'. Scan count 1, logical reads 83, physical reads 0, 
read-ahead reads 1, lob logical reads 0, lob physical reads 0, lob read-ahead 
reads 0.
 SQL Server Execution Times:
 CPU time = 0 ms, elapsed time = 167 ms.

Unfortunately openjpa doesn't support composite indexes. So I had to work 
around the problem by create 2 simple indexes indexes on last_check_time & 
pending. 

Query 2:
 (@P0 bigint,@P1 varchar(8000),@P2 datetime2(7))SELECT t0.id FROM WF_ACTIONS t0 
WHERE (t0.pending = @P0 AND t0.status = @P1 AND t0.last_check_time < @P2)
 Recommended Index:
 CREATE NONCLUSTERED INDEX [I_WF_JOBS_PENDING] ON [dbo].[WF_ACTIONS]
 (
[pending] ASC
 )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, 
DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
 GO
 CREATE NONCLUSTERED INDEX [I_WF_JOBS_LAST_CHECK_TIME] ON [dbo].[WF_ACTIONS]
 (
[pending] ASC
 )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, 
DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
 GO
Statistics:
 Before:
 Table 'WF_ACTIONS'. Scan count 1, logical reads 82034, physical reads 89, 
read-ahead reads 36446, lob logical reads 0, lob physical reads 0, lob 
read-ahead reads 0.
 SQL Server Execution Times:
 CPU time = 94 ms, elapsed time = 641094 ms.
 After:
 Table 'WF_ACTIONS'. Scan count 3, logical reads 10831, physical reads 0, 
read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead 
reads 0.
 Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, read-ahead 
reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
 Table 'Workfile'. Scan count 0, logical reads 0, physical reads 0, read-ahead 
reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
 SQL Server Execution Times:
 CPU time = 78 ms, elapsed time = 5085 ms.


> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when the metastore is running on SQL Server
> --
>
> Key: OOZIE-2626
> URL: https://issues.apache.org/jira/browse/OOZIE-2626
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, workflow
>Reporter: Fady K Sedrak
>
> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when running against SQL Server. A secondary index need 
> to be created against WF_JOBS (created_time), WF_ACTIONS (last_check_time & 
> pending) to avoid going for a full table scan when querying against these 
> fields.



--
This message was sent by Atlassian JIR

[jira] [Updated] (OOZIE-2626) Oozie workflow processing becomes slow after the increase of rows in WF_JOBS and WF_ACTIONS tables when the metastore is running on SQL Server

[Fady K Sedrak (JIRA)]

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

Fady K Sedrak updated OOZIE-2626:
-
Summary: Oozie workflow processing becomes slow after the increase of rows 
in WF_JOBS and WF_ACTIONS tables when the metastore is running on SQL Server  
(was: Oozie workflow processing becomes slow after the increase of rows in 
COORD_ACTIONS and WF_ACTIONS tables when the metastore is running on SQL Server)

> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when the metastore is running on SQL Server
> --
>
> Key: OOZIE-2626
> URL: https://issues.apache.org/jira/browse/OOZIE-2626
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, workflow
>Reporter: Fady K Sedrak
>
> Oozie workflow processing becomes slow after the increase of rows in 
> COORD_ACTIONS and WF_ACTIONS tables when running against SQL Server. A 
> secondary index need to be created against COORD_ACTIONS (last_modified_time 
> & status), WF_ACTIONS (last_modified_time & status) to avoid going for a full 
> table scan when querying against these fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2626) Oozie workflow processing becomes slow after the increase of rows in WF_JOBS and WF_ACTIONS tables when the metastore is running on SQL Server

[Fady K Sedrak (JIRA)]

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

Fady K Sedrak updated OOZIE-2626:
-
Description: Oozie workflow processing becomes slow after the increase of 
rows in WF_JOBS and WF_ACTIONS tables when running against SQL Server. A 
secondary index need to be created against WF_JOBS (created_time), WF_ACTIONS 
(last_check_time & pending) to avoid going for a full table scan when querying 
against these fields.  (was: Oozie workflow processing becomes slow after the 
increase of rows in COORD_ACTIONS and WF_ACTIONS tables when running against 
SQL Server. A secondary index need to be created against COORD_ACTIONS 
(last_modified_time & status), WF_ACTIONS (last_modified_time & status) to 
avoid going for a full table scan when querying against these fields.)

> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when the metastore is running on SQL Server
> --
>
> Key: OOZIE-2626
> URL: https://issues.apache.org/jira/browse/OOZIE-2626
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, workflow
>Reporter: Fady K Sedrak
>
> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS 
> and WF_ACTIONS tables when running against SQL Server. A secondary index need 
> to be created against WF_JOBS (created_time), WF_ACTIONS (last_check_time & 
> pending) to avoid going for a full table scan when querying against these 
> fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

Changes:

[purushah] OOZIE-2572 SLA DURATION miss not shown when job is running for longer

[rkanter] OOZIE-1793 Improve find bugs reporting for Oozie (rkanter)

[rkanter] OOZIE-2667 Optimize queries for DB export (gezapeti via rkanter)

[rkanter] OOZIE-2273 MiniOozie does not work outside of Oozie (rkanter)

--
[...truncated 6142 lines...]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[IN

[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2613:
--

A test is still failing for me with the hadoop-2 profile:
{noformat}
---
Test set: org.apache.oozie.dependency.TestHCatURIHandler
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.789 sec <<< 
FAILURE!
testExists(org.apache.oozie.dependency.TestHCatURIHandler)  Time elapsed: 0.004 
sec  <<< ERROR!
org.apache.oozie.service.HCatAccessorException: E1501: Error in getting HCat 
Access [org.apache.hive.hcatalog.common.HCatException : 9001 : Exception 
occurred while processing HCat request : MetaException while dropping 
partition.. Cause : MetaException(message:Got exception: 
org.apache.hadoop.security.AccessControlException Permission denied: user=test, 
access=WRITE, 
inode="/Users/rkanter/dev/oozie-git/core/target/test-data/oozietests/org.apache.oozie.dependency.TestHCatURIHandler/testExists/db1/table1/year=2012/month=12/dt=04":rkanter:supergroup:drwxr-xr-x
at 
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkFsPermission(FSPermissionChecker.java:265)
at 
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:251)
at 
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:232)
at 
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:179)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSNamesystem.java:5497)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.deleteInternal(FSNamesystem.java:3342)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.deleteInt(FSNamesystem.java:3296)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.delete(FSNamesystem.java:3280)
at 
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.delete(NameNodeRpcServer.java:727)
at 
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.delete(ClientNamenodeProtocolServerSideTranslatorPB.java:547)
at 
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2013)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2009)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2007)
)]
at 
org.apache.oozie.dependency.HCatURIHandler.delete(HCatURIHandler.java:201)
at 
org.apache.oozie.dependency.TestHCatURIHandler.testExists(TestHCatURIHandler.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:24)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.hive.hcatalog.common.HCatException : 9001 : Exception 
occurred while processing HCat request : MetaException w

[jira] [Updated] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

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

Updated the patch with all the changes. 

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch, OOZIE-2661-4.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Purshotam Shah (JIRA)]

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

Purshotam Shah commented on OOZIE-2661:
---

{code}
+else if (workflowJob.getStatus() == 
WorkflowJob.Status.SUSPENDED) {
+
coordAction.setStatus(CoordinatorAction.Status.SUSPENDED);
+slaStatus = Status.FAILED;
+// set pending to false as the status is SUSPENDED
+coordAction.setPending(0);
+}
{code}

is missing in patch 3.

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

--
[...truncated 6287 lines...]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[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.44/bin/apache-tomcat-6.0.44.tar.gz
  [get] To: 

[jira] [Updated] (OOZIE-2622) ExtJS 2.2 is no longer available

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-2622:
-
Summary: ExtJS 2.2 is no longer available  (was: ExtJS 2.2 in no available)

> ExtJS 2.2 is no longer available
> 
>
> Key: OOZIE-2622
> URL: https://issues.apache.org/jira/browse/OOZIE-2622
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Sergey Svinarchuk
>Priority: Blocker
> Fix For: 4.3.0
>
>
> ExtJS 2.2 is no longer available by link from Oozie docs - 
> http://dev.sencha.com/deploy/ext-2.2.zip 
> (http://oozie.apache.org/docs/4.2.0/DG_QuickStart.html)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2679) Decrease HttpClient library versions due to Hadoop incompatibility

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-2679:
-
Summary: Decrease HttpClient library versions due to Hadoop incompatibility 
 (was: Decrease HttpClient library versions)

> Decrease HttpClient library versions due to Hadoop incompatibility
> --
>
> Key: OOZIE-2679
> URL: https://issues.apache.org/jira/browse/OOZIE-2679
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2679.patch
>
>
> Version 4.4 of HttpClient has issued with Hadoop: HADOOP-11859 
> It will be fixed in Hadoop 2.8.0, until we use that we should use 4.3 of 
> HttpClient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2661:


Test failures are not related. Jenkins is having trouble updating the build 
details on Jira. 

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

--
[...truncated 6289 lines...]
[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 

  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz
  [get] To: 

.

[jira] [Commented] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2661:



Testing JIRA OOZIE-2661

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1807
.Tests failed: 2
.Tests errors: 0

.The patch failed the following testcases:

.  
testActionCheckTransientDuringLauncher(org.apache.oozie.command.wf.TestActionCheckXCommand)
.  testCoordinatorActionEvent(org.apache.oozie.event.TestEventGeneration)

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


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


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

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


> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

Changes:

[rkanter] OOZIE-2525 SchemaChecker fails with NPE (rkanter)

--
[...truncated 6283 lines...]
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[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.44/bin/apache-tomcat-6.0.44.tar.gz
  [get] To: 

[jira] [Commented] (OOZIE-2679) Decrease HttpClient library versions

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2679:
--

That's unfortunate about HADOOP-11859.  I've created OOZIE-2680 to followup on 
this once we make Hadoop 2.8.0 the minimum.

+1 pending Jenkins.

> Decrease HttpClient library versions
> 
>
> Key: OOZIE-2679
> URL: https://issues.apache.org/jira/browse/OOZIE-2679
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2679.patch
>
>
> Version 4.4 of HttpClient has issued with Hadoop: HADOOP-11859 
> It will be fixed in Hadoop 2.8.0, until we use that we should use 4.3 of 
> HttpClient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OOZIE-2680) Increase HttpClient to 4.4

[Robert Kanter (JIRA)]

Robert Kanter created OOZIE-2680:


 Summary: Increase HttpClient to 4.4
 Key: OOZIE-2680
 URL: https://issues.apache.org/jira/browse/OOZIE-2680
 Project: Oozie
  Issue Type: Bug
Reporter: Robert Kanter


Once Hadoop 2.8.0 becomes the minimum supported Hadoop version, we should 
upgrade HttpClient to 4.4 (or a newer one if available).  Previous versions are 
not compatible due to HADOOP-11859, which was added in Hadoop 2.8.0.  See 
OOZIE-2679.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 51459: Add an admin command to run the PurgeXCommand

[Robert Kanter]

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




docs/src/site/twiki/DG_CommandLineTool.twiki (line 139)


Don't forget to add the equivalent documentation to the REST API docs.


- Robert Kanter


On Sept. 18, 2016, 6:43 a.m., Abhishek Bafna wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51459/
> ---
> 
> (Updated Sept. 18, 2016, 6:43 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2041
> https://issues.apache.org/jira/browse/OOZIE-2041
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> By default {{PurgeService}} executes every hour to clean up old oozie 
> workflows, coordinators and bundles from Oozie DB. With the new {{oozie admin 
> -purge wf=1\;coord=2\;bundle=3\;limit=100\;oldCoordAction=true/false>}} 
> command, users (admin users) can execute {{PurgeService}} on demand.
> 
> # Allow users to specify older than values for (workflow, coordinator and 
> bundle) in {{days}}, limit and turn {{on/off}} for old coordinator actions. 
> At least one parameter needs to be specified.
> # If user does not specify one of parameter than {{PurgeService}} will use 
> the default value of it from {{oozie-default.xml}} or {{oozie-site.xml}}.
> # The execution of the Purge Command will require a lock for execution, so at 
> the same time two {{PurgeXCommand}} will not execute. In the case, when lock 
> is not acquired, it will queue the command.
> # Currently purge command is implemented as blocking command. Users will need 
> to wait until command execution completes.
> # In the HA mode, purge command can be executed only on the leader Oozie 
> server.
> # purge command can be enabled/disabled using 
> {{oozie.service.PurgeService.enable.command.line}} property. By default it is 
> enabled.
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java f1d0f2b 
>   client/src/main/java/org/apache/oozie/client/OozieClient.java a882cab 
>   client/src/main/java/org/apache/oozie/client/rest/JsonTags.java 397e9ed 
>   client/src/main/java/org/apache/oozie/client/rest/RestConstants.java 
> 4129364 
>   core/src/main/java/org/apache/oozie/command/PurgeXCommand.java ab06fdf 
>   core/src/main/java/org/apache/oozie/service/PurgeService.java 6e4a8e8 
>   core/src/main/java/org/apache/oozie/servlet/BaseAdminServlet.java 64d3f1f 
>   core/src/main/java/org/apache/oozie/servlet/V0AdminServlet.java fd573d5 
>   core/src/main/java/org/apache/oozie/servlet/V1AdminServlet.java 965a19a 
>   core/src/main/resources/oozie-default.xml 40a5fe5 
>   core/src/test/java/org/apache/oozie/client/TestOozieCLI.java a30baaa 
>   core/src/test/java/org/apache/oozie/servlet/TestAdminServlet.java ffa3dc1 
>   core/src/test/java/org/apache/oozie/servlet/TestV1AdminServlet.java 35568e1 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 567e260 
> 
> Diff: https://reviews.apache.org/r/51459/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Abhishek Bafna
> 
>

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2041:
--

I haven't looked through the patch yet, but I think for HA, we shouldn't put 
the burden on the user to pick the current leader server because we don't 
currently disclose which server is the leader.  Even if they knew the leader 
address, they'd have to temporarily change their Oozie client from the load 
balancer address to the leader address, which is annoying.

I think we should do one of the following:
# Any Oozie Server can run the purge command when triggered from the CLI.  The 
{{PurgeXCommand}} should be acquiring a ZK-based lock, so that doesn't seem 
like it should be problematic.  The only reason we currently have only the 
leader run the recurring purge is so that we don't run it more often than 
expected.
# The Oozie Server receiving the call from the CLI will forward it to the 
leader.

I like option 1 better than option 2.

> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch
>
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.  
> We can add a new admin command to run this.  e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we 
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either 
> it's already running (i.e. the user sent it twice) or if the scheduled 
> PurgeService is already running it.  On top of that, we may need extra 
> consideration for HA setups where we currently only run it on the leader.  
> We should probably also have a to not schedule the PurgeService in ooize-site 
> for users who only want to run it manually.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2667) Optimize queries for DB export

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2667:
--

+1

> Optimize queries for DB export
> --
>
> Key: OOZIE-2667
> URL: https://issues.apache.org/jira/browse/OOZIE-2667
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2667.001.patch, OOZIE-2667.002.patch
>
>
> Right now OozieDBExportCLI uses named queries, some of which are sorting the 
> result which is not necessary. 
> They should be checked and replaced with faster queries when possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1978) Forkjoin validation code is ridiculously slow in some cases

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-1978:
--

I'll commit this tomorrow afternoon PST if nobody has any other comments.

> Forkjoin validation code is ridiculously slow in some cases
> ---
>
> Key: OOZIE-1978
> URL: https://issues.apache.org/jira/browse/OOZIE-1978
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk, 4.0.1
>Reporter: Robert Kanter
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-1978-001.patch, OOZIE-1978-002.patch, 
> OOZIE-1978-002.patch, OOZIE-1978-003.patch, OOZIE-1978-004.patch, 
> OOZIE-1978-005.patch, OOZIE-1978-006.patch, OOZIE-1978_wip.001.patch, 
> workflow.xml
>
>
> We've had a few users who have run into problems where submitting a workflow 
> appears to hang (in the case of a subworkflow, it's similar but stuck in 
> PREP).  It turns out that if you wait long enough, it will actually go 
> through and the workflow will run normally.  The problem is that the forkjoin 
> validation code is taking a really long time.
> The attached example has a series of 20 forks where each fork has 6 actions 
> (it's based on an actual workflow, but all of the names were changed and the 
> actions were all replaced by simple shell actions).  One of our support guys 
> said it took 1-2 hours , but on my computer it was taking {color:red}*15+ 
> hours*{color} (I had to cancel it)
> While this example doesn't have any nested forks, those can also take a long 
> time too.
> It's easy to verify that it's the forkjoin validation code that's taking so 
> long by looking at a jstack of the Oozie server and seeing deep recursive 
> calls to 
> {{org.apache.oozie.workflow.lite.LiteWorkflowAppParser.validateForkJoin}}.  I 
> also noticed a lot of sitting around in calls LinkedList.contains.  
> I think we have 3 options:
> # See if we can make the existing code faster somehow.  Perhaps there's a way 
> to parallelize it?  Maybe there's some redundant checking that we can 
> identify and skip? Change some data structures? etc
> # See if we can write a new way to do this validation.  I had originally 
> completely rewritten this code a while ago, and we've since made a few fixes 
> to catch edge cases and things.  Perhaps it needs another rewrite?
> # Try to identify when it's taking a long time and at least let the user know 
> what's happening or something.  Right now, it just appears that the Oozie CLI 
> has hung and the job doesn't show up in the Oozie server.  Most users aren't 
> going to wait more than a minute or two.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-1986) Add findbugs report to pre-commit build

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-1986:
-
Description: 
Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
build generate a findbugs report.  It should probably before and after the 
patch and only complain it there are more after.  And it should link to the 
report.  Ideally, this would do some kind of diff (like Hadoop does) so it's 
easy to identify the new findbugs items.

You can generate the findbugs reports by running:
{noformat}
mvn verify -DskipTests
{noformat}
This also runs checkstyle

  was:
Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
build generate a findbugs report.  It should probably before and after the 
patch and only complain it there are more after.  And it should link to the 
report.

You can generate the findbugs reports by running:
{noformat}
mvn verify -DskipTests
{noformat}
This also runs checkstyle


> Add findbugs report to pre-commit build
> ---
>
> Key: OOZIE-1986
> URL: https://issues.apache.org/jira/browse/OOZIE-1986
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: Robert Kanter
>
> Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
> build generate a findbugs report.  It should probably before and after the 
> patch and only complain it there are more after.  And it should link to the 
> report.  Ideally, this would do some kind of diff (like Hadoop does) so it's 
> easy to identify the new findbugs items.
> You can generate the findbugs reports by running:
> {noformat}
> mvn verify -DskipTests
> {noformat}
> This also runs checkstyle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2572) SLA DURATION miss not shown when job is running for longer than expected time

[Purshotam Shah (JIRA)]

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

Purshotam Shah commented on OOZIE-2572:
---

Committed to trunk.

> SLA DURATION miss not shown when job is running for longer than expected time
> -
>
> Key: OOZIE-2572
> URL: https://issues.apache.org/jira/browse/OOZIE-2572
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 4.3.0
>
> Attachments: OOZIE-2572-1.patch, OOZIE-2572-10.patch, 
> OOZIE-2572-11.patch, OOZIE-2572-2.patch, OOZIE-2572-3.patch, 
> OOZIE-2572-4.patch, OOZIE-2572-5.patch, OOZIE-2572-6.patch, 
> OOZIE-2572-7.patch, OOZIE-2572-8.patch, OOZIE-2572-9.patch
>
>
> If job is running for beyond expected duration, Oozie UI is not slowing SLA 
> for duration miss.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2572) SLA DURATION miss not shown when job is running for longer than expected time

[Purshotam Shah (JIRA)]

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

Purshotam Shah commented on OOZIE-2572:
---

+1

> SLA DURATION miss not shown when job is running for longer than expected time
> -
>
> Key: OOZIE-2572
> URL: https://issues.apache.org/jira/browse/OOZIE-2572
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 4.3.0
>
> Attachments: OOZIE-2572-1.patch, OOZIE-2572-10.patch, 
> OOZIE-2572-11.patch, OOZIE-2572-2.patch, OOZIE-2572-3.patch, 
> OOZIE-2572-4.patch, OOZIE-2572-5.patch, OOZIE-2572-6.patch, 
> OOZIE-2572-7.patch, OOZIE-2572-8.patch, OOZIE-2572-9.patch
>
>
> If job is running for beyond expected duration, Oozie UI is not slowing SLA 
> for duration miss.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-2661:
---
Priority: Major  (was: Minor)

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [SCOPE] Oozie 4.3.0 Release

[Robert Kanter]

Abhishek,

You don't have git permissions to create the release branch.  I can take
care of that on Thursday if you want.


- Robert

On Tue, Sep 20, 2016 at 1:30 PM, Abhishek Bafna 
wrote:

> Hello All,
>
> I think we can create the new branch by Thursday (IST) and update version
> for new branch and master. If we have any important pending Jira's by then
> we will commit them to both new branch and master.
>
> I will start working on the next steps for release from release doc.
> https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release <
> https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release>
>
> Please do provide if you have any feedback or suggestion.
>
> Thanks,
> Abhishek
> > On Sep 20, 2016, at 12:52 AM, Rohini Palaniswamy <
> rohini.adi...@gmail.com> wrote:
> >
> > Sorry Abhishek for the long delay. Was on vacation and then busy catching
> > up with stuff. I did review a bunch of patches today which were marked
> > 4.3.0 and Patch Available apart from those which Robert or others have
> > already not commented on. Skipping those as they have better context. Tag
> > my name if there is something else that needs to be looked at.
> >
> > Regards,
> > Rohini
> >
> > On Mon, Sep 19, 2016 at 6:33 AM, Abhishek Bafna 
> > wrote:
> >
> >> Hello Robert, Rohini, Purshotam, Jaydeep
> >>
> >> As we discussed earlier, will be bumping the priority of some Jira's to
> >> 'blocker' for to be included into Oozie 4.3.0 release. We will try to
> >> complete as much possible out of that. (It would to good complete all.)
> >>
> >> @All, If I miss something, Please do priorities or send a message here.
> >>
> >> Thanks a lot for all the efforts and time we have put in last few weeks.
> >>
> >> Thanks,
> >> Abhishek
> >>> On Sep 8, 2016, at 10:14 AM, Abhishek Bafna 
> >> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> It has been a long time since we started the scope discussion for the
> >> Oozie-4.3.0 release.
> >>> Since then a lot of patches got reviewed and committed and I would to
> >> thank each one you for contributing your efforts for that.
> >>>
> >>> I think we should move to the next stage and go into blocker only mode
> >> from next week (one week). After that 7-10 days for preparing and
> >> completing release condidate.
> >>>
> >>> We did plan to update some of the old tech and some of them are still
> >> pending for review. If can spend time into reviewing them, it would be
> >> good, else we might have to move without them.
> >>>
> >>> There are also some good to have patches available for review and
> >> commit, I will bump up the priority for them. If I miss something,
> please
> >> feel free to do the same.
> >>>
> >>> Regards,
> >>> Abhishek
> >>>
>  On Aug 31, 2016, at 2:30 PM, Abhishek Bafna 
> >> wrote:
> 
>  Hi All,
> 
>  Can we please look into these upgrade related bugs?
> 
>  ActiveMQ https://issues.apache.org/jira/browse/OOZIE-2552
>  HttpClient   https://issues.apache.org/jira/browse/OOZIE-2538
>  OpenJPA  https://issues.apache.org/jira/browse/OOZIE-2488
>  Curator  https://issues.apache.org/jira/browse/OOZIE-2231
>  Hive https://issues.apache.org/jira/browse/OOZIE-2613
> 
>  Are the current patches good and feedback if there is any.
> 
>  Also, If we can do some reviews collectively.
> 
>  Thanks,
>  Abhishek
> 
> > On Aug 27, 2016, at 1:14 AM, Abhishek Bafna 
> >> wrote:
> >
> > Hello All,
> >
> > How is it looking now?
> >
> > I think we should move to blocker and critical patch mode. If
> >> required, we can take couple of days extra there.
> >
> > ~Abhishek
> >> On Aug 19, 2016, at 11:31 AM, Abhishek Bafna 
> >> wrote:
> >>
> >> Sure Robert. We can use some more time.
> >>
> >> ~Abhishek
> >>> On Aug 19, 2016, at 7:13 AM, Robert Kanter 
> >> wrote:
> >>>
> >>> Do you think we could wait one more week?  I've been really
> hammered
> >> with
> >>> some other work and there's more that I'd like to review here that
> I
> >>> haven't been able to get to.
> >>>
> >>> thanks
> >>> - Robert
> >>>
> >>> On Fri, Aug 12, 2016 at 2:30 AM, Abhishek Bafna <
> >> bafna.i...@gmail.com>
> >>> wrote:
> >>>
>  Sure. I guess we can one extra week and complete some more work.
>  Thanks everyone for responding.
> 
>  ~Abhishek
> > On Aug 12, 2016, at 2:46 PM, Purshotam Shah <
> >> purus...@yahoo-inc.com.INVALID>
>  wrote:
> >
> > Yes. I also have some pending patches.
> >
> > On Friday, August 12, 2016 2:11 AM, Robert Kanter <
>  rkan...@cloudera.com> wrote:
> >
> >
> > Ya, I could use some more time as well.  I have some deadlines
> >> early next
> > week, which has kept me from doing more reviews.
> >
> > thanks
> > - Robert
> 

Re: [SCOPE] Oozie 4.3.0 Release

[Abhishek Bafna]

Hello All,

I think we can create the new branch by Thursday (IST) and update version for 
new branch and master. If we have any important pending Jira's by then we will 
commit them to both new branch and master.

I will start working on the next steps for release from release doc.
https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release 


Please do provide if you have any feedback or suggestion.

Thanks,
Abhishek
> On Sep 20, 2016, at 12:52 AM, Rohini Palaniswamy  
> wrote:
> 
> Sorry Abhishek for the long delay. Was on vacation and then busy catching
> up with stuff. I did review a bunch of patches today which were marked
> 4.3.0 and Patch Available apart from those which Robert or others have
> already not commented on. Skipping those as they have better context. Tag
> my name if there is something else that needs to be looked at.
> 
> Regards,
> Rohini
> 
> On Mon, Sep 19, 2016 at 6:33 AM, Abhishek Bafna 
> wrote:
> 
>> Hello Robert, Rohini, Purshotam, Jaydeep
>> 
>> As we discussed earlier, will be bumping the priority of some Jira's to
>> 'blocker' for to be included into Oozie 4.3.0 release. We will try to
>> complete as much possible out of that. (It would to good complete all.)
>> 
>> @All, If I miss something, Please do priorities or send a message here.
>> 
>> Thanks a lot for all the efforts and time we have put in last few weeks.
>> 
>> Thanks,
>> Abhishek
>>> On Sep 8, 2016, at 10:14 AM, Abhishek Bafna 
>> wrote:
>>> 
>>> Hi All,
>>> 
>>> It has been a long time since we started the scope discussion for the
>> Oozie-4.3.0 release.
>>> Since then a lot of patches got reviewed and committed and I would to
>> thank each one you for contributing your efforts for that.
>>> 
>>> I think we should move to the next stage and go into blocker only mode
>> from next week (one week). After that 7-10 days for preparing and
>> completing release condidate.
>>> 
>>> We did plan to update some of the old tech and some of them are still
>> pending for review. If can spend time into reviewing them, it would be
>> good, else we might have to move without them.
>>> 
>>> There are also some good to have patches available for review and
>> commit, I will bump up the priority for them. If I miss something, please
>> feel free to do the same.
>>> 
>>> Regards,
>>> Abhishek
>>> 
 On Aug 31, 2016, at 2:30 PM, Abhishek Bafna 
>> wrote:
 
 Hi All,
 
 Can we please look into these upgrade related bugs?
 
 ActiveMQ https://issues.apache.org/jira/browse/OOZIE-2552
 HttpClient   https://issues.apache.org/jira/browse/OOZIE-2538
 OpenJPA  https://issues.apache.org/jira/browse/OOZIE-2488
 Curator  https://issues.apache.org/jira/browse/OOZIE-2231
 Hive https://issues.apache.org/jira/browse/OOZIE-2613
 
 Are the current patches good and feedback if there is any.
 
 Also, If we can do some reviews collectively.
 
 Thanks,
 Abhishek
 
> On Aug 27, 2016, at 1:14 AM, Abhishek Bafna 
>> wrote:
> 
> Hello All,
> 
> How is it looking now?
> 
> I think we should move to blocker and critical patch mode. If
>> required, we can take couple of days extra there.
> 
> ~Abhishek
>> On Aug 19, 2016, at 11:31 AM, Abhishek Bafna 
>> wrote:
>> 
>> Sure Robert. We can use some more time.
>> 
>> ~Abhishek
>>> On Aug 19, 2016, at 7:13 AM, Robert Kanter 
>> wrote:
>>> 
>>> Do you think we could wait one more week?  I've been really hammered
>> with
>>> some other work and there's more that I'd like to review here that I
>>> haven't been able to get to.
>>> 
>>> thanks
>>> - Robert
>>> 
>>> On Fri, Aug 12, 2016 at 2:30 AM, Abhishek Bafna <
>> bafna.i...@gmail.com>
>>> wrote:
>>> 
 Sure. I guess we can one extra week and complete some more work.
 Thanks everyone for responding.
 
 ~Abhishek
> On Aug 12, 2016, at 2:46 PM, Purshotam Shah <
>> purus...@yahoo-inc.com.INVALID>
 wrote:
> 
> Yes. I also have some pending patches.
> 
> On Friday, August 12, 2016 2:11 AM, Robert Kanter <
 rkan...@cloudera.com> wrote:
> 
> 
> Ya, I could use some more time as well.  I have some deadlines
>> early next
> week, which has kept me from doing more reviews.
> 
> thanks
> - Robert
> 
> On Thu, Aug 11, 2016 at 11:04 AM, jaydeep vishwakarma <
> jaydeepma...@gmail.com> wrote:
> 
>> Let see if we can wait for another week. So we can merge few more
 important
>> jiras.  Few of them I personally want to get reviewed and merged.
>> 
>> Regards,
>> Jaydeep
>> 
>> On Thu, Aug 11, 2016 at 4:09 PM, Abhishek Bafna <
>> bafna.i...@gmail.com>
>> 

[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2675:
---

Thanks [~rohini] for the review and committing it.

> Drop support for hadoop 0.23
> 
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2569) Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2569:
---

Thanks [~rohini] for the review and committing it.

> Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher 
> ---
>
> Key: OOZIE-2569
> URL: https://issues.apache.org/jira/browse/OOZIE-2569
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2569-00.patch, OOZIE-2569-02.patch, 
> OOZIE-2569-03.patch
>
>
> Oozie Spark action requires yarn-site, core-site, hdfs-site and mapred-site 
> to be present in the classpath for launching the spark applications. 
> Currently we manually copy these files into oozie spark sharelib.
> Until it is fixed through the spark, we can copy the 
> {{oozie.action.conf.xml}} file as yarn-site, core-site, hdfs-site and 
> mapred-site, which will avoid manual steps of copying those files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2498) Oozie CallerId configuration for downstream components

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2498:
---

Thanks [~rohini] for the review and committing it.

> Oozie CallerId configuration for downstream components 
> ---
>
> Key: OOZIE-2498
> URL: https://issues.apache.org/jira/browse/OOZIE-2498
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>  Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2498-01.patch
>
>
> The idea is to add callerId to every component, so we can track the chain of 
> application which cause the underlining operation. A typical chain is 
> Oozie->Pig|Hive->Tez->Hdfs. With proper callerId logging, we can trace Hdfs 
> operation back to Oozie workflow which triggers it.
> For Oozie, It will pass its workflow id as callerId to other components 
> (Pig/Hive).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-2661:
---
Attachment: OOZIE-2661-3.patch

Triggering jenkins again.

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-2661:
---
Attachment: (was: OOZIE-2661-3.patch)

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2678:
--
Attachment: OOZIE-2678-01.patch

Added the tez application tags for Shell and Java action as well.
Previously, Shell action did not have even yarn tags added, included them as 
well.

> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2678-00.patch, OOZIE-2678-01.patch
>
>
>  OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2678:
---

Realized it would be good to add for Java and shell actions as well. Have seen 
cases of people trying to run pig/hive jobs from those for reasons like 
submitting jobs in a for loop with different parameters.

Can you also pick up OOZIE-2194 for Spark action and add the spark tag for 
spark, java and shell actions.

> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2678-00.patch
>
>
>  OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2678:
---

[~rohini] Attached a patch. Please review it. Thanks.

> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2678-00.patch
>
>
>  OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2613:
---

Ping: [~rohini] and [~rkanter]

> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, 
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, 
> OOZIE-2613-06.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2582) Populating external child Ids for action failures

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2582:
---

Thanks for the feedback [~rohini]. Attached the updated patch here and RB as 
well.

> Populating external child Ids for action failures
> -
>
> Key: OOZIE-2582
> URL: https://issues.apache.org/jira/browse/OOZIE-2582
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, 
> OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, 
> OOZIE-2582-05.patch, OOZIE-2582-06.patch
>
>
> Currently Oozie external child ids are populated into workflow bean, when the 
> job/action completes successfully. It should populate external child ids in 
> case of job failures as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 49074: OOZIE-2582: Populating external child Ids for action failures

[Abhishek Bafna]

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

(Updated Sept. 20, 2016, 7:21 p.m.)


Review request for oozie.


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


Repository: oozie-git


Description
---

Currently Oozie external child ids are populated into workflow bean, when the 
job/action completes successfully. It should populate external child ids in 
case of job failures as well.


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/DistcpActionExecutor.java 
96726da 
  core/src/main/java/org/apache/oozie/action/hadoop/Hive2ActionExecutor.java 
b5b1bf9 
  core/src/main/java/org/apache/oozie/action/hadoop/HiveActionExecutor.java 
c74e9e6 
  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
ad07b57 
  core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
15a641b 
  core/src/main/java/org/apache/oozie/action/hadoop/SqoopActionExecutor.java 
6813a37 
  examples/src/main/apps/hive/script.q 3abc757 
  sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java 
6ac5ad6 
  sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java 
8de3766 
  
sharelib/hive/src/test/java/org/apache/oozie/action/hadoop/TestHiveActionExecutor.java
 b966d4b 
  sharelib/hive/src/test/java/org/apache/oozie/action/hadoop/TestHiveMain.java 
d72e298 
  
sharelib/hive2/src/test/java/org/apache/oozie/action/hadoop/TestHive2ActionExecutor.java
 5963e42 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
054f8ea 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/ShellMain.java 
5e80d00 
  sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java 
44debbd 
  
sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java
 a5291d9 
  sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java 
38e8e8c 
  sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java 
623fd2e 
  
sharelib/sqoop/src/test/java/org/apache/oozie/action/hadoop/TestSqoopActionExecutor.java
 6474092 

Diff: https://reviews.apache.org/r/49074/diff/


Testing
---


Thanks,

Abhishek Bafna

[jira] [Commented] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2661:
--

Testing JIRA OOZIE-2661

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1807
.Tests failed: 1
.Tests errors: 45

.The patch failed the following testcases:

.  testCoordinatorActionEvent(org.apache.oozie.event.TestEventGeneration)

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


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


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

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

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

Changes:

[purushah] OOZIE-2672 SLA periodic update does not remove job from map if job is

--
[...truncated 6322 lines...]
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attac

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

[Apache Jenkins Server]

See 

--
[...truncated 6274 lines...]
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[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.44/bin/apache-tomcat-6.0.44.tar.gz
  [get] To: 

[jira] [Commented] (OOZIE-2672) SLA periodic update does not remove job from map if job is removed from database

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2672:


Thanks Puru.

> SLA periodic update does not remove job from map if job is removed from 
> database
> 
>
> Key: OOZIE-2672
> URL: https://issues.apache.org/jira/browse/OOZIE-2672
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 4.3.0
>
> Attachments: OOZIE-2672-1.patch
>
>
> When we query for a job id which does not exist in database, it throws an 
> exception. We should catch this exception and remote the job from sla map.
> {code}
> 2016-09-15 03:01:56,256 ERROR SLACalculatorMemory:517 [pool-1-thread-17] - 
> SERVER[wf152] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[1514510-160812072515385-oozie_JB-C@4] ACTION[-] Exception in SLA 
> processing for job [1514510-160812072515385-oozie_JB-C@4]
> org.apache.oozie.executor.jpa.JPAExecutorException: E0604: Job does not exist 
> [select w.eventProcessed, w.lastModifiedTS from SLASummaryBean w where 
> w.jobId = :id]
> at 
> org.apache.oozie.executor.jpa.SLASummaryQueryExecutor.get(SLASummaryQueryExecutor.java:148)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateJobSla(SLACalculatorMemory.java:240)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateAllSlaStatus(SLACalculatorMemory.java:345)
> at org.apache.oozie.sla.service.SLAService$SLAWorker.run(SLAService.java:131)
> at org.apache.oozie.service.SchedulerService$2.run(SchedulerService.java:175)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Thank you [~puru] for pointing this out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2672) SLA periodic update does not remove job from map if job is removed from database

[Purshotam Shah (JIRA)]

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

Purshotam Shah commented on OOZIE-2672:
---

Committed to trunk. Test failure is not related.

> SLA periodic update does not remove job from map if job is removed from 
> database
> 
>
> Key: OOZIE-2672
> URL: https://issues.apache.org/jira/browse/OOZIE-2672
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 4.3.0
>
> Attachments: OOZIE-2672-1.patch
>
>
> When we query for a job id which does not exist in database, it throws an 
> exception. We should catch this exception and remote the job from sla map.
> {code}
> 2016-09-15 03:01:56,256 ERROR SLACalculatorMemory:517 [pool-1-thread-17] - 
> SERVER[wf152] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[1514510-160812072515385-oozie_JB-C@4] ACTION[-] Exception in SLA 
> processing for job [1514510-160812072515385-oozie_JB-C@4]
> org.apache.oozie.executor.jpa.JPAExecutorException: E0604: Job does not exist 
> [select w.eventProcessed, w.lastModifiedTS from SLASummaryBean w where 
> w.jobId = :id]
> at 
> org.apache.oozie.executor.jpa.SLASummaryQueryExecutor.get(SLASummaryQueryExecutor.java:148)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateJobSla(SLACalculatorMemory.java:240)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateAllSlaStatus(SLACalculatorMemory.java:345)
> at org.apache.oozie.sla.service.SLAService$SLAWorker.run(SLAService.java:131)
> at org.apache.oozie.service.SchedulerService$2.run(SchedulerService.java:175)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Thank you [~puru] for pointing this out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2672) SLA periodic update does not remove job from map if job is removed from database

[Purshotam Shah (JIRA)]

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

Purshotam Shah updated OOZIE-2672:
--
Fix Version/s: 4.3.0

> SLA periodic update does not remove job from map if job is removed from 
> database
> 
>
> Key: OOZIE-2672
> URL: https://issues.apache.org/jira/browse/OOZIE-2672
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 4.3.0
>
> Attachments: OOZIE-2672-1.patch
>
>
> When we query for a job id which does not exist in database, it throws an 
> exception. We should catch this exception and remote the job from sla map.
> {code}
> 2016-09-15 03:01:56,256 ERROR SLACalculatorMemory:517 [pool-1-thread-17] - 
> SERVER[wf152] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[1514510-160812072515385-oozie_JB-C@4] ACTION[-] Exception in SLA 
> processing for job [1514510-160812072515385-oozie_JB-C@4]
> org.apache.oozie.executor.jpa.JPAExecutorException: E0604: Job does not exist 
> [select w.eventProcessed, w.lastModifiedTS from SLASummaryBean w where 
> w.jobId = :id]
> at 
> org.apache.oozie.executor.jpa.SLASummaryQueryExecutor.get(SLASummaryQueryExecutor.java:148)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateJobSla(SLACalculatorMemory.java:240)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateAllSlaStatus(SLACalculatorMemory.java:345)
> at org.apache.oozie.sla.service.SLAService$SLAWorker.run(SLAService.java:131)
> at org.apache.oozie.service.SchedulerService$2.run(SchedulerService.java:175)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Thank you [~puru] for pointing this out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2672) SLA periodic update does not remove job from map if job is removed from database

[Purshotam Shah (JIRA)]

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

Purshotam Shah commented on OOZIE-2672:
---

+1

> SLA periodic update does not remove job from map if job is removed from 
> database
> 
>
> Key: OOZIE-2672
> URL: https://issues.apache.org/jira/browse/OOZIE-2672
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2672-1.patch
>
>
> When we query for a job id which does not exist in database, it throws an 
> exception. We should catch this exception and remote the job from sla map.
> {code}
> 2016-09-15 03:01:56,256 ERROR SLACalculatorMemory:517 [pool-1-thread-17] - 
> SERVER[wf152] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[1514510-160812072515385-oozie_JB-C@4] ACTION[-] Exception in SLA 
> processing for job [1514510-160812072515385-oozie_JB-C@4]
> org.apache.oozie.executor.jpa.JPAExecutorException: E0604: Job does not exist 
> [select w.eventProcessed, w.lastModifiedTS from SLASummaryBean w where 
> w.jobId = :id]
> at 
> org.apache.oozie.executor.jpa.SLASummaryQueryExecutor.get(SLASummaryQueryExecutor.java:148)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateJobSla(SLACalculatorMemory.java:240)
> at 
> org.apache.oozie.sla.SLACalculatorMemory.updateAllSlaStatus(SLACalculatorMemory.java:345)
> at org.apache.oozie.sla.service.SLAService$SLAWorker.run(SLAService.java:131)
> at org.apache.oozie.service.SchedulerService$2.run(SchedulerService.java:175)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Thank you [~puru] for pointing this out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2606) Set spark.yarn.jars to fix Spark 2.0 with Oozie

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2606:
---

Another thing is that you need to skip setting spark.yarn.jars if 
spark.yarn.archive is set by the user or is present in spark-defaults.conf

> Set spark.yarn.jars to fix Spark 2.0 with Oozie
> ---
>
> Key: OOZIE-2606
> URL: https://issues.apache.org/jira/browse/OOZIE-2606
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Jonathan Kelly
>Assignee: Satish Subhashrao Saley
>  Labels: spark, spark2.0.0
> Fix For: 4.3.0
>
> Attachments: OOZIE-2606-2.patch, OOZIE-2606.patch
>
>
> Oozie adds all of the jars in the Oozie Spark sharelib to the 
> DistributedCache such that all jars will be present in the current working 
> directory of the YARN container (as well as in the container classpath). 
> However, this is not quite enough to make Spark 2.0 work, since Spark 2.0 by 
> default looks for the jars in assembly/target/scala-2.11/jars [1] (as if it 
> is a locally built distribution for development) and will not find them in 
> the current working directory.
> To fix this, we can set spark.yarn.jars to *.jar so that it finds the jars in 
> the current working directory rather than looking in the wrong place. [2]
> [1] 
> https://github.com/apache/spark/blob/v2.0.0-rc2/launcher/src/main/java/org/apache/spark/launcher/CommandBuilderUtils.java#L357
> [2] 
> https://github.com/apache/spark/blob/v2.0.0-rc2/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala#L476
> Note: This property will be ignored by Spark 1.x.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2678:
---

Testcases passes locally.

> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2678-00.patch
>
>
>  OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2678:
---

Jenkins failed to add comment into Jira.

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

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

mv: cannot stat 'jira-cli-2.6.0': No such file or directory
chmod: cannot access 
'/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/test-patch/tools/jira-cli/jira.sh':
 No such file or directory
Adding comment to JIRA
bin/test-patch: line 124: 
/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/test-patch/tools/jira-cli/jira.sh:
 No such file or directory
{noformat}

Copy-Pasting Jenkins Report:
{noformat}

Testing JIRA OOZIE-2678

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 1807
Tests failed: 1
Tests errors: 0

The patch failed the following testcases:

  testSingleRecord(org.apache.oozie.servlet.TestBulkMonitorWebServiceAPI)

+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)
{noformat}

> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2678-00.patch
>
>
>  OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2582) Populating external child Ids for action failures

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2582:
---

Testcase passes locally.

> Populating external child Ids for action failures
> -
>
> Key: OOZIE-2582
> URL: https://issues.apache.org/jira/browse/OOZIE-2582
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, 
> OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, 
> OOZIE-2582-05.patch, OOZIE-2582-06.patch
>
>
> Currently Oozie external child ids are populated into workflow bean, when the 
> job/action completes successfully. It should populate external child ids in 
> case of job failures as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (OOZIE-2606) Set spark.yarn.jars to fix Spark 2.0 with Oozie

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2606:
--
Comment: was deleted

(was: regarding to 3) Spark has 
[VersionUtils|https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/util/VersionUtils.scala]
 but only in Spark2.0. I couldn't find anything before.)

> Set spark.yarn.jars to fix Spark 2.0 with Oozie
> ---
>
> Key: OOZIE-2606
> URL: https://issues.apache.org/jira/browse/OOZIE-2606
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Jonathan Kelly
>Assignee: Satish Subhashrao Saley
>  Labels: spark, spark2.0.0
> Fix For: 4.3.0
>
> Attachments: OOZIE-2606-2.patch, OOZIE-2606.patch
>
>
> Oozie adds all of the jars in the Oozie Spark sharelib to the 
> DistributedCache such that all jars will be present in the current working 
> directory of the YARN container (as well as in the container classpath). 
> However, this is not quite enough to make Spark 2.0 work, since Spark 2.0 by 
> default looks for the jars in assembly/target/scala-2.11/jars [1] (as if it 
> is a locally built distribution for development) and will not find them in 
> the current working directory.
> To fix this, we can set spark.yarn.jars to *.jar so that it finds the jars in 
> the current working directory rather than looking in the wrong place. [2]
> [1] 
> https://github.com/apache/spark/blob/v2.0.0-rc2/launcher/src/main/java/org/apache/spark/launcher/CommandBuilderUtils.java#L357
> [2] 
> https://github.com/apache/spark/blob/v2.0.0-rc2/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala#L476
> Note: This property will be ignored by Spark 1.x.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2582) Populating external child Ids for action failures

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2582:
--

Testing JIRA OOZIE-2582

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 4 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: 1808
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  testRecovery(org.apache.oozie.action.hadoop.TestJavaActionExecutor)

{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/3302/

> Populating external child Ids for action failures
> -
>
> Key: OOZIE-2582
> URL: https://issues.apache.org/jira/browse/OOZIE-2582
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, 
> OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, 
> OOZIE-2582-05.patch, OOZIE-2582-06.patch
>
>
> Currently Oozie external child ids are populated into workflow bean, when the 
> job/action completes successfully. It should populate external child ids in 
> case of job failures as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

--
[...truncated 6322 lines...]
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run

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

[Apache Jenkins Server]

See 

--
[...truncated 9703 lines...]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 

  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz

[jira] [Commented] (OOZIE-2679) Decrease HttpClient library versions

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2679:
---

Thank you for the quick fix [~abhishekbafna]!
+1 (non-binding)
[~rkanter], [~puru], [~jaydeepvishwakarma], please review this.

> Decrease HttpClient library versions
> 
>
> Key: OOZIE-2679
> URL: https://issues.apache.org/jira/browse/OOZIE-2679
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2679.patch
>
>
> Version 4.4 of HttpClient has issued with Hadoop: HADOOP-11859 
> It will be fixed in Hadoop 2.8.0, until we use that we should use 4.3 of 
> HttpClient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2679) Decrease HttpClient library versions

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2679:
--
Attachment: OOZIE-2679.patch

> Decrease HttpClient library versions
> 
>
> Key: OOZIE-2679
> URL: https://issues.apache.org/jira/browse/OOZIE-2679
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2679.patch
>
>
> Version 4.4 of HttpClient has issued with Hadoop: HADOOP-11859 
> It will be fixed in Hadoop 2.8.0, until we use that we should use 4.3 of 
> HttpClient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2676:
---

Thanks [~gezapeti]. Will be uploading the patch with:

{code}
 4.3.3
 4.3.6
{code}

I have tested for these tests manually.

mvn clean test -Dtest=org.apache.oozie.client.* -Phadoop-2
mvn clean test -Dtest=org.apache.oozie.servlet.* -Phadoop-2
mvn clean test -Dtest=org.apache.oozie.action.hadoop.TestJavaActionExecutor 
-Phadoop-2 -pl core

mvn clean test -Dtest=org.apache.oozie.client.*
mvn clean test -Dtest=org.apache.oozie.servlet.* -pl core
mvn clean test -Dtest=org.apache.oozie.action.hadoop.TestJavaActionExecutor -pl 
core


> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2679) Decrease HttpClient library versions

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2679:
--
Description: 
Version 4.4 of HttpClient has issued with Hadoop: HADOOP-11859 
It will be fixed in Hadoop 2.8.0, until we use that we should use 4.3 of 
HttpClient.


  was:Version 4.4 of HttpClient causes HADOOP-


> Decrease HttpClient library versions
> 
>
> Key: OOZIE-2679
> URL: https://issues.apache.org/jira/browse/OOZIE-2679
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Version 4.4 of HttpClient has issued with Hadoop: HADOOP-11859 
> It will be fixed in Hadoop 2.8.0, until we use that we should use 4.3 of 
> HttpClient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2679) Decrease HttpClient library versions

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2679:
--
Priority: Blocker  (was: Major)

> Decrease HttpClient library versions
> 
>
> Key: OOZIE-2679
> URL: https://issues.apache.org/jira/browse/OOZIE-2679
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Version 4.4 of HttpClient causes HADOOP-



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OOZIE-2679) Decrease HttpClient library versions

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna reassigned OOZIE-2679:
-

Assignee: Abhishek Bafna

> Decrease HttpClient library versions
> 
>
> Key: OOZIE-2679
> URL: https://issues.apache.org/jira/browse/OOZIE-2679
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
>
> Version 4.4 of HttpClient causes HADOOP-



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2194) oozie job -kill doesn't work with spark action

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2194:
---

Previously oozie used application tags only to deal with AM restarts and RM 
non-work preserving restarts which may launch duplicate AMs. OOZIE-2243 used it 
to also kill if user issued a kill. Previously it was relying only on the 
shutdown hooks of Pig and Hive for the launched child jobs to be killed. 
Problem was that shutdown hook might not be executed in some scenarios and it 
did not kill jobs launched by users from java actions as they usually don't 
bother killing jobs in finally or shutdown hooks.

Even with the application tags, shutdown hook which calls application specific 
kill API is useful in following scenarios
- Give child jobs a chance to do graceful shutdown/kill and write down any 
required history. 
- In case of failures and no user kill, the application will continue to 
run. So for cases like Tez which reuses applications to launch multiple DAGs, 
Pig needs to shutdown the application. Else it will be hanging around till the 
configured idle timeout. Not sure how that works with Spark


> oozie job -kill doesn't work with spark action
> --
>
> Key: OOZIE-2194
> URL: https://issues.apache.org/jira/browse/OOZIE-2194
> Project: Oozie
>  Issue Type: Bug
>Reporter: Thomas Graves
>
> I was trying the spark action out with oozie and was able to launch fine. But 
> when I tried do use oozie job -kill it only killed the launcher job and not 
> the spark application itself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2676:
---

Thank you for the help [~abhishekbafna]!
Tests are fine with the 4.3 versions of the libraries. 
I've created OOZIE-2679 to decrease the http client versions and after that 
this patch could be applied.

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 44204: OOZIE:2243 - Hadoop jobs doesnot get killed when coordinator action get killed

[Jaydeep Vishwakarma]

> On Sept. 19, 2016, 11:44 p.m., Rohini Palaniswamy wrote:
> > core/src/test/java/org/apache/hadoop/examples/SleepJob.java, lines 166-167
> > 
> >
> > Why is this required? Isn't core-site.xml a default resource?

It is default for the launcher job, But when launcher launches the child job it 
take the core-default and its ports are different. I verified same by debugging 
and the


> On Sept. 19, 2016, 11:44 p.m., Rohini Palaniswamy wrote:
> > core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java,
> >  line 548
> > 
> >
> > Assume.assumeTrue("Skip this test for Hadoop 1.x", 
> > HadoopShims.isYARN());

How does this work. Do you want me to replace this with  "if 
(HadoopShims.isYARN()) {". This test case will not work for 1.x. Please guide 
me.


- Jaydeep


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


On Aug. 27, 2016, 7:46 p.m., Jaydeep Vishwakarma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/44204/
> ---
> 
> (Updated Aug. 27, 2016, 7:46 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2243
> https://issues.apache.org/jira/browse/OOZIE-2243
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Whenever the coord action or workflow gets killed only the job that has error 
> gets killed while the other hadoop jobs keeps on running and only the 
> workflow status gets changed to killed.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> e546e77 
>   core/src/main/java/org/apache/oozie/action/hadoop/LauncherMapperHelper.java 
> ed06707 
>   
> core/src/main/java/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.java
>  1ea7097 
>   core/src/test/java/org/apache/hadoop/examples/SleepJob.java 8dec534 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> 5f9e29a 
>   
> hadooplibs/hadoop-utils-1/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java
>  dca7820 
>   
> hadooplibs/hadoop-utils-2/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java
>  ce8c14f 
>   
> hadooplibs/hadoop-utils-3/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java
>  94e01ea 
> 
> Diff: https://reviews.apache.org/r/44204/diff/
> 
> 
> Testing
> ---
> 
> done
> 
> 
> Thanks,
> 
> Jaydeep Vishwakarma
> 
>

[jira] [Created] (OOZIE-2679) Decrease HttpClient library versions

[Peter Cseh (JIRA)]

Peter Cseh created OOZIE-2679:
-

 Summary: Decrease HttpClient library versions
 Key: OOZIE-2679
 URL: https://issues.apache.org/jira/browse/OOZIE-2679
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Cseh
 Fix For: 4.3.0


Version 4.4 of HttpClient causes HADOOP-



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2676:
---

I think we can go with

{code}
 4.3.3
 4.3.6
{code}

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2676:
---

I am running the testcases with {{4.3.}} version. I was able to execute the 
{{TestWorkflowXClient}} for both the profiles. I will update the same soon. 
Thanks [~gezapeti].

{code}
 4.3
 4.3
{code}

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2606) Set spark.yarn.jars to fix Spark 2.0 with Oozie

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2606:
---

regarding to 3) Spark has 
[VersionUtils|https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/util/VersionUtils.scala]
 but only in Spark2.0. I couldn't find anything before.

> Set spark.yarn.jars to fix Spark 2.0 with Oozie
> ---
>
> Key: OOZIE-2606
> URL: https://issues.apache.org/jira/browse/OOZIE-2606
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Jonathan Kelly
>Assignee: Satish Subhashrao Saley
>  Labels: spark, spark2.0.0
> Fix For: 4.3.0
>
> Attachments: OOZIE-2606-2.patch, OOZIE-2606.patch
>
>
> Oozie adds all of the jars in the Oozie Spark sharelib to the 
> DistributedCache such that all jars will be present in the current working 
> directory of the YARN container (as well as in the container classpath). 
> However, this is not quite enough to make Spark 2.0 work, since Spark 2.0 by 
> default looks for the jars in assembly/target/scala-2.11/jars [1] (as if it 
> is a locally built distribution for development) and will not find them in 
> the current working directory.
> To fix this, we can set spark.yarn.jars to *.jar so that it finds the jars in 
> the current working directory rather than looking in the wrong place. [2]
> [1] 
> https://github.com/apache/spark/blob/v2.0.0-rc2/launcher/src/main/java/org/apache/spark/launcher/CommandBuilderUtils.java#L357
> [2] 
> https://github.com/apache/spark/blob/v2.0.0-rc2/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala#L476
> Note: This property will be ignored by Spark 1.x.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2634) Queue dump command message is confusing when the queue is empty

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2634:
---

I'm not sure the two extra lines are needed in the output, otherwise it looks 
great!
+1 (non-binding)
Thank you for the contribution [~andras.piros].

> Queue dump command message is confusing when the queue is empty
> ---
>
> Key: OOZIE-2634
> URL: https://issues.apache.org/jira/browse/OOZIE-2634
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Minor
>  Labels: newbie
> Fix For: 4.4.0
>
> Attachments: OOZIE-2634.001.patch, OOZIE-2634.002.patch, 
> OOZIE-2634.003.patch
>
>
> If the callable queue is empty, and you run the queue dump command, the 
> message says:
> {noformat}
> # oozie admin queuedump
> [Server Queue Dump]:
> Queue dump is null!
> **
> [Server Uniqueness Map Dump]:
> Uniqueness dump is null!
> {noformat}
> This message makes it sound like a bad thing, especially the exclamation 
> mark.  We should change the message to something more neutral and helpful, 
> like "The queue is empty" or something like that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2194) oozie job -kill doesn't work with spark action

[Thomas Graves (JIRA)]

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

Thomas Graves commented on OOZIE-2194:
--

Maybe I missed it but doesn't OOZIE-2243 use the yarn kill api?  Does the code 
from OOZIE-2243  only get run on a clean shutdown and not a hard kill then?  
Which is why the shutdown hook is required.

We are working on implementing the shutdown hook in Spark but unfortunately its 
not trivial so it taking longer then expected.

> oozie job -kill doesn't work with spark action
> --
>
> Key: OOZIE-2194
> URL: https://issues.apache.org/jira/browse/OOZIE-2194
> Project: Oozie
>  Issue Type: Bug
>Reporter: Thomas Graves
>
> I was trying the spark action out with oozie and was able to launch fine. But 
> when I tried do use oozie job -kill it only killed the launcher job and not 
> the spark application itself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OOZIE-2676) Make hadoop-2 as the default profile

[Peter Cseh (JIRA)]

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

Peter Cseh edited comment on OOZIE-2676 at 9/20/16 1:17 PM:


I managed to reproduce on the current master branch with no additional patches 
and running {code} mvn clean test -Dtest=TestWorkflowXClient -Phadoop-2 {code} 
All fail with similar error messages as in HADOOP-118589 and an NPE as a root 
cause.
I haven't checked all the failing tests, but all of them seems to talk to the 
Oozie server via Http.


was (Author: gezapeti):
I managed to reproduce on the current master branch with no additional patches 
and running {code} mvn clean test -Dtest=TestWorkflowXClient -Phadoop-2 {code} 
All fail with similar error messages as in HADOOP-118589 and an NPE as a root 
cause.

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2676:
---

I managed to reproduce on the current master branch with no additional patches 
and running {code} mvn clean test -Dtest=TestWorkflowXClient -Phadoop-2 {code} 
All fail with similar error messages as in HADOOP-118589 and an NPE as a root 
cause.

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2676:
---

[~gezapeti] Are you using the attached patch or made some more changes? I 
wanted to try it out. If there is any more information, please do provide. 
Thanks.


> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2194) oozie job -kill doesn't work with spark action

[Thomas Graves (JIRA)]

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

Thomas Graves commented on OOZIE-2194:
--

application tags should already be supported, see docs at 
http://spark.apache.org/docs/latest/running-on-yarn.html spark.yarn.tags  .

> oozie job -kill doesn't work with spark action
> --
>
> Key: OOZIE-2194
> URL: https://issues.apache.org/jira/browse/OOZIE-2194
> Project: Oozie
>  Issue Type: Bug
>Reporter: Thomas Graves
>
> I was trying the spark action out with oozie and was able to launch fine. But 
> when I tried do use oozie job -kill it only killed the launcher job and not 
> the spark application itself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2676:
---

It seems like these client tests were broken with hadoop-2 profile since 
OOZIE-2538. It looks like we’re hitting HADOOP-11859
It will be fixed in Hadoop 2.8.0, we might want to revert OOZIE-2538 until 
that. 


> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2678:
--
Attachment: OOZIE-2678-00.patch

> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2678-00.patch
>
>
>  OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2582) Populating external child Ids for action failures

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2582:
--
Attachment: OOZIE-2582-06.patch

> Populating external child Ids for action failures
> -
>
> Key: OOZIE-2582
> URL: https://issues.apache.org/jira/browse/OOZIE-2582
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, 
> OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, 
> OOZIE-2582-05.patch, OOZIE-2582-06.patch
>
>
> Currently Oozie external child ids are populated into workflow bean, when the 
> job/action completes successfully. It should populate external child ids in 
> case of job failures as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna reassigned OOZIE-2678:
-

Assignee: Abhishek Bafna

> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
>
>  OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) 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 -c core.askpass=true 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 3ad35372e20d9e995688d52548f7858537f22be3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3ad35372e20d9e995688d52548f7858537f22be3
 > git rev-list 3ad35372e20d9e995688d52548f7858537f22be3 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson6543745442741263099.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 --:--:--  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:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:31 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:32 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:33 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:34 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:35 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:36 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:37 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:38 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:39 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:40 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:41 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:42 --:--:-- 0
  0 00 00   

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

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) 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 -c core.askpass=true 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 3ad35372e20d9e995688d52548f7858537f22be3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3ad35372e20d9e995688d52548f7858537f22be3
 > git rev-list 3ad35372e20d9e995688d52548f7858537f22be3 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson7502412421433405413.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 --:--:--  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:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:31 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:32 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:33 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:34 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:35 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:36 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:37 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:38 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:39 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:40 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:41 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:42 --:--:-- 0
  0 00 00   

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

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) 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 -c core.askpass=true 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 3ad35372e20d9e995688d52548f7858537f22be3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3ad35372e20d9e995688d52548f7858537f22be3
 > git rev-list 3ad35372e20d9e995688d52548f7858537f22be3 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson5341455163761291405.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 --:--:--  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:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:31 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:32 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:33 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:34 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:35 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:36 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:37 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:38 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:39 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:40 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:41 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:42 --:--:-- 0
  0 00 00   

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

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) 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 -c core.askpass=true 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 3ad35372e20d9e995688d52548f7858537f22be3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3ad35372e20d9e995688d52548f7858537f22be3
 > git rev-list 3ad35372e20d9e995688d52548f7858537f22be3 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson566479412749625207.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 --:--:--  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:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:31 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:32 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:33 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:34 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:35 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:36 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:37 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:38 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:39 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:40 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:41 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:42 --:--:-- 0
  0 00 00

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

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) 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 -c core.askpass=true 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 3ad35372e20d9e995688d52548f7858537f22be3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3ad35372e20d9e995688d52548f7858537f22be3
 > git rev-list 3ad35372e20d9e995688d52548f7858537f22be3 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson3372599062906733421.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 --:--:--  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:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:31 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:32 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:33 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:34 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:35 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:36 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:37 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:38 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:39 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:40 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:41 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:42 --:--:-- 0
  0 00 00   

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

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) 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 -c core.askpass=true 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 3ad35372e20d9e995688d52548f7858537f22be3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3ad35372e20d9e995688d52548f7858537f22be3
 > git rev-list 3ad35372e20d9e995688d52548f7858537f22be3 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson4368219850375277845.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 --:--:-- --:--:-- --:--:-- 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:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:31 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:32 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:33 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:34 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:35 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:36 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:37 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:38 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:39 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:40 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:41 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:42 --:--:-- 0
  0 00 00   

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

[Apache Jenkins Server]

See 

--
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) 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 -c core.askpass=true 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 3ad35372e20d9e995688d52548f7858537f22be3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3ad35372e20d9e995688d52548f7858537f22be3
 > git rev-list 3ad35372e20d9e995688d52548f7858537f22be3 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson1114538867346909050.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 --:--:-- --:--:-- --:--:-- 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:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:31 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:32 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:33 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:34 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:35 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:36 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:37 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:38 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:

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

[Apache Jenkins Server]

See 

--
[...truncated 9349 lines...]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[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 

[WARNING] Assembly file: 

 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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[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 

[INFO] Copying 3 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] 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[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.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[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 

[INFO] Copying 3 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 

[INFO] Copying 3 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 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 

  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz

[jira] [Updated] (OOZIE-2634) Queue dump command message is confusing when the queue is empty

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2634:

Attachment: OOZIE-2634.003.patch

Some lines were too long.

All the tests have been run locally - and passed. So I think there're some 
flaky tests that fail from time to time.

> Queue dump command message is confusing when the queue is empty
> ---
>
> Key: OOZIE-2634
> URL: https://issues.apache.org/jira/browse/OOZIE-2634
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Minor
>  Labels: newbie
> Fix For: 4.4.0
>
> Attachments: OOZIE-2634.001.patch, OOZIE-2634.002.patch, 
> OOZIE-2634.003.patch
>
>
> If the callable queue is empty, and you run the queue dump command, the 
> message says:
> {noformat}
> # oozie admin queuedump
> [Server Queue Dump]:
> Queue dump is null!
> **
> [Server Uniqueness Map Dump]:
> Uniqueness dump is null!
> {noformat}
> This message makes it sound like a bad thing, especially the exclamation 
> mark.  We should change the message to something more neutral and helpful, 
> like "The queue is empty" or something like that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)