I'm working a sizeable oozie (CDH oozie 4.1.0) deployment, where workflows and coordinators are constantly being updated. I have two problems though:
1. I am not sure why, but my bundles are constantly in the SUSPENDED state. sometimes this results in all of the coordinators within them being marked as suspended, and sometimes the coordinators remain running. Is there any way a bundle could become suspended on its own somehow? 2. When I resume a suspended coordinator, it immediately starts submitting all of the "missed" actions, but I actually just want it to do this once, or wait until the next materialization time. I realize this is explicit behaviour in the docs. Is there a flag to disable this on the service itself? thanks! Oren
