On 04/13/2017 08:49 AM, Radoslaw Garbacz wrote:
> Thank you, however in my case this parameter does not change the
> described behavior.
>
> I have a more detail example:
> order: res_A-clone -> res_B-clone -> res_C
> when "res_C" is not on the node, which had "res_A" instance failed, it
> will
Thank you, however in my case this parameter does not change the described
behavior.
I have a more detail example:
order: res_A-clone -> res_B-clone -> res_C
when "res_C" is not on the node, which had "res_A" instance failed, it will
not be restarted, only "res_A" and "res_B" all instances will.
On 04/06/2017 09:32 AM, Radoslaw Garbacz wrote:
> Hi,
>
>
> I have a question regarding resources order settings.
>
> Having cloned resources: "res_1-clone", "res_2-clone",
> and defined order: first "res_1-clone" then "res_2-clone"
>
> When I have a monitoring failure on a remote node with
Hi,
I have a question regarding resources order settings.
Having cloned resources: "res_1-clone", "res_2-clone",
and defined order: first "res_1-clone" then "res_2-clone"
When I have a monitoring failure on a remote node with "res_1" (an instance
of "res_1-clone") which causes all dependent
