Hi Isuru, Yes the autoscaler.xml is overwritten by the file inside *s* tratos-installer/config/all/repository/conf/*autoscaler.xml, *which misses the expiryTimeout config. This was fixed in both 4.0.0 branch as well as in the Master in the commits [1 <https://github.com/apache/stratos/commit/6eb9819e8704e2caa6009bca3aa41c5c51efedab>] and [2 <https://github.com/apache/stratos/commit/0b982f740e9ca2b6785d0f518acb3ab33e4d4578>] respectively.
@Prasanna: If you are using the rc4, this fix is not there. So you'll have to manually add the above config. Thanks, Lasindu On Thu, Aug 7, 2014 at 11:35 AM, Isuru Haththotuwa <[email protected]> wrote: > Hi Prasanna, > > In my local build, there is a section named expiryTimeout in the > autoscaler.xml, which corresponds to the initial time period waited before > marking a member as obsolete. In your case, this seem to be missing. Since > you are using a puppet based deployment, its possible that this file has > been overwritten by an outdated file in the puppet master side. Could you > please check on this? > > > On Thu, Aug 7, 2014 at 11:23 AM, Prasanna Dangalla <[email protected]> > wrote: > >> Hi >> >> I'm doploying a php cartrige using stratos and a puppet master. After 15 >> minites it says the following message and starts deploying another cartrige. >> >> >> *Pending state of member: >> prasanew8.php.domaina9a84401-34af-489c-85bf-5f2e1e4fa4ac is expired. Adding >> as an obsoleted member. {org.apache.stratos.autoscaler.PartitionContext}* >> >> >> My stratos installer config/all/repository/conf/autoscaler.xml file looks >> like this. () >> >> <configuration> >> <autoscaler> >> <rulesEvaluator> >> <schedule> >> <initialDelay>30</initialDelay> >> <period>15</period> >> </schedule> >> </rulesEvaluator> >> <cloudController> >> <hostname>CC_HOSTNAME</hostname> >> <port>CC_LISTEN_PORT</port> >> <clientTimeout>300000</clientTimeout> >> </cloudController> >> <stratosManager> >> <hostname>SM_HOSTNAME</hostname> >> <port>SM_LISTEN_PORT</port> >> <!-- <clientTimeout>300000</clientTimeout> --> >> <clientTimeout>900000</clientTimeout> >> </stratosManager> >> </autoscaler> >> </configuration> >> >> I adjusted stratosManager clientTimeout and reinstalled stratos. Still it >> start deploying a new one after 15 minitus. Is there another place to >> change this ? >> >> Thanks >> >> Prasanna Dangalla >> Software Engineer, WSO2, Inc.; http://wso2.com/ >> lean.enterprise.middleware >> >> cell: +94 777 55 80 30 | +94 718 11 27 51 >> twitter: @prasa77 >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> * <http://wso2.com/>* >> >> >> -- *Lasindu Charith* Software Engineer, WSO2 Inc. Mobile: +94714427192 Web: blog.lasindu.com
