Hi,

I see from the source that the TwillRunnerService is locating existing
controllers by querying ZK in the background.  Since these run in the
background, there seems to be no way to know when the requests are
complete.  Thus, on starting up the service, I can't reliably determine
the complete set of controllers running from previous sessions.  Is
there a way to know?  Is there a listener I can register?

Also, I see that YarnTwillController internally determines the current
application state (RUNNING, ACCEPTED, etc) via a YarnAppicationReport. 
Is there any public API for this information?

Basically I'm trying to work through the problem of submission of an
application, monitoring the current state, detecting somehow that it is
going to stay stuck in the ACCEPTED state, and then working out why. 
Sometimes it is lack of memory resources, sometimes cpu.  Is there any
programmatic way?

Thanks,
Martin Serrano

Reply via email to