[jira] [Commented] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
[ https://issues.apache.org/jira/browse/OOZIE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052019#comment-15052019 ] Mike Grimes commented on OOZIE-2185: Is it not included in the conf directory of the client tarball? > Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script) > - > > Key: OOZIE-2185 > URL: https://issues.apache.org/jira/browse/OOZIE-2185 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Justice >Assignee: Mike Grimes >Priority: Minor > Labels: client, feature, newbie > Attachments: OOZIE-2185-1.patch, OOZIE-2185-2.patch, > OOZIE-2185-3.patch > > > Currently, the oozie cli doesn't source any environment script. Users may > wish to define environment variables such as OOZIE_URL outside of normal > shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh. > This is somewhat confusing when users see hadoop commands sourcing > hadoop-env.sh, mapred-env.sh, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
[
https://issues.apache.org/jira/browse/OOZIE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052005#comment-15052005
]
Robert Kanter commented on OOZIE-2185:
--
I played around with this. It looks good. One thing though is that I think
the reference oozie-client-env.sh should end up in the conf dir of a
deployment, like oozie-env.sh does.
{noformat}
>> [29] 17:46 : oozie (master) :: ls -l conf
total 280
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 action-conf
-rw-r--r-- 1 rkanter staff 824 Dec 10 17:42 adminusers.txt
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 hadoop-conf
-rw-r--r-- 1 rkanter staff1409 Dec 10 17:42 hadoop-config.xml
-rw-r--r-- 1 rkanter staff 112856 Dec 10 17:42 oozie-default.xml.reference
-rw-r--r-- 1 rkanter staff2215 Dec 10 17:42 oozie-env.cmd
-rw-r--r-- 1 rkanter staff2114 Dec 10 17:42 oozie-env.sh
-rw-r--r-- 1 rkanter staff5937 Dec 10 17:42 oozie-log4j.properties
-rw-r--r-- 1 rkanter staff 198 Dec 10 17:43 oozie-site.xml
{noformat}
It does show up when I build Oozie, so maybe it's being excluded from the
tarball or something?
{noformat}
>> [13] 17:52 : oozie-trunk (master) :: ls -l
>> distro/target/oozie-4.3.0-SNAPSHOT-distro/oozie-4.3.0-SNAPSHOT/conf/
total 288
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 action-conf
-rw-r--r-- 1 rkanter staff 824 Dec 10 17:42 adminusers.txt
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 hadoop-conf
-rw-r--r-- 1 rkanter staff1409 Dec 10 17:42 hadoop-config.xml
-rw-r--r--@ 1 rkanter staff 43 Dec 10 17:49 oozie-client-env.sh
-rw-r--r-- 1 rkanter staff 112856 Dec 10 17:42 oozie-default.xml.reference
-rw-r--r-- 1 rkanter staff2215 Dec 10 17:42 oozie-env.cmd
-rw-r--r-- 1 rkanter staff2114 Dec 10 17:42 oozie-env.sh
-rw-r--r-- 1 rkanter staff5937 Dec 10 17:42 oozie-log4j.properties
-rw-r--r-- 1 rkanter staff 198 Dec 10 17:43 oozie-site.xml
{noformat}
> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
> Issue Type: New Feature
> Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Assignee: Mike Grimes
>Priority: Minor
> Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch, OOZIE-2185-2.patch,
> OOZIE-2185-3.patch
>
>
> Currently, the oozie cli doesn't source any environment script. Users may
> wish to define environment variables such as OOZIE_URL outside of normal
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh.
> This is somewhat confusing when users see hadoop commands sourcing
> hadoop-env.sh, mapred-env.sh, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
[
https://issues.apache.org/jira/browse/OOZIE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052005#comment-15052005
]
Robert Kanter edited comment on OOZIE-2185 at 12/11/15 1:56 AM:
I played around with this. It looks good. One thing though is that I think
the oozie-client-env.sh should end up in the conf dir of a deployment, like
oozie-env.sh does.
{noformat}
>> [29] 17:46 : oozie (master) :: ls -l conf
total 280
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 action-conf
-rw-r--r-- 1 rkanter staff 824 Dec 10 17:42 adminusers.txt
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 hadoop-conf
-rw-r--r-- 1 rkanter staff1409 Dec 10 17:42 hadoop-config.xml
-rw-r--r-- 1 rkanter staff 112856 Dec 10 17:42 oozie-default.xml.reference
-rw-r--r-- 1 rkanter staff2215 Dec 10 17:42 oozie-env.cmd
-rw-r--r-- 1 rkanter staff2114 Dec 10 17:42 oozie-env.sh
-rw-r--r-- 1 rkanter staff5937 Dec 10 17:42 oozie-log4j.properties
-rw-r--r-- 1 rkanter staff 198 Dec 10 17:43 oozie-site.xml
{noformat}
It does show up when I build Oozie, so maybe it's being excluded from the
tarball or something?
{noformat}
>> [13] 17:52 : oozie-trunk (master) :: ls -l
>> distro/target/oozie-4.3.0-SNAPSHOT-distro/oozie-4.3.0-SNAPSHOT/conf/
total 288
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 action-conf
-rw-r--r-- 1 rkanter staff 824 Dec 10 17:42 adminusers.txt
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 hadoop-conf
-rw-r--r-- 1 rkanter staff1409 Dec 10 17:42 hadoop-config.xml
-rw-r--r--@ 1 rkanter staff 43 Dec 10 17:49 oozie-client-env.sh
-rw-r--r-- 1 rkanter staff 112856 Dec 10 17:42 oozie-default.xml.reference
-rw-r--r-- 1 rkanter staff2215 Dec 10 17:42 oozie-env.cmd
-rw-r--r-- 1 rkanter staff2114 Dec 10 17:42 oozie-env.sh
-rw-r--r-- 1 rkanter staff5937 Dec 10 17:42 oozie-log4j.properties
-rw-r--r-- 1 rkanter staff 198 Dec 10 17:43 oozie-site.xml
{noformat}
was (Author: rkanter):
I played around with this. It looks good. One thing though is that I think
the reference oozie-client-env.sh should end up in the conf dir of a
deployment, like oozie-env.sh does.
{noformat}
>> [29] 17:46 : oozie (master) :: ls -l conf
total 280
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 action-conf
-rw-r--r-- 1 rkanter staff 824 Dec 10 17:42 adminusers.txt
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 hadoop-conf
-rw-r--r-- 1 rkanter staff1409 Dec 10 17:42 hadoop-config.xml
-rw-r--r-- 1 rkanter staff 112856 Dec 10 17:42 oozie-default.xml.reference
-rw-r--r-- 1 rkanter staff2215 Dec 10 17:42 oozie-env.cmd
-rw-r--r-- 1 rkanter staff2114 Dec 10 17:42 oozie-env.sh
-rw-r--r-- 1 rkanter staff5937 Dec 10 17:42 oozie-log4j.properties
-rw-r--r-- 1 rkanter staff 198 Dec 10 17:43 oozie-site.xml
{noformat}
It does show up when I build Oozie, so maybe it's being excluded from the
tarball or something?
{noformat}
>> [13] 17:52 : oozie-trunk (master) :: ls -l
>> distro/target/oozie-4.3.0-SNAPSHOT-distro/oozie-4.3.0-SNAPSHOT/conf/
total 288
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 action-conf
-rw-r--r-- 1 rkanter staff 824 Dec 10 17:42 adminusers.txt
drwxr-xr-x 3 rkanter staff 102 Dec 10 17:42 hadoop-conf
-rw-r--r-- 1 rkanter staff1409 Dec 10 17:42 hadoop-config.xml
-rw-r--r--@ 1 rkanter staff 43 Dec 10 17:49 oozie-client-env.sh
-rw-r--r-- 1 rkanter staff 112856 Dec 10 17:42 oozie-default.xml.reference
-rw-r--r-- 1 rkanter staff2215 Dec 10 17:42 oozie-env.cmd
-rw-r--r-- 1 rkanter staff2114 Dec 10 17:42 oozie-env.sh
-rw-r--r-- 1 rkanter staff5937 Dec 10 17:42 oozie-log4j.properties
-rw-r--r-- 1 rkanter staff 198 Dec 10 17:43 oozie-site.xml
{noformat}
> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
> Issue Type: New Feature
> Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Assignee: Mike Grimes
>Priority: Minor
> Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch, OOZIE-2185-2.patch,
> OOZIE-2185-3.patch
>
>
> Currently, the oozie cli doesn't source any environment script. Users may
> wish to define environment variables such as OOZIE_URL outside of normal
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh.
> This is somewhat confusing when users see hadoop commands sourcing
> hadoop-env.sh, mapred-env.sh, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2402) oozie-setup.sh sharelib create takes a long time on large clusters
[ https://issues.apache.org/jira/browse/OOZIE-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051997#comment-15051997 ] Robert Kanter commented on OOZIE-2402: -- Ya, the test-patch script has been having problems lately. Thanks for fixing #4. The patch looks good, but I'd like to actually play around a bit with it first. I'll try to get to that sometime either this week or next week. > oozie-setup.sh sharelib create takes a long time on large clusters > -- > > Key: OOZIE-2402 > URL: https://issues.apache.org/jira/browse/OOZIE-2402 > Project: Oozie > Issue Type: Improvement > Components: tools >Affects Versions: 4.2.0 >Reporter: Illya Yalovyy >Assignee: Illya Yalovyy > Attachments: OOZIE-2402-1.patch, OOZIE-2402-2.patch, > OOZIE-2402-3.patch, OOZIE-2402-4.patch > > > When cluster has 256+ nodes it can take up to 5 minutes to create a sharelib. > Copy the tarball itself takes only around 10 seconds. It seems like > performance could be improved by loading files concurrently in many threads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
[
https://issues.apache.org/jira/browse/OOZIE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052052#comment-15052052
]
Robert Kanter commented on OOZIE-2185:
--
Oh, you're right.
{noformat}
>> [13] 18:37 : oozie-trunk (master) :: tar -tf
>> ./client/target/oozie-client-4.3.0-SNAPSHOT-client.tar.gz
oozie-client-4.3.0-SNAPSHOT/DISCLAIMER.txt
oozie-client-4.3.0-SNAPSHOT/LICENSE.txt
oozie-client-4.3.0-SNAPSHOT/NOTICE.txt
oozie-client-4.3.0-SNAPSHOT/README.txt
oozie-client-4.3.0-SNAPSHOT/release-log.txt
oozie-client-4.3.0-SNAPSHOT/source-headers.txt
oozie-client-4.3.0-SNAPSHOT/bin/oozie
oozie-client-4.3.0-SNAPSHOT/conf/oozie-client-env.sh
oozie-client-4.3.0-SNAPSHOT/lib/oozie-client-4.3.0-SNAPSHOT.jar
oozie-client-4.3.0-SNAPSHOT/lib/json-simple-1.1.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-cli-1.2.jar
oozie-client-4.3.0-SNAPSHOT/lib/guava-11.0.2.jar
oozie-client-4.3.0-SNAPSHOT/lib/jsr305-1.3.9.jar
oozie-client-4.3.0-SNAPSHOT/lib/jackson-core-asl-1.8.8.jar
oozie-client-4.3.0-SNAPSHOT/lib/jackson-mapper-asl-1.8.8.jar
oozie-client-4.3.0-SNAPSHOT/lib/activemq-client-5.10.2.jar
oozie-client-4.3.0-SNAPSHOT/lib/slf4j-api-1.6.6.jar
oozie-client-4.3.0-SNAPSHOT/lib/geronimo-jms_1.1_spec-1.1.1.jar
oozie-client-4.3.0-SNAPSHOT/lib/hawtbuf-1.10.jar
oozie-client-4.3.0-SNAPSHOT/lib/geronimo-j2ee-management_1.1_spec-1.0.1.jar
oozie-client-4.3.0-SNAPSHOT/lib/oozie-hadoop-auth-hadoop-1-4.3.0-SNAPSHOT.jar
oozie-client-4.3.0-SNAPSHOT/lib/hadoop-core-1.2.1.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-codec-1.4.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-configuration-1.6.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-collections-3.2.1.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-lang-2.4.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-logging-1.1.jar
oozie-client-4.3.0-SNAPSHOT/lib/log4j-1.2.17.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-digester-1.8.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-beanutils-1.7.0.jar
oozie-client-4.3.0-SNAPSHOT/lib/commons-beanutils-core-1.8.0.jar
oozie-client-4.3.0-SNAPSHOT/lib/slf4j-simple-1.6.6.jar
oozie-client-4.3.0-SNAPSHOT/lib/xercesImpl-2.10.0.jar
oozie-client-4.3.0-SNAPSHOT/lib/xml-apis-1.4.01.jar
{noformat}
+1
> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
> Issue Type: New Feature
> Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Assignee: Mike Grimes
>Priority: Minor
> Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch, OOZIE-2185-2.patch,
> OOZIE-2185-3.patch
>
>
> Currently, the oozie cli doesn't source any environment script. Users may
> wish to define environment variables such as OOZIE_URL outside of normal
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh.
> This is somewhat confusing when users see hadoop commands sourcing
> hadoop-env.sh, mapred-env.sh, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2402) oozie-setup.sh sharelib create takes a long time on large clusters
[ https://issues.apache.org/jira/browse/OOZIE-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052053#comment-15052053 ] Illya Yalovyy commented on OOZIE-2402: -- Thank you! Please let me know if you have any questions. > oozie-setup.sh sharelib create takes a long time on large clusters > -- > > Key: OOZIE-2402 > URL: https://issues.apache.org/jira/browse/OOZIE-2402 > Project: Oozie > Issue Type: Improvement > Components: tools >Affects Versions: 4.2.0 >Reporter: Illya Yalovyy >Assignee: Illya Yalovyy > Attachments: OOZIE-2402-1.patch, OOZIE-2402-2.patch, > OOZIE-2402-3.patch, OOZIE-2402-4.patch > > > When cluster has 256+ nodes it can take up to 5 minutes to create a sharelib. > Copy the tarball itself takes only around 10 seconds. It seems like > performance could be improved by loading files concurrently in many threads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (61 issues) Subscriber: ooziedaily Key Summary OOZIE-2409 hive2 action with hive 1.2.1 failed https://issues.apache.org/jira/browse/OOZIE-2409 OOZIE-2407 AbandonedService should not send mail if there is no abandoned coord https://issues.apache.org/jira/browse/OOZIE-2407 OOZIE-2402 oozie-setup.sh sharelib create takes a long time on large clusters https://issues.apache.org/jira/browse/OOZIE-2402 OOZIE-2400 Workflow xml configuration parser cannot deal with namespace prefix https://issues.apache.org/jira/browse/OOZIE-2400 OOZIE-2396 oozie compile with hadoop 2.7.1 failed https://issues.apache.org/jira/browse/OOZIE-2396 OOZIE-2394 Oozie can execute command without holding lock https://issues.apache.org/jira/browse/OOZIE-2394 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-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-2172 ZooKeeper Security Tests failed with JVM IBM JAVA https://issues.apache.org/jira/browse/OOZIE-2172 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
