[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (56 issues) Subscriber: ooziedaily Key Summary OOZIE-2390 Rerun with failed option removing completed output data https://issues.apache.org/jira/browse/OOZIE-2390 OOZIE-2380 Oozie Hive action failed with wrong tmp path https://issues.apache.org/jira/browse/OOZIE-2380 OOZIE-2362 SQL injection in BulkJPAExecutor https://issues.apache.org/jira/browse/OOZIE-2362 OOZIE-2357 CoordRerun should queue CoordPushDependencyCheckXCommand if there is push dependencies https://issues.apache.org/jira/browse/OOZIE-2357 OOZIE-2349 Method getCoordJobInfo(String jobId, String filter, int offset, int length, boolean desc) is not present in LocalOozieClientCoord https://issues.apache.org/jira/browse/OOZIE-2349 OOZIE-2348 Recovery service keeps on recovering coord action of suspended jobs https://issues.apache.org/jira/browse/OOZIE-2348 OOZIE-2346 Add Oozie job console url and sub-workflow information like the super-parent id and workflow depth into the 'oozie.job.info' property https://issues.apache.org/jira/browse/OOZIE-2346 OOZIE-2338 Invalid configuration defined reported for some valid configs https://issues.apache.org/jira/browse/OOZIE-2338 OOZIE-2312 oozie doesn't purge audit and error log https://issues.apache.org/jira/browse/OOZIE-2312 OOZIE-2273 MiniOozie does not work outside of Oozie https://issues.apache.org/jira/browse/OOZIE-2273 OOZIE-2259 Create a callback action https://issues.apache.org/jira/browse/OOZIE-2259 OOZIE-2258 Introducing a new counter in the instrumentation log to distinguish between the reasons for launcher failure https://issues.apache.org/jira/browse/OOZIE-2258 OOZIE-2253 Spark Job is failing when it is running in standalone server https://issues.apache.org/jira/browse/OOZIE-2253 OOZIE-2244 Oozie should mask passwords in the logs when logging command arguments https://issues.apache.org/jira/browse/OOZIE-2244 OOZIE-2243 Kill Command does not kill the child job for java action https://issues.apache.org/jira/browse/OOZIE-2243 OOZIE- Oozie UI parent job should be clickable https://issues.apache.org/jira/browse/OOZIE- OOZIE-2203 Fix the login example https://issues.apache.org/jira/browse/OOZIE-2203 OOZIE-2196 Create Local Client for Bundle https://issues.apache.org/jira/browse/OOZIE-2196 OOZIE-2168 Oozie flow and action names have 50 char limit https://issues.apache.org/jira/browse/OOZIE-2168 OOZIE-2134 Remove references to Services.get().getConf() in code https://issues.apache.org/jira/browse/OOZIE-2134 OOZIE-2106 Make tomcat download url configurable in the pom file https://issues.apache.org/jira/browse/OOZIE-2106 OOZIE-2105 Make version of submodules configurable with parent version https://issues.apache.org/jira/browse/OOZIE-2105 OOZIE-2099 Add test-patch support for patches generated without --no-prefix https://issues.apache.org/jira/browse/OOZIE-2099 OOZIE-2081 WorkflowJob notification to include coordinator action id https://issues.apache.org/jira/browse/OOZIE-2081 OOZIE-2060 Incorrect documentation of Java action config XML filename https://issues.apache.org/jira/browse/OOZIE-2060 OOZIE-2044 ssh action succeed with a not exists command which should be fail. https://issues.apache.org/jira/browse/OOZIE-2044 OOZIE-2030 Configuration properties from global section is not getting set in Hadoop job conf when using sub-workflow action in Oozie workflow.xml https://issues.apache.org/jira/browse/OOZIE-2030 OOZIE-2020 Rerun all Failed/killed/timedout coordinator actions rather than specifying action numbers https://issues.apache.org/jira/browse/OOZIE-2020 OOZIE-1980 Sql error should not fail coord job https://issues.apache.org/jira/browse/OOZIE-1980 OOZIE-1977 Display patch analysis issues https://issues.apache.org/jira/browse/OOZIE-1977 OOZIE-1936 Queuedump command should display queue information for all server. https://issues.apache.org/jira/browse/OOZIE-1936 OOZIE-1931 Admin command to print all locks held by server(s) https://issues.apache.org/jira/browse/OOZIE-1931 OOZIE-1927 Use StoreStatusFilter for WorkflowsJobGetJPAExecutor https://issues.apache.org/jira/browse/OOZIE-1927 OOZIE-1922 MemoryLocksService fails if lock is acquired multiple times in same thread and released https://issues.apache.org/jira/browse/OOZIE-1922 OOZIE-1918 ActionXCommand refactoring for code reuse https://issues.apache.org/jira/browse/OOZIE-1918 OOZIE-1860 Oozie job mapper launch fails due to null value returned from action file https://issues.apache.org/jira/browse/OOZIE-1860 OOZIE-
[jira] [Commented] (OOZIE-2259) Create a callback action
[
https://issues.apache.org/jira/browse/OOZIE-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991214#comment-14991214
]
Srikanth Sundarrajan commented on OOZIE-2259:
-
[~puru], I feel that isolating this into a different thread pool was necessary
for exactly solving the issue that you highlighted. If the callback action were
to be in the main command queue execution threadpool, it can potentially take
the system for a ride. The only issue I see is that if there were significant
back pressure on the callback end point, then the auxillary queue for callback
actions may grow and put some memory pressure. But eventually it would start
throttling down the materialization of the coordinator that triggered of the
workflow/action. Generally the sense I get is that the there are enough safe
guards to prevent general degradation of other services within the system.
> Create a callback action
> -
>
> Key: OOZIE-2259
> URL: https://issues.apache.org/jira/browse/OOZIE-2259
> Project: Oozie
> Issue Type: New Feature
> Components: action
>Reporter: Jaydeep Vishwakarma
>Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2259-v1.patch, OOZIE-2259-v3.patch,
> OOZIE-2259-v4.patch, OOZIE-2259-v5.patch
>
>
> Need an action to send notification to external server by oozie. We should be
> able to do multiple types of callback, Currently I know jms and http call. It
> should suppose to have capability to call diffrent types of methods along
> with n number of arguments.
> The sample workflow with callback action
> {code:xml}
>
> ...
>
>
> [HOST]
> [METHOD]
>
> [KEY][VALUE]
>
> ...
>
> ...
>
> ...
>
> {code}
> HOST : by the host system can figure out if it is http or jms callback
> action. System will send the notification to that host.
> METHOD : it can be POST/GET/QUEUE/TOPIC
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2390) Rerun with failed option removing completed output data
[ https://issues.apache.org/jira/browse/OOZIE-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990463#comment-14990463 ] Purshotam Shah commented on OOZIE-2390: --- There could be partial failure. I might have pig script which might produce output and failed in next statement. If you want to rerun those action without deleting output then it always fail. I agree that most of time we don't have to cleanup output for failed rerun, but there could be some case where you need to do cleanup. If user uses only failed option, then assume nocleanup. But if user says -nocleanup=false, then we should cleanup ouput dir. > Rerun with failed option removing completed output data > --- > > Key: OOZIE-2390 > URL: https://issues.apache.org/jira/browse/OOZIE-2390 > Project: Oozie > Issue Type: Bug >Reporter: Jaydeep Vishwakarma >Assignee: Jaydeep Vishwakarma >Priority: Critical > Attachments: OOZIE-2390.patch > > > Rerun with failed option is used to run workflow from failed node. During the > time of rerun cleanup operation is removing the output directories which is > incorrect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2259) Create a callback action
[
https://issues.apache.org/jira/browse/OOZIE-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990411#comment-14990411
]
Purshotam Shah commented on OOZIE-2259:
---
Thanks Jaydeep, most of thing looks good.
My only concern is having different thread pool. Default http timeout may not
work for most cases.
We might have to increase timeout say 1 min. If we have few coord with wrong
url ( or takes more time) then it might impact other workflows SLA.
We noticed similar case with hcat connection caching. If one coord has
incorrect URL, it impacted others.
[~rohini] [~rkanter] [~sriksun] what u guys think? If others are ok, +1 from my
side.
> Create a callback action
> -
>
> Key: OOZIE-2259
> URL: https://issues.apache.org/jira/browse/OOZIE-2259
> Project: Oozie
> Issue Type: New Feature
> Components: action
>Reporter: Jaydeep Vishwakarma
>Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2259-v1.patch, OOZIE-2259-v3.patch,
> OOZIE-2259-v4.patch, OOZIE-2259-v5.patch
>
>
> Need an action to send notification to external server by oozie. We should be
> able to do multiple types of callback, Currently I know jms and http call. It
> should suppose to have capability to call diffrent types of methods along
> with n number of arguments.
> The sample workflow with callback action
> {code:xml}
>
> ...
>
>
> [HOST]
> [METHOD]
>
> [KEY][VALUE]
>
> ...
>
> ...
>
> ...
>
> {code}
> HOST : by the host system can figure out if it is http or jms callback
> action. System will send the notification to that host.
> METHOD : it can be POST/GET/QUEUE/TOPIC
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
