[ANNOUNCE] CFP open for ApacheCon North America 2016

2015-11-25 Thread Rich Bowen 
Community growth starts by talking with those interested in your
project. ApacheCon North America is coming, are you?

We are delighted to announce that the Call For Presentations (CFP) is
now open for ApacheCon North America. You can submit your proposed
sessions at
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp
for big data talks and
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
for all other topics.

ApacheCon North America will be held in Vancouver, Canada, May 9-13th
2016. ApacheCon has been running every year since 2000, and is the place
to build your project communities.

While we will consider individual talks we prefer to see related
sessions that are likely to draw users and community members. When
submitting your talk work with your project community and with related
communities to come up with a full program that will walk attendees
through the basics and on into mastery of your project in example use
cases. Content that introduces what's new in your latest release is also
of particular interest, especially when it builds upon existing well
know application models. The goal should be to showcase your project in
ways that will attract participants and encourage engagement in your
community, Please remember to involve your whole project community (user
and dev lists) when building content. This is your chance to create a
project specific event within the broader ApacheCon conference.

Content at ApacheCon North America will be cross-promoted as
mini-conferences, such as ApacheCon Big Data, and ApacheCon Mobile, so
be sure to indicate which larger category your proposed sessions fit into.

Finally, please plan to attend ApacheCon, even if you're not proposing a
talk. The biggest value of the event is community building, and we count
on you to make it a place where your project community is likely to
congregate, not just for the technical content in sessions, but for
hackathons, project summits, and good old fashioned face-to-face networking.

-- 
rbo...@apache.org
http://apache.org/

[jira] [Commented] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-25 Thread Mike Grimes (JIRA) 

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

Mike Grimes commented on OOZIE-2185:


Great, thanks for looking at this.

I'll make those fixes and update the patch.

> 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
>
>
> 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-2307) Publish Oozie 4.2.0 artifacts

2015-11-25 Thread Venkat Ranganathan (JIRA) 

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

Venkat Ranganathan commented on OOZIE-2307:
---

I assigned to you because did the work already [~shwethags]

> Publish Oozie 4.2.0 artifacts
> -
>
> Key: OOZIE-2307
> URL: https://issues.apache.org/jira/browse/OOZIE-2307
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Peeyush Bishnoi
>Assignee: Shwetha G S
> Fix For: 4.2.0
>
>




--
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

2015-11-25 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-2402:
--

The overall approach looks good to me.  This should be helpful in speeding 
things up.
Some minor things:
# Please remove the trailing whitespaces from the 7 lines
# Can you update the docs?  Update this section 
(http://oozie.apache.org/docs/4.2.0/AG_Install.html#Oozie_Server_Setup) with 
the new usage info.  You can find the source for this page in AG_Install.twiki 
in the code
# In {{concurrentCopyFromLocal}}, I think we should put the call to 
{{copyFolderRecursively}} in a try-catch-finally block.  For instance, we 
should make sure to always call {{threadpool.shutdown()}}.
# It would be nice if {{checkCopyResults}} could print out the exception for 
each failure, instead of just one.  Otherwise, if there are multiple problems, 
the user will have to keep trying after resolving each issue.  
# In {{copyFolderRecursively}}, the Streams should be closed in a finally 
block, not a catch block.  Otherwise, they're only closed if an Exception occurs
# The description for the concurrency should say what the default is (e.g. 
"(default=1)")
# Why use Streams instead of {{fs.copyFromLocalFile}}?
# Can you add/update unit tests in {{TestOozieSharelibCLI}}?

> 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
>
>
> 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-2172) ZooKeeper Security Tests failed with JVM IBM JAVA

2015-11-25 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-2172:
--

Thanks for creating and uploading a patch [~GauravPande].  Can you regenerate 
the patch with {{--no-prefix}}?  This will get rid of the leading "a" and "b", 
which is why it couldn't apply the patch.

