Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Monday 24 May 2004 17:06, Martin Bene wrote: > > So, what do you suggest ? -- Unfortunately heartbeat does not > > take hints > > from DRBD. The only way to make sure that heartbeat does not > > activate a > > resource is to not start it at all. > > > > We are aware of the problem and working on it. But do not > > expect that we > > will change anything in DRBD-0.6.x . > > > > Development happens at DRBD-0.7. Although it is not formal, I would > > say we are already in a kind of feature freeze for 0.7. > > Hmm, the obvious approach would be an option to return a resource to > unconfigured state if the 2nd node can't be reached within a timeout. > You'd end up with two configured and one unconfigured drbd device. In > the previously mentioned example. > > If heartbeat subsequenctly tries to activate a resource on that > unconfigured device, it will fail, while still allowing other resources > to come up. > > An administrator would be able to configure / start drbd + corresponding > services on whatever node he likes. None too sure how well heartbeat > would be able to further deal with this state of resources. > Hmm, I like this idea... [I will give it a try] -Philipp -- : Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :