With Pacemaker 1.1.8 and drbd 8.4.2, we are observing that when the primary
node is put into standby mode ('crm node standby') the drbd resource on the
secondary node refuses to be promoted because it is in a WFConnection state. Is
this normal and by design? I don't recall seeing this behavior on our older
clusters. What is supposed to happen when the primary node is put in standby or
suddenly crashes?
--
Eric Robinson
Director of Information Technology
Physician Select Management, LLC
775-885-2211 x 111
Disclaimer - December 6, 2012
This email and any files transmitted with it are confidential and intended
solely for [email protected]. If you are not the named addressee you
should not disseminate, distribute, copy or alter this email. Any views or
opinions presented in this email are solely those of the author and might not
represent those of Physicians' Managed Care or Physician Select Management.
Warning: Although Physicians' Managed Care or Physician Select Management has
taken reasonable precautions to ensure no viruses are present in this email,
the company cannot accept responsibility for any loss or damage arising from
the use of this email or attachments.
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