> ZooKeeper Security Tests failed with JVM IBM JAVA
> -
>
> Key: OOZIE-2172
> URL: https://issues.apache.org/jira/browse/OOZIE-2172
> Project: Oozie
>  Issue Type: Test
>  Components: HA
>Affects Versions: 4.1.0, 4.2.0
> Environment:  zookeeper-security-tests]# mvn -verion
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
> 2014-12-14T12:29:23-05:00)
> Maven home: /opt/apache-maven-3.2.5
> Java version: 1.7.0, vendor: IBM Corporation
> Java home: /usr/lib/jvm/ibm-java-x86_64-71-pxa6470_27sr2fp10-20141218_02/jre
> Default locale: en_US, platform encoding: ISO-8859-1
> OS name: "linux", version: "3.10.0-229.el7.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: pascal oliva
>  Labels: ibm-jdk, jaas, oozie, patch, security, zookeeper
> Attachments: OOZIE-2172.patch
>
>
> ZooKeeper Security Tests failed by using IBM JAVA
> ---
> Concurrency config is parallel='classes', perCoreThreadCount=false, 
> threadCount=1, useUnlimitedThreads=false
> Running org.apache.oozie.util.TestZKUtilsWithSecurity
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 36.493 sec 
> <<< FAILURE!
> Results :
> Tests in error:
>   testCheckAndSetACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): 
> org.apache.hcatalog.common.HCatException : 9001 : Exception occurred while 
> processing HCat request : MetaException while creating HMS client. Cause : 
> MetaException(message:Could not connect to meta store using any of the URIs 
> provided. Most recent failure: 
> org.apache.thrift.transport.TTransportException: java.net.ConnectException: 
> Connection refused(..)
>   testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): Could not 
> configure server because SASL configuration did not allow the  ZooKeeper 
> server to authenticate itself properly: 
> javax.security.auth.login.LoginException: Bad JAAS configuration: 
> unrecognized option: storeKey
> ..
> Traces On 
> target/./surefire-reports/org.apache.oozie.util.TestZKUtilsWithSecurity-output.txt
> at 
> com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767)
> at 
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568)
> at 
> com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)
> at 
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313)
> at 
> com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3965)
> at 
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764)
> at 
> org.apache.hcatalog.common.HiveClientCache.getOrCreate(HiveClientCache.java:167)
> at 
> org.apache.hcatalog.common.HiveClientCache.get(HiveClientCache.java:143)
> at 
> org.apache.hcatalog.common.HCatUtil.getHiveClient(HCatUtil.java:548)
> at 
> org.apache.hcatalog.api.HCatClientHMSImpl.initialize(HCatClientHMSImpl.java:596)
> ... 27 more
> testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity)  Time 
> elapsed: 0.009 sec  <<< ERROR!
> java.io.IOException: Could not configure server because SASL configuration 
> did not allow the  ZooKeeper server to authenticate itself properly: 
> javax.security.auth.login.LoginException: Bad JAAS configuration: 
> unrecognized option: storeKey
> at 
> org.apache.zookeeper.server.ServerCnxnFactory.configureSaslLogin(ServerCnxnFactory.java:207)
> at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:87)
> at 
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:111)
> at 
> org.apache.curator.test.TestingZooKeeperMain.runFromConfig(TestingZooKeeperMain.java:73)
> at 
> org.apache.curator.test.TestingZooKeeperServer$1.run(TestingZooKeeperServer.java:134)
> at java.lang.Thread.run(Thread.java:863)
> ...
> howto reproduce :
> git clone -b branch-4.1 https://github.com/apache/oozie.git
> cd oozie
> ./bin/mkdistro.sh -DskipTests -Phadoop-2
> cd zookeeper-security-tests/
> mvn clean test -Phadoop-2



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

[jira] [Commented] (OOZIE-2307) Publish Oozie 4.2.0 artifacts

2015-11-25 Thread Venkat Ranganathan (JIRA) 

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

Venkat Ranganathan commented on OOZIE-2307:
---

[~shwethags]  - Now that you have published the maven artifacts can this be 
closed?

> Publish Oozie 4.2.0 artifacts
> -
>
> Key: OOZIE-2307
> URL: https://issues.apache.org/jira/browse/OOZIE-2307
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Peeyush Bishnoi
>Assignee: Shwetha G S
> Fix For: 4.2.0
>
>




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

[jira] [Updated] (OOZIE-2307) Publish Oozie 4.2.0 artifacts

2015-11-25 Thread Venkat Ranganathan (JIRA) 

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

Venkat Ranganathan updated OOZIE-2307:
--
Assignee: Shwetha G S

