Thanks Nick:
Here's the config that is the issue right now:
#SERVER1.vip.intranet.mydomain.com
virtual=172.28.191.194:8080
protocol=tcp
scheduler=lc
checktype=connect
checkport=8080
#negotiatetimeout=10
real=172.28.191.170:8080 masq
real=172.28.191.171:8080 masq
#service=ldap
protocol=tcp
checktimeout=10
checkinterval=10
#SERVER2.vip.intranet.mydomain.com
virtual=172.28.191.155:8080
protocol=tcp
scheduler=lc
checktype=connect
checkport=8080
#negotiatetimeout=10
real=172.28.191.139:8080 masq
real=172.28.191.140:8080 masq
protocol=tcp
checktimeout=10
checkinterval=10
So traffic comes in to 155 on Blade A or B depending on which LVS server
s primary, gets "sprayed" to 139/140 on Blades A,B
From 139/140 on Blade A or B it goes to 194 on Blade A and gets
"sprayed" to 170/171 on Blades A,B
(FWIW, I didn't design this mess, in fact I argued vehemently against it
and lost so it is what it is.)
Summary:
Request ---- > 155 LVS (Blade A or B)
----> 139/140 (Blade A or B)
---- > 194 LVS (Blade A or B)
----- > 170 Blade A /171 Blade B
The problem arises when traffic is routed from 194 on Blade A to 170 on
Blade A. It hangs. If it goes to 171 on Blade B, it works.
On 11-11-09 11:19 AM, Nick Khamis wrote:
> Maybe post the ldirecotrd related configs?
>
> Nick.
>
> On Wed, Nov 9, 2011 at 10:15 AM, mike<[email protected]> wrote:
>> Got a bit of an odd issue and I'm hoping someone can help me figure this
>> out.
>>
>> The set up is not ideal but here's the basic flow:
>>
>> Request goes to VIP1 on LVS on Blade A. It then routes it to one of 2
>> load balanced pairs on Blade A or B (works perfectly). That request then
>> goes to one of 2 load balanced JBOSS instances which also reside on
>> Blade A or B. So A--->AorB --->AorB. Weird I know, but the customer
>> wanted it this way.
>>
>> So what I've found is that when a request is made from a Blade to one of
>> the JBOSS instances on the same Blade, it hangs. If the request is made
>> to the JBOSS instance on the other Blade it goes through ok.
>>
>> This can be tested with a simple wget. If I sit on Blade A and issue a
>> wget to one of the backend servers on the same blade, it hangs. If I
>> issue it to one of the backend servers not on the same blade, it goes
>> through. I can't help but think there is something I have to set on the
>> LVS side or even on the backend servers but I'm not sure what.
>>
>> Any ideas?
>> _______________________________________________
>> Linux-HA mailing list
>> [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
