I have not tried this hive.server2.idle.operation.timeoutWith hive.server2.session.check.interval set to a positive time value, operation will be closed when it's not accessed for this duration of time, which can be disabled by setting to zero value. With positive value, it's checked for operations in terminal state only (FINISHED, CANCELED, CLOSED, ERROR). With negative value, it's checked for all of the operations regardless of state. hive.server2.idle.session.timeoutWith hive.server2.session.check.interval set to a positive time value, session will be closed when it's not accessed for this duration of time, which can be disabled by setting to zero or negative value. and if it was metastore issue, did you try: hive.metastore.client.socket.timeoutMetaStore Client socket timeout in seconds. ... View more

I should have done a bit more research... this is a problem in Storm 0.10, but it looks like the upcoming Storm 1.0 release will handle this situation by allowing properties to be passed directly to the Kafka Bolt instead of indirectly through the Topology configuration: https://github.com/apache/storm/blob/master/external/storm-kafka/src/jvm/org/apache/storm/kafka/bolt/KafkaBolt.java#L87-L90 ... View more

To answer my own question, the oozie user mailing list led me to this option within the java action configuration: <property> <name>oozie.launcher.mapreduce.user.classpath.first</name> <value>true</value> </property> https://mail-archives.apache.org/mod_mbox/oozie-us... See also OOZIE-2066: https://issues.apache.org/jira/browse/OOZIE-2066 ... View more