> Publish Oozie 4.2.0 artifacts
> -
>
> Key: OOZIE-2307
> URL: https://issues.apache.org/jira/browse/OOZIE-2307
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Peeyush Bishnoi
>Assignee: Shwetha G S
> Fix For: 4.2.0
>
>




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

[jira] [Updated] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-25 Thread Robert Kanter (JIRA) 

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

Robert Kanter updated OOZIE-2185:
-
Assignee: Mike Grimes

> 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
>
>
> 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] [Updated] (OOZIE-2402) oozie-setup.sh sharelib create takes a long time on large clusters

2015-11-25 Thread Robert Kanter (JIRA) 

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

Robert Kanter updated OOZIE-2402:
-
Assignee: Illya Yalovyy

> 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
>
>
> 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-2390) Rerun with failed option removing completed output data

2015-11-25 Thread Purshotam Shah (JIRA) 

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

Purshotam Shah commented on OOZIE-2390:
---

{quote}
Purshotam Shah ,Oozie removes the output directory by default, As default value 
of -nocleanup is false. So either you give the -nocleanup=false or do not 
provide that option both are same. By this approach impossible to understand 
what user wants.
Yes, when we have intermediate output from any workflow action we will expect 
failures. I think we should introduce another flag -failedwithcleanup on rerun. 
What is your thought on it?
{quote}

We can support -nocleanup  with param ( true/false).  For backward compatibly 
we can also support only -nocleanup ( which means -nocleanup=true).
For failed, we can have default as true and for other cases default can be 
false.

> 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)

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

2015-11-25 Thread Robert Kanter 

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



core/src/main/java/org/apache/oozie/action/callback/CallbackActionExecutor.java 
(line 195)


We're in the CallbackActionExecutor, so you can just refer to these 
directly: CALLBACK_ACTION_HTTP_CONNECTION_TIMEOUT_SECS, 
CALLBACK_ACTION_HTTP_SOCKET_TIMEOUT_SECS, and CALLBACK_ACTION_KEEPALIVE_SECS
to improve readability



core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java
 (line 133)


Perhaps we should use ``(freeHTTPPort + 1)`` for this?



core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java
 (line 172)


Perhaps we should use ``(freeJMSPort + 1)`` for this?



docs/src/site/twiki/DG_CallbackActionExtension.twiki (line 12)


Callback Action



docs/src/site/twiki/DG_CallbackActionExtension.twiki (line 97)


minOccurs="0".

Please double check that this all matches the XSD file.  It might be 
easiest to just copy-paste it again.


- Robert Kanter


On Nov. 12, 2015, 12:21 p.m., Jaydeep Vishwakarma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36123/
> ---
> 
> (Updated Nov. 12, 2015, 12:21 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2259
> https://issues.apache.org/jira/browse/OOZIE-2259
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Adding callback as an action, It have support for HTTP and JMS server. Not 
> covering Excecutor level queue, I will create a separate jira for it.
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 48bac7d 
>   client/src/main/resources/callback-action-0.1.xsd PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/action/callback/CallbackActionExecutor.java
>  PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/callback/JMSNotification.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/service/CallbackActionService.java 
> PRE-CREATION 
>   core/src/main/resources/oozie-default.xml 0a7e250 
>   
> core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java
>  PRE-CREATION 
>   docs/src/site/twiki/DG_CallbackActionExtension.twiki PRE-CREATION 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 1823247 
>   docs/src/site/twiki/index.twiki 8591530 
> 
> Diff: https://reviews.apache.org/r/36123/diff/
> 
> 
> Testing
> ---
> 
> Done, 
> Will add more test cases.
> 
> 
> Thanks,
> 
> Jaydeep Vishwakarma
> 
>

[jira] [Commented] (OOZIE-2259) Create a callback action

2015-11-25 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-2259:
--

I left a few more comments on the latest patch on RB.  Just some very minor 
things.  After that, I think I'm good with the patch.  Given that this is a new 
action, it would be good for some others to also review it.  [~puru], [~rohini]

> 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, OOZIE-2259_v6.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-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-25 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-2185:
--

I'll need to spend a bit more time playing around with it; probably some time 
next week.  But at a first glance, this seems reasonable.  A few minor things:
# Most users won't need to set {{OOZIE_AUTH}} explicitly because the Oozie 
Client figures this out automatically most of the time.  I think we should 
mention that in the description; something like:
{noformat}
# Authenticaton type - used as value for the '-auth' option if set
# Note that Oozie normally determines this automatically so you usually won't 
need to set it
# Options: [SIMPLE|KERBEROS]
{noformat}
# Missing a newline at the end of oozie-client-env.sh
# It would be good to also put {{OOZIE_CLIENT_OPTS}} in there (it lets you 
apply JVM options, such as Xmx, truststore, etc)


