Adding DRBD to cluster management
DRBD is actually one of the most difficult resources to manage with Pacemaker. Unlike a regular service that is started or stopped depending on where it is active, DRBD is always active. The only thing that changes between two nodes running DRBD is the Primary or Secondary state ascribed to each.
Due to this complication, DRBD is not one resource, but two:
- A DRBD resource to manage starting and stopping DRBD
- A master/slave resource to control which node acts as the
Primary
In this recipe, we'll allocate both of these resources so that Pacemaker can manage DRBD properly.
Getting ready
As we're continuing to configure Pacemaker, make sure you've followed all previous recipes.
How to do it...
In the previous chapter, we ...
Get PostgreSQL 9 High Availability Cookbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
