On Fri, Feb 7, 2014 at 4:48 PM, Sheng Yang wrote:
> Thanks for the comment!
>
> On Fri, Feb 7, 2014 at 3:25 PM, Chiradeep Vittal <
> chiradeep.vit...@citrix.com> wrote:
>
>> +1.
>> * The guideline is not clear as to when a developer should use this
>> executor. Why not use it all the time (even f
Thanks for the comment!
On Fri, Feb 7, 2014 at 3:25 PM, Chiradeep Vittal <
chiradeep.vit...@citrix.com> wrote:
> +1.
> * The guideline is not clear as to when a developer should use this
> executor. Why not use it all the time (even for a single command)
>
The mechanism behind is NOT a "producer
+1.
* The guideline is not clear as to when a developer should use this
executor. Why not use it all the time (even for a single command)
* Are there any issues when there are multiple management servers involved?
* Any threading concerns? That is, multiple threads are attempting to
update the VR,
> On Feb 6, 2014, at 8:03 PM, Sheng Yang wrote:
>
> Hi Devs,
>
> Here I'd like to introduce this improvement of VR.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-6047
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Virtual+Router+aggregated+command+execution
>
> In short, we
Hi Devs,
Here I'd like to introduce this improvement of VR.
https://issues.apache.org/jira/browse/CLOUDSTACK-6047
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Virtual+Router+aggregated+command+execution
In short, we would speed up VR's rebooting and re-creating, by aggregated
execution