> 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
>
>
> 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] [Created] (OOZIE-2407) AbandonedService should not send mail if there is no abandoned coord

2015-11-25 Thread Purshotam Shah (JIRA) 
Purshotam Shah created OOZIE-2407:
-

 Summary: AbandonedService should not send mail if there is no 
abandoned coord
 Key: OOZIE-2407
 URL: https://issues.apache.org/jira/browse/OOZIE-2407
 Project: Oozie
  Issue Type: Bug
Reporter: Purshotam Shah






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

[jira] [Commented] (OOZIE-2394) Oozie can execute command without holding lock

2015-11-25 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-2394:
--

A few minor things:
# XCommand has an else statement that now has a new line
{code}
} else {
{code}
became
{code}
}
else {
{code}
Can you put that back?
# There's a lot of formatting changes in areas of the code that weren't 
changed.  Don't we generally not fix those unless actually changing that part 
of the code?
# It would be good to make at least a simple test to show that XCommands and 
the locking is reentrant.  Perhaps just create a DummyXCommand that 
synchronously calls a Dummy2XCommand and both have the same entity key or 
something like that?  The test should probably have some kind of timeout in 
case this ever breaks.

> Oozie can execute command without holding lock
> --
>
> Key: OOZIE-2394
> URL: https://issues.apache.org/jira/browse/OOZIE-2394
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Critical
> Attachments: OOZIE-2394-V1.patch
>
>
> To speedup job submission ( not the the forked actions) we create workflow 
> actions synchronously. We call ActionStartXCommand from SignalXCommand by 
> setting isSynchronous = true. This will bypass lock acquiring, which is Ok, 
> SignalXCommand will have the job lock.
> If there is transient error. Same command is requeued which will have 
> isSynchronous flag set to true.
> Requeued command will wake-up and started executing without acquiring lock. 
> If the job submission takes more than 2 min, then we might have issue.
> Action recovery is set to 2 min ( default), Recovery service will run and 
> submitted new the command. since the first command didn't acquire any lock. 
> Recovery will be able to run the new command.
> We will have two same command running parallely.
> All our commands are reentrant, we don't have to have set synchronized flag 
> to run multiple command from same thread.
> Because of reentrant, command running in same thread should be able to 
> acquire same lock.



--
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

2015-11-25 Thread Illya Yalovyy (JIRA) 

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

Illya Yalovyy commented on OOZIE-2402:
--

[~rkanter],

Thank you for the prompt review.

Please see my notes below:
1. Will fix it.
2. I'll update related documentation.
3. Will fix it.
4. Will fix it.
5. {{IOUtils.copyBytes(in, out, fs.getConf(), true);}} closes both streams 
internally. We need this {{close()}} statement in catch section only for a case 
when {{out = fs.create(new Path(dstPath, file.getName()));}} fails with an 
exception.
6. Will fix it
7. I wanted to escape overhead of hadoop FS implementation, but I will run some 
tests to actually measure the difference. If it is not significant,  I will use 
{{fs.copyFromLocalFile}} to copy individual files.
8. Will add unit test



> 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
>
>
> 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)

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

2015-11-25 Thread Jaydeep Vishwakarma 


> On Nov. 25, 2015, 9:47 p.m., Robert Kanter wrote:
> > core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java,
> >  line 133
> > 
> >
> > Perhaps we should use ``(freeHTTPPort + 1)`` for this?

I understood your concern. Even it is possible that the freeHTTPPort + 1 has 
been occupied by some server. I will use findFreePort() to ensure the unused 
port.


> On Nov. 25, 2015, 9:47 p.m., Robert Kanter wrote:
> > core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java,
> >  line 172
> > 
> >
> > Perhaps we should use ``(freeJMSPort + 1)`` for this?

Same here , I will use findFreePort() to ensure the unused port.


