Didn't quite get your question. Can you please elaborate?
On Fri, Dec 6, 2013 at 12:04 PM, Lahiru Sandaruwan <[email protected]> wrote: > Nirmal, > > Do you mean CPU/ Memory consumption details or the current topology(The > partitions of the current instances)? > > > On Fri, Dec 6, 2013 at 11:58 AM, Nirmal Fernando > <[email protected]>wrote: > >> All, >> >> Currently when a new member is about to spawn, the partition would always >> be selected via an algorithm and there's no much intelligence over there. >> Ideally, what should happen is; autoscaler should identify the partition >> that it needs to spawn the next instance via the data it receives, if it >> fails only it should pick next partition up from a algorithm. >> wdyt? >> >> -- >> Best Regards, >> Nirmal >> >> Nirmal Fernando. >> PPMC Member & Committer of Apache Stratos, >> Senior Software Engineer, WSO2 Inc. >> >> Blog: http://nirmalfdo.blogspot.com/ >> > > > > -- > -- > Lahiru Sandaruwan > Software Engineer, > Platform Technologies, > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > email: [email protected] cell: (+94) 773 325 954 > blog: http://lahiruwrites.blogspot.com/ > twitter: http://twitter.com/lahirus > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 > > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
