+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
wrote:
>
> +1 Reka. I hope this won't be a global level lock rather a cluster level
> lock.
>
> On Sun, Dec 14, 2014
+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
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 parti
A good thought Reka, this issue was there with the minimum rule in the
previous release as well. We could try this out.
Thanks
On Sun, Dec 14, 2014 at 10:07 AM, Reka Thirunavukkarasu
wrote:
>
> Hi All,
>
> As we now support adding cluster instances dynamically, we will have to
> wait for next on
Makes sense, we will definitely need locking support before this.
Thanks.
On Sun, Dec 14, 2014 at 10:07 AM, Reka Thirunavukkarasu
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 particula
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
