Krille
Gesendet: Samstag, 25. Januar 2014 01:46
An: linux-ha@lists.linux-ha.org
Betreff: Re: [Linux-HA] heartbeat failover
On Thu, 23 Jan 2014 16:45:04 + bjoern.bec...@easycash.de wrote:
Uhhh..I got the same configuration as the example config you sent me
now. But I cause high cpu load
side?
Best regards
Björn
-Ursprüngliche Nachricht-
Von: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Becker, Björn
Gesendet: Donnerstag, 23. Januar 2014 17:45
An: linux-ha@lists.linux-ha.org
Betreff: Re: [Linux-HA] heartbeat failover
without multicast?
Best regards
Björn
-Ursprüngliche Nachricht-
Von: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Digimer
Gesendet: Mittwoch, 22. Januar 2014 20:36
An: General Linux-HA mailing list
Betreff: Re: [Linux-HA] heartbeat failover
2014 20:36 An: General Linux-HA
mailing list Betreff: Re: [Linux-HA] heartbeat failover
On 22/01/14 10:44 AM, bjoern.bec...@easycash.de wrote:
Hello,
I got a drbd+nfs+heartbeat setup and in general it's working. But
it takes to long to failover and I try to tune this.
When node 1
...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Lukas Grossar
Gesendet: Donnerstag, 23. Januar 2014 16:54
An: linux-ha@lists.linux-ha.org
Betreff: Re: [Linux-HA] heartbeat failover
Hi Björn
Here ist an example how you can setup corosync to use Unicast UDP:
https
-Ursprüngliche Nachricht-
Von: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Becker, Björn
Gesendet: Donnerstag, 23. Januar 2014 17:28
An: linux-ha@lists.linux-ha.org
Betreff: Re: [Linux-HA] heartbeat failover
Hi Lukas,
thank you. Well
Hello,
I got a drbd+nfs+heartbeat setup and in general it's working. But it takes to
long to failover and I try to tune this.
When node 1 is active and I shutdown node 2, then node 1 try to activate the
cluster.
The problem is, node 1 already got the primary role and when re-activating it
On 22/01/14 10:44 AM, bjoern.bec...@easycash.de wrote:
Hello,
I got a drbd+nfs+heartbeat setup and in general it's working. But it takes to
long to failover and I try to tune this.
When node 1 is active and I shutdown node 2, then node 1 try to activate the
cluster.
The problem is, node 1
On 23 Apr 2012, at 02:23, Net Warrior wrote:
auto_failback on
No. As far as I'm aware this is to control what happens when your initial node
recovers. If you have 2 nodes, a and b, and a is active, but then fails, b will
take over, but when a is fixed and recovers, heartbeat will 'fail back'
Hi, Net Warrior!
What version of HA/Pacemaker do you use?
Did you already RTFM - e.g.
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained
- or:
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch
HTH
Nikita Michalko
Am Montag, 23.
Hi Nikita
This is the version
heartbeat-3.0.0-0.7
My aim is to, if node1 is powered off or losts it's ethernet
connection,. node2 wont make the failover automatically, I want to
make it manually, but could not find how to accomplish that.
Thanks for your time and support
Best regards
Why even use heartbeat then - Just manually ifconfig the interface.
On 4/23/12 7:39 AM, Net Warrior wrote:
Hi Nikita
This is the version
heartbeat-3.0.0-0.7
My aim is to, if node1 is powered off or losts it's ethernet
connection,. node2 wont make the failover automatically, I want to
True, but even on the most expensive software likve Veritas Cluster or
Red Hat Cluster I can configure how I want to failover the resources (
auto or manual ), that's why my curiosity to acomplish the same in
here.
Thanks for your time
Best Regards
2012/4/23, David Coulson
On 04/23/2012 01:47 PM, Net Warrior wrote:
True, but even on the most expensive software likve Veritas Cluster or
Red Hat Cluster I can configure how I want to failover the resources (
auto or manual ), that's why my curiosity to acomplish the same in
here.
with the help of the meat-ware
Hi There
I configured heartbeat to failover an IP address , if I for example
shutdown one node, the other takes it's ip address, so far so good, now
my doubt is if there is a way to configure it not to make the failover
automatically and have someone run the failover manually, can you provide
Hello List.
I came in this morning and found that one of my clusters had a failure
over the weekend. This cluster is not yet production, but is slated to
become a production cluster soon, so I am hoping I can get some
help/advice to keep this type of failure from occurring again in the
future.
exactly. I personally use 3-ware raid controllers with a raid-1 (mirror)
configured. I monitor these controllers with nagios and switch disks
within 2 days, if one dies. But you could also use a linux software raid
and _sata_ not _pata_ disks to obtain the above. Another way to detect
Hello Coach-X (what a strange name),
This has happened several times. Nothing shows up in either log file,
and a hard reboot brings the master back online. Is this caused by
the serial link still being active? Is there a way to have this type
of issue cause the slave to become active?
We have a simple two node cluster that share an ip and one resource
(exim). Connection is by serial link. The system works fine if we
power down the master or take it offline, but if the master experiences
a drive error, making the resource unavailable the failover never happens.
This has
Hello.
Testing Heartbeat v2.1.2 I'm trying to configure failover.
I'm looking for initiate a failover on a failed monitored resource.
I have been doing that unsing the default-failure-stickiness, but when
the two node scores (computed by heartbeat) are negative the resource is
stopped.
Is
On Jan 24, 2008, at 9:47 AM, Sylvain MALAVIEILLE wrote:
Hello.
Testing Heartbeat v2.1.2 I'm trying to configure failover.
I'm looking for initiate a failover on a failed monitored resource.
I have been doing that unsing the default-failure-stickiness, but
when the two node scores (computed
Hi there !
As Sylvain, I don't understand how HeartBeat (and in particular
PaceMaker) ensure high availability of a service (application resource)
if it is not possible to configure automatic failover in case of
resource failure needed by the service ?
How people configure HB to ensure the
On Jan 24, 2008, at 10:20 AM, GAUTIER Hervé wrote:
Hi there !
As Sylvain, I don't understand how HeartBeat (and in particular
PaceMaker) ensure high availability of a service (application
resource) if it is not possible to configure automatic failover in
case of resource failure needed
Andrew Beekhof a écrit :
On Jan 24, 2008, at 10:20 AM, GAUTIER Hervé wrote:
Hi there !
As Sylvain, I don't understand how HeartBeat (and in particular
PaceMaker) ensure high availability of a service (application
resource) if it is not possible to configure automatic failover in
case
On Jan 24, 2008, at 11:59 AM, GAUTIER Hervé wrote:
Andrew Beekhof a écrit :
On Jan 24, 2008, at 10:20 AM, GAUTIER Hervé wrote:
Hi there !
As Sylvain, I don't understand how HeartBeat (and in particular
PaceMaker) ensure high availability of a service (application
resource) if it is
Andrew Beekhof a écrit :
What it wont do is move to a node where the resource has _already_
failed.
That's my point.
The rationale is that if something happened on nodeX enough times to
cause the resource migrate away, then there is unlikely to be any
point trying nodeX again until the
Hi,
i have a simple fail-over heartbeat/drbd cluster set up. In each
server there are two network cards. One for internet access (WAN) and
one for internal communication and synchronization (LAN). If one node
looses internet connection (WAN) the other takes over all resources
as
27 matches
Mail list logo
