Caleb,
Sorry, made a mistake there. In the simple case the application has the
simple classname, not the full one.
-Martin
On 02/10/2017 02:02 PM, Martin Serrano wrote:
Caleb,
The TwillRunnerService handles the ZK registration of applications for
you. When TwillClient B starts the service it can get the controllers
for the application via the TwillRunnerService.lookup method. If you
did not explicitly name your application, then your are probably using
the prepare method that names the application to the full classname of
your runnable.
-Martin
On 02/09/2017 10:53 AM, Meier, Caleb wrote:
Hello,
Suppose that I start an instance of NotificationRunnable with
TwillClient A. NotificationRunnable continues to run after
TwillClient A terminates (I no longer have a handle on the
YarnTwillRunner that prepared it), but I want to send a command to
NotificatonRunnable using an instance of TwillController that I
create in TwillClient B. Is this possible? It seems like I would
still need access to the YarnTwillRunner that started the
NotificationRunnable. I’m basing this on the source code for
YarnTwillRunner.lookup(…) – it seems like this method only returns
controllers for runnables that the enclosing instance of
YarnTwillRunner has prepared. Am I mistaken about this? If not, do
I need to explicitly register my application with a
ZkDiscoveryService and then look it up later through the same
service? Is there a better way to go about this?
Thanks,
Caleb A. Meier, Ph.D.
Software Engineer II ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office: (703)797-3066
caleb.me...@parsons.com<mailto:caleb.me...@parsons.com> ♦
www.parsons.com<https://webportal.parsons.com/,DanaInfo=www.parsons.com+>
