Hi Mingjiang, Thanks! Yes, i was also trying this and is working in my scenario.
Best, -Thomas On Mon, Nov 10, 2014 at 1:09 AM, Mingjiang Shi <[email protected]> wrote: > Hi Thomas, > I think this can be achieved by modifying the file role_command_order.json > under the stack definition folder (e.g. BIGTOP/0.8). > > Here is an example that defines the namenode should be started before > starting the secondary namenode > > "SECONDARY_NAMENODE-START": ["NAMENODE-START"] > > > Hope this helps. > > > On Mon, Nov 10, 2014 at 4:49 PM, Thomas Yu <[email protected]> wrote: > >> Hi, >> >> I'm trying to extend ambari with a new stack and service definition, but >> one of my service is depending on HDFS. I had tried to use the >> <requiredServices> as well as <dependencies> tags in the metainfo.xml, but >> that doesn't help so far. >> >> Basically, i'll need my service, e.g. "service1", to start only after HDFS >> had been started, since the service need to initialize certain files in >> the >> HDFS. Is there a way to achieve that ? >> >> If possible, i would also like to control the sequence of installation >> (i.e. having my service install after HDFS). Is this possible ? >> >> >> Thanks, >> >> -Thomas >> > > > > -- > Cheers > -MJ > > -- > You received this message because you are subscribed to the Google Groups > "Internal HD OSS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/pivotal.io/d/msgid/internal-hd-oss/CAP-cZMb_ir8fR1Tru6T6mGJxSiRp8TftWQi3ZNVKB8xpoHPrsg%40mail.gmail.com > <https://groups.google.com/a/pivotal.io/d/msgid/internal-hd-oss/CAP-cZMb_ir8fR1Tru6T6mGJxSiRp8TftWQi3ZNVKB8xpoHPrsg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . >
