+1. A read write locking model can be used (similar to the one we have in Topology and Applications) at the cluster monitor level.
On Sun, Dec 14, 2014 at 7:19 AM, Nirmal Fernando <nirmal070...@gmail.com> wrote: > > +1 Reka. I hope this won't be a global level lock rather a cluster level > lock. > > On Sun, Dec 14, 2014 at 10:07 AM, Reka Thirunavukkarasu <r...@wso2.com> > wrote: > >> Hi All, >> >> As we now support adding cluster instances dynamically, we will have to >> wait for next one minute to get the members started in that particular >> cluster instance which will delay other dependencies startup when it comes >> to scaling or terminate and start again. Also, after adding the members in >> obsolete member list when terminating a cluster, we will again have to wait >> for one minute to get the members terminated. This will delay the action >> based on the termination specially when it comes to terminate-dependent or >> terminate-all scenarios. >> >> Can we do $subject by introducing locking support for the cluster >> monitor? So that whenever needed, we can directly execute the cluster >> monitor by taking lock to take decision only for min check and obsolete >> check. Let Cluster monitor periodically execute to take decision like min >> check, obsolete check and scaling. Because, AFAIK for scaling we will have >> to wait minimum one minute to get all the latest stats. >> >> Thanks, >> Reka >> >> -- >> Reka Thirunavukkarasu >> Senior Software Engineer, >> WSO2, Inc.:http://wso2.com, >> Mobile: +94776442007 >> >> >> > > -- > Best Regards, > Nirmal > > Nirmal Fernando. > PPMC Member & Committer of Apache Stratos, > Senior Software Engineer, WSO2 Inc. > > Blog: http://nirmalfdo.blogspot.com/ > > -- > <http://nirmalfdo.blogspot.com/> > <http://nirmalfdo.blogspot.com/> > Thanks and Regards, > > Isuru H. > <http://nirmalfdo.blogspot.com/> > +94 716 358 048 <http://nirmalfdo.blogspot.com/>* <http://wso2.com/>* > > > * <http://wso2.com/>* > > >