- Jaydeep


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


On Nov. 26, 2015, 7:43 a.m., Jaydeep Vishwakarma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36123/
> ---
> 
> (Updated Nov. 26, 2015, 7:43 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2259
> https://issues.apache.org/jira/browse/OOZIE-2259
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Adding callback as an action, It have support for HTTP and JMS server. Not 
> covering Excecutor level queue, I will create a separate jira for it.
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 48bac7d 
>   client/src/main/resources/callback-action-0.1.xsd PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/action/callback/CallbackActionExecutor.java
>  PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/callback/JMSNotification.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/service/CallbackActionService.java 
> PRE-CREATION 
>   core/src/main/resources/oozie-default.xml 0a7e250 
>   
> core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java
>  PRE-CREATION 
>   docs/src/site/twiki/DG_CallbackActionExtension.twiki PRE-CREATION 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 1823247 
>   docs/src/site/twiki/index.twiki 8591530 
> 
> Diff: https://reviews.apache.org/r/36123/diff/
> 
> 
> Testing
> ---
> 
> Done, 
> Will add more test cases.
> 
> 
> Thanks,
> 
> Jaydeep Vishwakarma
> 
>

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

2015-11-25 Thread Jaydeep Vishwakarma 

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

(Updated Nov. 26, 2015, 7:43 a.m.)


Review request for oozie.


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


Repository: oozie-git


Description
---

Adding callback as an action, It have support for HTTP and JMS server. Not 
covering Excecutor level queue, I will create a separate jira for it.


Diffs (updated)
-

  client/src/main/java/org/apache/oozie/cli/OozieCLI.java 48bac7d 
  client/src/main/resources/callback-action-0.1.xsd PRE-CREATION 
  
core/src/main/java/org/apache/oozie/action/callback/CallbackActionExecutor.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/action/callback/JMSNotification.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/service/CallbackActionService.java 
PRE-CREATION 
  core/src/main/resources/oozie-default.xml 0a7e250 
  
core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java
 PRE-CREATION 
  docs/src/site/twiki/DG_CallbackActionExtension.twiki PRE-CREATION 
  docs/src/site/twiki/DG_CommandLineTool.twiki 1823247 
  docs/src/site/twiki/index.twiki 8591530 

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


Testing
---

Done, 
Will add more test cases.


Thanks,

Jaydeep Vishwakarma

[jira] [Updated] (OOZIE-2259) Create a callback action

2015-11-25 Thread Jaydeep Vishwakarma (JIRA) 

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

Jaydeep Vishwakarma updated OOZIE-2259:
---
Attachment: OOZIE-2259_v7.patch

> 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, OOZIE-2259_v6.patch, 
> OOZIE-2259_v7.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] [Resolved] (OOZIE-2307) Publish Oozie 4.2.0 artifacts

2015-11-25 Thread Shwetha G S (JIRA) 

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

Shwetha G S resolved OOZIE-2307.

Resolution: Fixed

> Publish Oozie 4.2.0 artifacts
> -
>
> Key: OOZIE-2307
> URL: https://issues.apache.org/jira/browse/OOZIE-2307
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Peeyush Bishnoi
>Assignee: Shwetha G S
> Fix For: 4.2.0
>
>




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

[jira] Subscription: Oozie Patch Available

2015-11-25 Thread jira 
Issue Subscription
Filter: Oozie Patch Available (59 issues)

Subscriber: ooziedaily

Key Summary
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-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-2185  Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other 
env script)
https://issues.apache.org/jira/browse/OOZIE-2185
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
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

[jira] [Updated] (OOZIE-2172) ZooKeeper Security Tests failed with JVM IBM JAVA

2015-11-25 Thread Gaurav Pande (JIRA) 

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

Gaurav Pande updated OOZIE-2172:

Attachment: OOZIE-2172.patch

Submitting a patch (OOZIE-2172.patch) with fix for zookeeper security related 
tests in oozie with ibmjdk

