LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

LVS-DR director connecting to itself...

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: LVS-DR director connecting to itself...
From: Helgi Hrafn Gunnarsson <helgi.gunnarsson@xxxxxxxxxxx>
Date: Fri, 3 Nov 2006 14:30:35 +0200
Hello, all.

I have a problem that I'm having a terrible time addressing.

I have the following setup.

V1: MySQL server
V2: MySQL server
V3: Web server
V4: Web server

The MySQL servers are replicated, meaning they contain the same information. 
I've successfully set up an LVS on V3 that connects to V1 and V2 according to 
which one of them is up. The VIP on V3 can be reached from V4 and from that 
point of view, everything is great. The problem is that it cannot be reached 
from V3 itself, which is what I desperately need.

This is a major problem because V4 is going to be the backup LVS server when V3 
goes down.

I've read a bunch of mailing lists and docs and every solution I've found so 
far is only for too old kernels, 2.4 or even 2.2, when I'm using 2.6. 
Furthermore, a hack in ip_vs_core seems to be required to make this possible 
with LVD-DR, which I want to avoid is possible.

Question 1: Is it possible to make the V3 capable of connecting to the VIP when 
the VIP is on V3 itself without a kernel hack? If so, how?

Question 2: If it's impossible with a kernel hack, is anyone aware of a kernel 
hack that should work for kernel 2.6.x?

Question 3: Are there any other solutions than LVS which might help me do what 
I'm trying to do, that anyone is aware of?

Any and all help with this is greatly appreciated. Thanks in advance.

Kind regards,
Helgi Hrafn Gunnarsson
helgi.gunnarsson@xxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>