Note that drillbit.sh does quite a bit of setup, then turns around to call runbit. You’ll have to duplicate that setup in your own wrapper script. As an alternative, you can create a new “command” in drillbit.sh to call runbit in the foreground.
This same issue arose in the Drill-on-YARN work and the “run in foreground” option in drillbit.sh was my first attempt at solving the problem. In the end, we created a purpose-built script for running under YARN to handle other YARN weirdness. Still, when I check in the YARN work, perhaps I should leave the “run in foreground” option in drillbit.sh for cases such as this. Thoughts? Thanks, - Paul > On May 29, 2016, at 8:59 AM, Charles Nnamdi Akalugwu <[email protected]> > wrote: > > ah excellent John!! That is exactly what I wanted! :) > > On Sun, May 29, 2016 at 5:00 PM, John Omernik <[email protected]> wrote: > >> Instead of using drillbit.sh use runbit. I use that with Marathon on Mesos, >> and it runs it in the foreground and works well. >> >> John >> >> >> >> On Sun, May 29, 2016 at 9:55 AM, Charles Nnamdi Akalugwu < >> [email protected]> wrote: >> >>> Hi guys, >>> >>> I would like to manage the lifecycle of my drillbits using supervisord. >> The >>> first problem is that the drillbit script get detached and does not run >> in >>> the foreground. My question is this: how can I get to run the drillbits >> in >>> the foreground to allow me use supervisord to manage them? >>> >>> Best regards >>> >>
