So I am now worried I have messed up my own installations on Mesos, so I dove into the two scripts, and found that main things that drillbit.sh sets up is logging. I have moved that to my drill-env.sh which via drill-config is called when executing the runbit. I setup the logging etc there, because I wanted to be in more control of what is happening with logging and I use MapRFS as my logging destination rather than local hosts... just makes more sense to have the logs centralized. The only others things I noticed in the drillbit.sh were:
niceness - I don't set niceness, but per drillbit.sh it sets it to 0 and that's the default, so I think I ok here and then the GC Server options which I think have to do with logging more than anything. (Maybe I am reading that wrong) Basically, as I am reading things, as long as I setup logging (which I do in drill-env, I should be good with runbit. If I am missing something here, please let me know :) On Sun, May 29, 2016 at 4:42 PM, John Omernik <[email protected]> wrote: > So what does drillbit.sh setup that is missing from runbit? It's been > working for me, but am I missing something? :) > > > On Sunday, May 29, 2016, Paul Rogers <[email protected]> wrote: > >> 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 >> >>> >> >> >> >> > > -- > Sent from my iThing >
