[Linux-HA] Are there any Linux alternatives to drbd and heartbeat?
sergeyfd at gmail.com
Fri Dec 10 14:03:27 MST 2010
On Fri, Dec 10, 2010 at 1:55 PM, Les Mikesell <lesmikesell at gmail.com> wrote:
> On 12/10/2010 2:29 PM, Serge Dubrouski wrote:
>>>>> What I
>>>>> wanted was advice on the best platform that had a packaged, re-usable
>>>>> setup available that was likely to be maintained in updates for a long
>>>> There's a bit of problem with your requirement: you forgot "supported".
>>>> As in try getting any support here for version of heartbeat that ships
>>>> with RHEL 5 (or Suse 10, as I understand).
>>> I'm not looking for support for my local environment. I'm looking for a
>>> version that is reusable and works without local hacks. Or whatever
>>> might be expected to work for a long time into the future if set up now.
>>> But I suppose not changing interfaces wildly would be part of that
>>> requirement so a packager can maintain it.
>> You still didn't tell what you are building. I have a cluster of 2
>> nodes running 2 instances of Apache for 3 years already. OS CentOS
>> 5.5, Pacemaker + Heartbeat. Upgraded it couple of times without any
>> issues. Is it long enough? I also support a couple of other clusters
>> on CentOS 5.5.
> Right now, all I have are a few instances of heartbeat floating a
> fail-over IP address between pairs of boxes that don't really need any
> state maintained (basically client-facing proxies) because that's all
> I've trusted the old versions to handle. Everything else is behind load
> balancers with data replication handled some other way. I'm sure I'd
> find a lot more places to use paired fail-over systems if they were
> simple to set up and included data replication. So at this point it is
> more about building a test platform than making any specific application
> work. But in the back of my head, I'm kind of wishing our developers
> would adopt riak or a similar redundant/scalable data store and do away
> with most of the need for specifically paired systems.
That's exactly what I've been running on my Apache cluster: 2
instances of Apache (one per server with fail over ability) plus
virtual IP for each instance. Each Apache has several Proxies with
mod_load_balancer. You can user CentOS 5.5 for that any any recent
package of Pacemaker/Corosync. Since you don't really have any shared
data between cluster nodes you event don't have to bother about
STONITH devices. Apache config files once created usually don't get
changed but even if they do you can sync them manually. A whole
project can be built in 10 - 15 minutes (doesn't include Apache
configuration). After that you can update Pacemaker once a year or so,
or can even let it run forever.
> Les Mikesell
> lesmikesell at gmail.com
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> See also: http://linux-ha.org/ReportingProblems
More information about the Linux-HA