> ZooKeeper Security Tests failed with JVM IBM JAVA
> -
>
> Key: OOZIE-2172
> URL: https://issues.apache.org/jira/browse/OOZIE-2172
> Project: Oozie
>  Issue Type: Test
>  Components: HA
>Affects Versions: 4.1.0, 4.2.0
> Environment:  zookeeper-security-tests]# mvn -verion
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
> 2014-12-14T12:29:23-05:00)
> Maven home: /opt/apache-maven-3.2.5
> Java version: 1.7.0, vendor: IBM Corporation
> Java home: /usr/lib/jvm/ibm-java-x86_64-71-pxa6470_27sr2fp10-20141218_02/jre
> Default locale: en_US, platform encoding: ISO-8859-1
> OS name: "linux", version: "3.10.0-229.el7.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: pascal oliva
>  Labels: ibm-jdk, jaas, oozie, patch, security, zookeeper
> Attachments: OOZIE-2172.patch
>
>
> ZooKeeper Security Tests failed by using IBM JAVA
> ---
> Concurrency config is parallel='classes', perCoreThreadCount=false, 
> threadCount=1, useUnlimitedThreads=false
> Running org.apache.oozie.util.TestZKUtilsWithSecurity
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 36.493 sec 
> <<< FAILURE!
> Results :
> Tests in error:
>   testCheckAndSetACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): 
> org.apache.hcatalog.common.HCatException : 9001 : Exception occurred while 
> processing HCat request : MetaException while creating HMS client. Cause : 
> MetaException(message:Could not connect to meta store using any of the URIs 
> provided. Most recent failure: 
> org.apache.thrift.transport.TTransportException: java.net.ConnectException: 
> Connection refused(..)
>   testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): Could not 
> configure server because SASL configuration did not allow the  ZooKeeper 
> server to authenticate itself properly: 
> javax.security.auth.login.LoginException: Bad JAAS configuration: 
> unrecognized option: storeKey
> ..
> Traces On 
> target/./surefire-reports/org.apache.oozie.util.TestZKUtilsWithSecurity-output.txt
> at 
> com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767)
> at 
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568)
> at 
> com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)
> at 
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313)
> at 
> com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3965)
> at 
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764)
> at 
> org.apache.hcatalog.common.HiveClientCache.getOrCreate(HiveClientCache.java:167)
> at 
> org.apache.hcatalog.common.HiveClientCache.get(HiveClientCache.java:143)
> at 
> org.apache.hcatalog.common.HCatUtil.getHiveClient(HCatUtil.java:548)
> at 
> org.apache.hcatalog.api.HCatClientHMSImpl.initialize(HCatClientHMSImpl.java:596)
> ... 27 more
> testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity)  Time 
> elapsed: 0.009 sec  <<< ERROR!
> java.io.IOException: Could not configure server because SASL configuration 
> did not allow the  ZooKeeper server to authenticate itself properly: 
> javax.security.auth.login.LoginException: Bad JAAS configuration: 
> unrecognized option: storeKey
> at 
> org.apache.zookeeper.server.ServerCnxnFactory.configureSaslLogin(ServerCnxnFactory.java:207)
> at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:87)
> at 
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:111)
> at 
> org.apache.curator.test.TestingZooKeeperMain.runFromConfig(TestingZooKeeperMain.java:73)
> at 
> org.apache.curator.test.TestingZooKeeperServer$1.run(TestingZooKeeperServer.java:134)
> at java.lang.Thread.run(Thread.java:863)
> ...
> howto reproduce :
> git clone -b branch-4.1 https://github.com/apache/oozie.git
> cd oozie
> ./bin/mkdistro.sh -DskipTests -Phadoop-2
> cd zookeeper-security-tests/
> mvn clean test -Phadoop-2



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

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

2015-11-25 Thread Apache Jenkins Server 
See 

--
[...truncated 2491 lines...]
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oozie-mini ---
[INFO] Deleting 

[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] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie WorkflowGenerator 4.3.0-SNAPSHOT
[INFO] 
Downloading: 
https://repository.apache.org/content/groups/snapshots/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml



Downloading: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/groups/snapshots/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml


605/605 B   

Downloaded: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
 (605 B at 2.4 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
oozie-workflowgenerator ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-workflowgenerator ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-workflowgenerator ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 24 resources to ../../img
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
oozie-workflowgenerator ---
[INFO] Compiling 39 source files to 

[WARNING] 
:[243,30]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[270,30]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[271,26]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[272,14]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[273,14]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING]

[jira] [Commented] (OOZIE-2172) ZooKeeper Security Tests failed with JVM IBM JAVA

