<div dir="ltr">Hi Ulrich, thanks for the answer, <div>as Ken explained me, there isnt any way to prevent earlier members from running<br>if a later member has no available node, </div><div>if no node is available for the failed member, then it will just remain<br>stopped,and the earlier<br>members will stay active where they are. <br></div><div>i really hope was a solution or workaorund for this, but as ken clarify, pacemaker cant hadle this exceptions.</div><div><br></div><div>Many thanks for your quick and effective support.</div><div><br></div><div>Have a good evening!</div><div><br></div><div>Damiano</div><div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno gio 28 gen 2021 alle ore 11:15 Ulrich Windl <<a href="mailto:Ulrich.Windl@rz.uni-regensburg.de">Ulrich.Windl@rz.uni-regensburg.de</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">>>> damiano giuliani <<a href="mailto:damianogiuliani87@gmail.com" target="_blank">damianogiuliani87@gmail.com</a>> schrieb am 27.01.2021 um<br>
19:25<br>
in Nachricht<br>
<CAG=zYNOx-R=wKbhtm=4N7qaoYKE=<a href="mailto:ofORVQ7jA0jr17oYjgqOhQ@mail.gmail.com" target="_blank">ofORVQ7jA0jr17oYjgqOhQ@mail.gmail.com</a>>:<br>
> Hi Andrei, Thanks for ur help.<br>
> if one of my resource in the group fails or the primary node went down (<br>
> in my case acspcmk-02 ), the probe notices it and pacemaker tries to<br>
> restart the whole resource group on the second node.<br>
> if the second node cant run one of my grouped resources, it tries to stop<br>
> them.<br>
<br>
And what exactly is what you want? The behavior described it how the cluster<br>
handles it normally.<br>
<br>
> <br>
> <br>
> i attached my cluster status; my primary node ( acspcmk-02 ) fails and the<br>
> resource group tries to restart on the acspcmk-01, i keep broken the<br>
> resource "lta-subscription-backend-ope-s3" on purpose and as you can see<br>
> some grouped resources are still started..<br>
> i would like to know how achive a condition that the resource group must<br>
> start properly for each resources, if not stop all the group without some<br>
> services still up and running.<br>
> <br>
> <br>
> 2 nodes configured<br>
> 28 resources configured<br>
> <br>
> Online: [ acspcmk-01 ]<br>
> OFFLINE: [ acspcmk-02 ]<br>
> <br>
> Full list of resources:<br>
> <br>
> Clone Set: lta-odata-frontend-ope-s1-clone [lta-odata-frontend-ope-s1]<br>
> Started: [ acspcmk-01 ]<br>
> Stopped: [ acspcmk-02 ]<br>
> Clone Set: lta-odata-frontend-ope-s2-clone [lta-odata-frontend-ope-s2]<br>
> Started: [ acspcmk-01 ]<br>
> Stopped: [ acspcmk-02 ]<br>
> Clone Set: lta-odata-frontend-ope-s3-clone [lta-odata-frontend-ope-s3]<br>
> Started: [ acspcmk-01 ]<br>
> Stopped: [ acspcmk-02 ]<br>
> Clone Set: s1ltaestimationtime-clone [s1ltaestimationtime]<br>
> Started: [ acspcmk-01 ]<br>
> Stopped: [ acspcmk-02 ]<br>
> Clone Set: s2ltaestimationtime-clone [s2ltaestimationtime]<br>
> Started: [ acspcmk-01 ]<br>
> Stopped: [ acspcmk-02 ]<br>
> Clone Set: s3ltaestimationtime-clone [s3ltaestimationtime]<br>
> Started: [ acspcmk-01 ]<br>
> Stopped: [ acspcmk-02 ]<br>
> Clone Set: openresty-clone [openresty]<br>
> Started: [ acspcmk-01 ]<br>
> Stopped: [ acspcmk-02 ]<br>
> Resource Group: LTA_SINGLE_RESOURCES<br>
> VIP (ocf::heartbeat:IPaddr2): Started acspcmk-01<br>
> lta-subscription-backend-ope-s1<br>
> (systemd:lta-subscription-backend-ope-s1): Started acspcmk-01<br>
> lta-subscription-backend-ope-s2<br>
> (systemd:lta-subscription-backend-ope-s2): Started acspcmk-01<br>
> lta-subscription-backend-ope-s3<br>
> (systemd:lta-subscription-backend-ope-s3): Stopped<br>
> s1ltaquotaservice (systemd:s1ltaquotaservice): Stopped<br>
> s2ltaquotaservice (systemd:s2ltaquotaservice): Stopped<br>
> s3ltaquotaservice (systemd:s3ltaquotaservice): Stopped<br>
> s1ltarolling (systemd:s1ltarolling): Stopped<br>
> s2ltarolling (systemd:s2ltarolling): Stopped<br>
> s3ltarolling (systemd:s3ltarolling): Stopped<br>
> s1srvnotificationdispatcher<br>
> (systemd:s1srvnotificationdispatcher): Stopped<br>
> s2srvnotificationdispatcher<br>
> (systemd:s2srvnotificationdispatcher): Stopped<br>
> s3srvnotificationdispatcher<br>
> (systemd:s3srvnotificationdispatcher): Stopped<br>
> <br>
> Failed Resource Actions:<br>
> * lta-subscription-backend-ope-s3_start_0 on acspcmk-01 'unknown error'<br>
> (1): call=466, status=complete, exitreason='',<br>
> last-rc-change='Wed Jan 27 13:00:21 2021', queued=0ms, exec=2128ms<br>
> <br>
> Daemon Status:<br>
> corosync: active/disabled<br>
> pacemaker: active/disabled<br>
> pcsd: active/enabled<br>
> sbd: active/enabled<br>
> <br>
> <br>
> I hope i explained my problem at my best,<br>
> <br>
> Thanks for your time and help.<br>
> <br>
> Good Evening<br>
> <br>
> Damiano<br>
> <br>
> Il giorno mer 27 gen 2021 alle ore 19:03 Andrei Borzenkov <<br>
> <a href="mailto:arvidjaar@gmail.com" target="_blank">arvidjaar@gmail.com</a>> ha scritto:<br>
> <br>
>> 27.01.2021 19:06, damiano giuliani пишет:<br>
>> > Hi all im pretty new to the clusters, im struggling trying to configure<br>
a<br>
>> > bounch of resources and test how they failover.my need is to start and<br>
>> > manage a group of resources as one (in order to archive this a resource<br>
>> > group has been created), and if one of them cant run and still fails,<br>
the<br>
>> > cluster will try to restart the resource group in the secondary node, if<br>
>> it<br>
>> > cant run the all the resource toghter disable all the resource group.<br>
>> > i would like to know if there is a way to set the cluster to disable all<br>
>> > the resources of the group (or the group itself) if it cant be run all<br>
>> the<br>
>> > resoruces somewhere.<br>
>> ><br>
>><br>
>> That's what pacemaker group does. I am not sure what you mean with<br>
>> "disable all resources". If resource fail count on a node exceeds<br>
>> threshold, this node is banned from running resource. If resource failed<br>
>> on every node, no node can run it until you clear fail count.<br>
>><br>
>> "Disable resource" in pacemaker would mean setting its target-role to<br>
>> stopped. That does not happen automatically (at least I am not aware of<br>
>> it).<br>
>> _______________________________________________<br>
>> Manage your subscription:<br>
>> <a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a> <br>
>><br>
>> ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a> <br>
>><br>
<br>
<br>
<br>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
</blockquote></div>