Re: [ClusterLabs] trace of resource - sometimes restart, sometimes not
- On 7 Oct, 2022, at 01:08, Ken Gaillot kgail...@redhat.com wrote: > > Yes, trace_ra is an agent-defined resource parameter, not a Pacemaker- > defined meta-attribute. Resources are restarted anytime a parameter > changes (unless the parameter is set up for reloads). > > trace_ra is unusual in that it's supported automatically by the OCF > shell functions, rather than by the agents directly. That means it's > not advertised in metadata. Otherwise agents could mark it as > reloadable, and reload would be a quick no-op. > OK. But why no restart if i just set "crm resource trace dlm monitor" ? Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] trace of resource - sometimes restart, sometimes not
On Fri, Oct 7, 2022 at 6:05 AM Lentes, Bernd wrote: > > > - On 7 Oct, 2022, at 01:08, Ken Gaillot kgail...@redhat.com wrote: > > > > > Yes, trace_ra is an agent-defined resource parameter, not a Pacemaker- > > defined meta-attribute. Resources are restarted anytime a parameter > > changes (unless the parameter is set up for reloads). > > > > trace_ra is unusual in that it's supported automatically by the OCF > > shell functions, rather than by the agents directly. That means it's > > not advertised in metadata. Otherwise agents could mark it as > > reloadable, and reload would be a quick no-op. > > > > OK. But why no restart if i just set "crm resource trace dlm monitor" ? I would guess that it's because `crm resource trace dlm monitor` updates only a resource operation's attributes, while `crm resource trace dlm` updates the resource's instance attributes. An update to the operation attributes might not get considered when calculating the digest, while an update to the instance attributes does... not sure off the top of my head. Ken likely knows > > Bernd___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] trace of resource - sometimes restart, sometimes not
- On 7 Oct, 2022, at 01:08, Ken Gaillot kgail...@redhat.com wrote: > > Yes, trace_ra is an agent-defined resource parameter, not a Pacemaker- > defined meta-attribute. Resources are restarted anytime a parameter > changes (unless the parameter is set up for reloads). > > trace_ra is unusual in that it's supported automatically by the OCF > shell functions, rather than by the agents directly. That means it's > not advertised in metadata. Otherwise agents could mark it as > reloadable, and reload would be a quick no-op. > OK. But why no restart if i just set "crm resource trace dlm monitor" ? Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] trace of resource - sometimes restart, sometimes not
- On 7 Oct, 2022, at 01:18, Reid Wahl nw...@redhat.com wrote: > How did you set a trace just for monitor? crm resource trace dlm monitor. > Wish I could help with that -- it's mostly a mystery to me too ;) :-)) smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] trace of resource - sometimes restart, sometimes not
On Thu, Oct 6, 2022 at 4:08 PM Ken Gaillot wrote: > > On Thu, 2022-10-06 at 21:05 +0200, Lentes, Bernd wrote: > > Hi, > > > > i have some problems with our DLM, so i wanted to trace it. Yesterday > > i just set a trace for "monitor". No restart of DLM afterwards. It > > went fine as expected. How did you set a trace just for monitor? > > I got logs in /var/lib/heartbeat/trace_ra. After some monitor i > > stopped tracing. > > > > Today i set a trace for all operations. > > Now resource DLM restarted: > > * Restartdlm:0 ( ha-idg-1 > > ) due to resource definition change > > I didn't expect that so i had some trouble. > > Is the difference in this behaviour intentional ? If yes, why ? Is > > there a rule ? > > Yes, trace_ra is an agent-defined resource parameter, not a Pacemaker- > defined meta-attribute. Resources are restarted anytime a parameter > changes (unless the parameter is set up for reloads). > > trace_ra is unusual in that it's supported automatically by the OCF > shell functions, rather than by the agents directly. That means it's > not advertised in metadata. Otherwise agents could mark it as > reloadable, and reload would be a quick no-op. > > > > > Furthermore i'd like to ask where i can find more information about > > DLM, because it is a mystery for me. Wish I could help with that -- it's mostly a mystery to me too ;) > > Sometimes the DLM does not respond to the "monitor", so it needs to > > be restarted, and therefore all depending resources (which is a lot). > > This happens under some load (although not completely overwhelmed). > > > > Thanks. > > > > Bernd > > > -- > Ken Gaillot > > ___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ > -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] trace of resource - sometimes restart, sometimes not
On Thu, 2022-10-06 at 21:05 +0200, Lentes, Bernd wrote: > Hi, > > i have some problems with our DLM, so i wanted to trace it. Yesterday > i just set a trace for "monitor". No restart of DLM afterwards. It > went fine as expected. > I got logs in /var/lib/heartbeat/trace_ra. After some monitor i > stopped tracing. > > Today i set a trace for all operations. > Now resource DLM restarted: > * Restartdlm:0 ( ha-idg-1 > ) due to resource definition change > I didn't expect that so i had some trouble. > Is the difference in this behaviour intentional ? If yes, why ? Is > there a rule ? Yes, trace_ra is an agent-defined resource parameter, not a Pacemaker- defined meta-attribute. Resources are restarted anytime a parameter changes (unless the parameter is set up for reloads). trace_ra is unusual in that it's supported automatically by the OCF shell functions, rather than by the agents directly. That means it's not advertised in metadata. Otherwise agents could mark it as reloadable, and reload would be a quick no-op. > > Furthermore i'd like to ask where i can find more information about > DLM, because it is a mystery for me. > Sometimes the DLM does not respond to the "monitor", so it needs to > be restarted, and therefore all depending resources (which is a lot). > This happens under some load (although not completely overwhelmed). > > Thanks. > > Bernd > -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