2015-11-25 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2172:
--

Testing JIRA OOZIE-2172

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> ZooKeeper Security Tests failed with JVM IBM JAVA
> -
>
> Key: OOZIE-2172
> URL: https://issues.apache.org/jira/browse/OOZIE-2172
> Project: Oozie
>  Issue Type: Test
>  Components: HA
>Affects Versions: 4.1.0, 4.2.0
> Environment:  zookeeper-security-tests]# mvn -verion
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
> 2014-12-14T12:29:23-05:00)
> Maven home: /opt/apache-maven-3.2.5
> Java version: 1.7.0, vendor: IBM Corporation
> Java home: /usr/lib/jvm/ibm-java-x86_64-71-pxa6470_27sr2fp10-20141218_02/jre
> Default locale: en_US, platform encoding: ISO-8859-1
> OS name: "linux", version: "3.10.0-229.el7.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: pascal oliva
>  Labels: ibm-jdk, jaas, oozie, patch, security, zookeeper
> Attachments: OOZIE-2172.patch
>
>
> ZooKeeper Security Tests failed by using IBM JAVA
> ---
> Concurrency config is parallel='classes', perCoreThreadCount=false, 
> threadCount=1, useUnlimitedThreads=false
> Running org.apache.oozie.util.TestZKUtilsWithSecurity
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 36.493 sec 
> <<< FAILURE!
> Results :
> Tests in error:
>   testCheckAndSetACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): 
> org.apache.hcatalog.common.HCatException : 9001 : Exception occurred while 
> processing HCat request : MetaException while creating HMS client. Cause : 
> MetaException(message:Could not connect to meta store using any of the URIs 
> provided. Most recent failure: 
> org.apache.thrift.transport.TTransportException: java.net.ConnectException: 
> Connection refused(..)
>   testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): Could not 
> configure server because SASL configuration did not allow the  ZooKeeper 
> server to authenticate itself properly: 
> javax.security.auth.login.LoginException: Bad JAAS configuration: 
> unrecognized option: storeKey
> ..
> Traces On 
> target/./surefire-reports/org.apache.oozie.util.TestZKUtilsWithSecurity-output.txt
> at 
> com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767)
> at 
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568)
> at 
> com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)
> at 
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313)
> at 
> com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3965)
> at 
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764)
> at 
> org.apache.hcatalog.common.HiveClientCache.getOrCreate(HiveClientCache.java:167)
> at 
> org.apache.hcatalog.common.HiveClientCache.get(HiveClientCache.java:143)
> at 
> org.apache.hcatalog.common.HCatUtil.getHiveClient(HCatUtil.java:548)
> at 
> org.apache.hcatalog.api.HCatClientHMSImpl.initialize(HCatClientHMSImpl.java:596)
> ... 27 more
> testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity)  Time 
> elapsed: 0.009 sec  <<< ERROR!
> java.io.IOException: Could not configure server because SASL configuration 
> did not allow the  ZooKeeper server to authenticate itself properly: 
> javax.security.auth.login.LoginException: Bad JAAS configuration: 
> unrecognized option: storeKey
> at 
> org.apache.zookeeper.server.ServerCnxnFactory.configureSaslLogin(ServerCnxnFactory.java:207)
> at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:87)
> at 
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:111)
> at 
> org.apache.curator.test.TestingZooKeeperMain.runFromConfig(TestingZooKeeperMain.java:73)
> at 
> org.apache.curator.test.TestingZooKeeperServer$1.run(TestingZooKeeperServer.java:134)
> at java.lang.Thread.run(Thread.java:863)
> ...
> howto reproduce :
> git clone -b branch-4.1 https://github.com/apache/oozie.git
> cd oozie
> ./bin/mkdistro.sh -DskipTests -Phadoop-2
> cd zookeeper-security-tests/
> mvn clean test -Phadoop-2



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

[jira] [Commented] (OOZIE-2259) Create a callback action

2015-11-25 Thread Jaydeep Vishwakarma (JIRA) 

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

Jaydeep Vishwakarma commented on OOZIE-2259:


Thanks you again [~rkanter] :), I have updated the patch.

> 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, OOZIE-2259_v6.patch, 
> OOZIE-2259_v7.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)