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
On 4/3/18
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 Home: http
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"
<users-boun...@clusterlabs.org on behalf of arvidj...@gm
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"
<users-boun...@clusterlabs.org on behalf of sgard...@trustwave.com> wrote:
>Thanks, Ken.
>
>I just want all master-mod
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.
--
Sam Gardner
section of my CIB (full CIB is attached):
--
Sam Gardner
Trustwave | SMART SECURITY ON D
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" <kgail...@redhat.com> wrote:
>
[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
This transmission
-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" <sgard...@trustwave.com> wrote:
>'on-fail=standby' works well, however, setting a failure-timeout appears
>to automatica
'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" <kgail...@redhat.com> wrote:
>On 03/28
-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
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" <lars.ellenb...@linbit.com> wrote:
>On Fri, Mar 25, 2016 at 04:08:48PM +, Sam Gardner wrote:
>> On 3/25/16, 10:26 AM, &quo
On 3/25/16, 10:26 AM, "Lars Ellenberg" <lars.ellenb...@linbit.com> 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
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" <emi2f...@gmail.com> wrote:
>If you don't want INFINITY after the node is begin r
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 Gardner
Trustwave | SMART
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
recipient, you are hereby notified that any
16 matches
Mail list logo