Yup, that stuff goes directly to hadoop-daemon.sh (or whatever the name is) and circumvent the normal init.d (systemd when supported) life-cycle managements. Meaning that no environment will be read, etc.
Cos On Wed, Apr 27, 2016 at 09:43PM, Bruno Mahé wrote: > Do these scripts actually work with Apache Bigtop packages? > Last I remember they were also making strong assumptions about the > layout of the files and would just not work. > > Thanks, > Bruno > > On 04/27/2016 04:33 AM, MrAsanjar . wrote: > >Roman, > >I respectfully disagree and not going to start a debate on proper test and > >development methodology, as they are very much so customer and workload > >centric. > >Regardless, I would like to propose to package these scripts > >separately (i.e. called hadoop-utils.deb/rpm) and let the admin decide > >whether to utilize these scripts. > > > >On Tue, Apr 26, 2016 at 7:17 PM, Roman Shaposhnik <[email protected]> > >wrote: > > > >>On Tue, Apr 26, 2016 at 4:23 PM, MrAsanjar . <[email protected]> wrote: > >>>these scripts get used extensively as part of our test and development, > >>as > >>>it provides lightweight cluster management without having any > >>dependencies > >>>on other tools like Ambari and puppet. > >>Then I have to ask: if you're testing this as part of your end-to-end > >>system > >>testing you're really not testing the right thing (remember: in production > >>those scripts are gone in pretty much most of the distros). > >> > >>If you're simply testing Hadoop from a quick smoke test perspective, why > >>bother with packages to begin with? Untar the binary tarball an go. > >> > >>Thanks, > >>Roman. > >> > >>P.S. I remember having this exact discussion with Cloudera QA team way back > >>when: if you're not testing what your customers will be deploying you're > >>not > >>really testing much. > >> >
signature.asc
Description: Digital signature
