|
On Sat, 1 Apr 2000, jake buchholz wrote:
> when I noticed that ipvsadm -L was
> reporting the port as :3309, but tcpdump was calling it .mysql... I grepped
> /etc/services, and discovered what the problem is.
>
> mysql's port is 3306, not 3309! Damn, my discalculate eyes! I switched to
> use that port, and wouldn't ya know... it actually _works_. (slaps
> forehead)
I gave those numbers a cursory glance, assumed you'd got it right and
then forgot about it :-)
Can you check the posible data corruption problem sometime. Like connect
directly from a client box to 2 realservers and write to one mysqld and
check if the other mysqld can see the write (I have no idea what to look
for actually - this is just a test off the top of my head. It would be
nice to simulate the LVS:mysqld setup first to give us some confidence).
There's a test suite taht comes with mysql. I guess you could run that on
an LVS. If there's a potential data corruption problem we'd likely see it
there (unless the mysql client opens a persistant connection).
> Should note that mysql has entries in /etc/services on 3306 for both tcp
> and udp -- not quite sure if traffic is expected via both, or if it'll
> try one if the other isn't available for some reason.
it might be like DNS where requests shorter than 512bytes are sent by udp
and larger ones are sent by tcp (I think).
Joe
--
Joseph Mack mack@xxxxxxxxxxx
|
