So do you mean that the install order does not like my thought? ----- Original Message ----- From: "Di Li" <[email protected]> To: [email protected] Sent: Wednesday, March 21, 2018 8:45:06 PM Subject: Re: Questions aboute install order
metainfo only list direct dependencies. RCO only dictates what a dependent should do when it INSTALL/START if its dependencies are also INSTALL-*ing*, START-*ing*, etc. You can verify this by running a start all, where high level services waits for their dependencies to start. It does not, howerver, let Ambari install/start dependencies for you. You can easily verify this by starting a high level service such as HBASE and has RCO depdencies on HDFS. On Wed, Mar 21, 2018 at 4:11 AM, <[email protected]> wrote: > Hi! > > I know that when choose services, i can define service dependence in > service's metainfo.xml, > at the same time, i can define order in role_command_order.json. > > > I have some questions: > > 1) why the dependence in metainfo can not auto covert into > role_command_order which i think it is very cool? > A depend on B, so install B before install A, isn't it? > > 2) If A depend on B and C, D depend on A and E, i define in > role_command_order.json as below: > > A_CLIENT_INSTALL: [B_CLIENT_INSTALL, C_CLIETN_INSTALL], > D_CLIENT_INSTALL: [A_CLIENT_INSTALL, E_CLIETN_INSTALL], > > > so the install order is B,C,A,E,D , right? >
