Hi, To test a custom action, I'd recommend simply running it in an Oozie server and seeing if you run into any problems. You can also attach a debugger to Oozie to help there. To save on turn-around time, you can also write a unit test that starts up LocalOozie and tries to submit your action. To attach a debugger to Oozie, you should add the following to the "Oozie Service Environment Advanced Configuration Snippet (Safety Valve)" in Cloudera Manager (if not using CM, then you'd export this in oozie-env.sh: CATALINA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005" Besides using the debugger I mentioned above, looking at the launcher output (assuming you added print statements) can also be helpful; you can attach a debugger to the launcher job, but that's a bit harder because you need to attach it to the MR container instead of the Oozie server. Oozie is pretty easy to run anywhere. You can run it in a VM, on a cluster, or even on your Mac. When developing for Oozie, I typically run it on my Mac against a pseudo-distributed cluster, also on my Mac. You can use oozie.service.HadoopAccessorService.hadoop.configurations to point Oozie at any Hadoop cluster, or even multiple ones. Nothing special. Just make sure that your custom action's jar is in the Oozie servers classpath and that if your custom action has a sharelib, it's deployed in HDFS and Oozie sees it.
... View more
