Mailing List Archive: Q: Avoid resource restart after configuration change

Hi!

I'd like to change a resource's configuration, but don't want a restart of the resource. That is, I want the configuration to be effective the next time the resource is started.

I know in general it doesn't make sense, but for cLVM it does: Per default debug logging is on and it floods the syslog with junk.
If I want to turn off debug logging, I'll have to pass an extra parameter to clvmd, or I could do "clvmd -d0 -C" to fix the problem until next resource start.

As cLVMd is clones to all nodes in the cluster, a configuration change would effectively halt the whole cluster (all users of cLVM). I want to avoid that. As you can see, I can change the running resources, and I can configure the resources to be fine next time they restart.

So all I need is way to prevent a restart of clvmd when changing its resource configuration.

Regards,
Ulrich

_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

> On 1 Dec 2014, at 7:46 pm, Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> wrote:
>
> Hi!
>
> I'd like to change a resource's configuration, but don't want a restart of the resource. That is, I want the configuration to be effective the next time the resource is started.
>
> I know in general it doesn't make sense, but for cLVM it does: Per default debug logging is on and it floods the syslog with junk.
> If I want to turn off debug logging, I'll have to pass an extra parameter to clvmd, or I could do "clvmd -d0 -C" to fix the problem until next resource start.
>
> As cLVMd is clones to all nodes in the cluster, a configuration change would effectively halt the whole cluster (all users of cLVM). I want to avoid that. As you can see, I can change the running resources, and I can configure the resources to be fine next time they restart.
>
> So all I need is way to prevent a restart of clvmd when changing its resource configuration.

You could make it in a scratch copy of the cib, note the new digests in the status section and include those in your update.
Alternatively, use maintenance-mode and crm_resource -C
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems