Re: [ClusterLabs] Advisory order for cluster-managed resources

put in place? 10 or 15 resources colocated on the same node, starting up in a consistent order will require (at least) 2x the number of constraints in this scheme - it seemed to me that sets would simplify things but perhaps not. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND

[ClusterLabs] Advisory order for cluster-managed resources

can do it with separate constraints but it seems like an order set is a useful shortcut here. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

entire group, which isn't ideal (though admittedly unlikely in this particular use case). Thanks much for all of the help, -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND On 3/25/18, 6:06 AM, "Users on behalf of Andrei Borzenkov" wrote: >25.03.2018 10:21, Alberto

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

e the constraints aren't set up correctly. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND On 3/23/18, 12:42 PM, "Users on behalf of Sam Gardner" wrote: >Thanks, Ken. > >I just want all master-mode resources to be running wherever DRBDFS is running >(essential

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

ote, there are other resources I have in play (some active/passive like DRBDFS, some Master/Slave like the ship resources) that are related, but not shown here - I'm just having a hard time reasoning about the generalized form that my constraints should take to make this sort of thing work.

[ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

quot; section of my CIB (full CIB is attached): -- Sam Gardner Trustwave | SMART SECURITY

Re: [ClusterLabs] Pacemaker on-fail standby recovery does not start DRBD slave resource

One other note: Manually standby-ing and unstandby-ing a node gives the behavior I want (eg, after the node is unstandby-ed, the DRBDSlave resource works). -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND On 3/30/16, 11:46 AM, "Ken Gaillot" wrote: >On 03/30/2016 11:20 AM, Sam

[ClusterLabs] Pacemaker on-fail standby recovery does not start DRBD slave resource

01) srcversion: 315FB2BBD4B521D13C20BF4 [154094.894574] block drbd1: disk( Failed -> Diskless ) [154094.894647] block drbd1: drbd_bm_resize called with capacity == 0 [154094.894652] drbd wwwdata: Terminating drbd_w_wwwdata -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND _

Re: [ClusterLabs] Make sure either 0 or all resources in a group are running

-n) does restart the state of the node properly, however. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND On 3/28/16, 4:31 PM, "Sam Gardner" wrote: >'on-fail=standby' works well, however, setting a failure-timeout appears >to automatically bring the node out o

Re: [ClusterLabs] Make sure either 0 or all resources in a group are running

'on-fail=standby' works well, however, setting a failure-timeout appears to automatically bring the node out of standby after it expires. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND On 3/28/16, 3:31 PM, "Ken Gaillot" wrote: >On 03/28/2016 02:19 PM, Sam Gar

[ClusterLabs] Make sure either 0 or all resources in a group are running

. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any

[ClusterLabs] Resource failure-timeout does not reset when resource fails to connect to both nodes

-threshold? -- Sam Gardner Software Engineer Trustwave | SMART SECURITY ON DEMAND This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby

Re: [ClusterLabs] Set "start-failure-is-fatal=false" on only one resource?

Thanks, I'll give a newer version a shot. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND On 3/25/16, 3:37 PM, "Lars Ellenberg" wrote: >On Fri, Mar 25, 2016 at 04:08:48PM +, Sam Gardner wrote: >> On 3/25/16, 10:26 AM, "Lars Ellenberg" >>wrote:

Re: [ClusterLabs] Set "start-failure-is-fatal=false" on only one resource?

On 3/25/16, 10:26 AM, "Lars Ellenberg" wrote: >On Thu, Mar 24, 2016 at 09:01:18PM +, Sam Gardner wrote: >> I'm having some trouble on a few of my clusters in which the DRBD Slave >>resource does not want to come up after a reboot until I manually run >>re

Re: [ClusterLabs] Set "start-failure-is-fatal=false" on only one resource?

I am using failure-timeout on the DRBDSlave resource: "Meta Attrs: failure-timeout=33s" -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND On 3/25/16, 10:00 AM, "emmanuel segura" wrote: >If you don't want INFINITY after the node is begin rebooted, you can >use

Re: [ClusterLabs] Set "start-failure-is-fatal=false" on only one resource?

rbd_resource=wwwdata Meta Attrs: failure-timeout=33s Operations: monitor interval=11s (DRBDSlave-monitor-interval-11s start interval=0s on-fail=restart (DRBDSlave-start-on-fail-restart) monitor interval=13s role=Master (DRBDSlave-monitor-interval-13s) -- Sam Gardn

[ClusterLabs] Set "start-failure-is-fatal=false" on only one resource?

12 and Corosync 1.4.8 on a RedHat 6-like system. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended rec