Hi Sanjay, thanks for your response.
These days im getting the same issue more frequently. And the suggested solution to kill the job is not a good idea. As in our flow Once the first App shutdown successfully,next app will launch and proceed further. Please suggest how we can dealt *If an operator is stuck in “teardown()” it can prevent successful shutdown of the application and it could show up as RUNNING indefinitely*. Thanks Chiranjeevi V On Wed, Jan 4, 2017 at 3:27 AM, Sanjay Pujare <[email protected]> wrote: > Chiranjeevi > > > > Shutdown requires that an application’s all containers/operators are “torn > down” gracefully as part of processing the latest window. If an operator is > stuck in “teardown()” it can prevent successful shutdown of the application > and it could show up as RUNNING indefinitely. > > > > If you don’t want to debug these issues in teardown() you can just kill > the application thru the Yarn REST API > > > > Sanjay > > > > *From: *chiranjeevi vasupilli <[email protected]> > *Reply-To: *<[email protected]> > *Date: *Tuesday, January 3, 2017 at 6:10 AM > *To: *<[email protected]> > *Subject: *DT job not getting finished > > > > Hi Team, > > > > In my use case , i have two dags to completed the processing. And iam > using curl command to shutdown the application. > > > > But some times we are facing an issue to shutdown the first dag . From DT > console we are able to see that the application has released all the > resources but it remains in RUNNING state for infinite time. > > > > Please suggest . > > > [image: nline image 1] > > > > -- > > ur's > chiru > -- ur's chiru
