Doyle, Have you thrown it in all input operators? It starts from the operator you throw it in and propagates downstream. All operators need to shutdown before application changes state.
Regards, Ashwin. On Aug 11, 2016 5:01 AM, "Doyle, Austin O." <[email protected]> wrote: > The ShutdownException does stop the operator but doesn’t seem to update > the state of the application, still in the RUNNING state. Is there > something specific I need to put in the endwindows or teardowns? > > > > *From:* Chinmay Kolhatkar [mailto:[email protected]] > *Sent:* Thursday, August 11, 2016 2:12 AM > *To:* [email protected] > *Subject:* Re: Apex Finished Status > > > > Just one additional information to what Sandesh said. ShutdownException > shuts down the operator from which its thrown and all downstream operators > to that operator. > > Hence if you want the DAG to shutdown completely, you need to throw > ShutdownException from all *input* operators. > > > > -Chinmay. > > > > > > On Thu, Aug 11, 2016 at 9:58 AM, Sandesh Hegde <[email protected]> > wrote: > > Hello Austin, > > > > Throwing ShutdownException from the operators will shutdown the Apex > Application. > > > > > > On Wed, Aug 10, 2016 at 8:56 AM Doyle, Austin O. < > [email protected]> wrote: > > When would an Apex Application return a FINISHED status from YARN as > opposed to continually being in the RUNNING state? > > Is there a way to force the YARN status to FINISHED from within the > application when processing is complete? > > >
