![]() |
lvs-users
|
| To: | lvs-users@xxxxxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | failed node criteria (heartbeat) |
| From: | Karl <karl.mueller@xxxxxxxxxxxxxx> |
| Date: | Mon, 23 Oct 2000 09:48:59 -0500 |
I'm using LVS-NAT, and I'm wondering if there is a 'wrapper' for heartbeat that would detect component failures on the active node (i.e. losing network connectivity on one interface) and fail-over to the secondary for something less then a total failure of the primary. Essentially, I'm looking for an 'environment sensor' of some sort w/ enough logic to keep the workload on whichever LVS node is 'healthiest'. thanks -karl |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | More on scheduling..., Benjamin Lee |
|---|---|
| Next by Date: | Bug: Persistence doesn't associate TCP-->UDP connections to same server, Michael E Brown |
| Previous by Thread: | More on scheduling..., Benjamin Lee |
| Next by Thread: | Bug: Persistence doesn't associate TCP-->UDP connections to same server, Michael E Brown |
| Indexes: | [Date] [Thread] [Top] [All Lists] |