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
