Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux Virtual Server: Users

syncd

 

 

Linux Virtual Server users RSS feed   Index | Next | Previous | View Threaded


MKrauss at hitchhiker

Feb 23, 2006, 1:19 PM

Post #1 of 4 (519 views)
Permalink
syncd

Hi,
i'm currently testing the "Server State Sync Demon", mcast is going well and
established states are tranfered fine to the backup device, now i am
looking
for the persistent stats which are stated as NONE, those doesn't seem to
get
transfered to the backup device, i guess thats by design or is there a
way to
change this ?

thx


_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://www.in-addr.de/mailman/listinfo/lvs-users


ratz at drugphish

Feb 25, 2006, 6:51 AM

Post #2 of 4 (501 views)
Permalink
Re: syncd [In reply to]

Matthias Krauss wrote:
> Hi,
> i'm currently testing the "Server State Sync Demon", mcast is going well
> and
> established states are tranfered fine to the backup device, now i am
> looking
> for the persistent stats which are stated as NONE, those doesn't seem to
> get
> transfered to the backup device, i guess thats by design or is there a
> way to
> change this ?

According to the code they should be "transfered" as well, reading
../ipvs/ip_vs_sync.c:ip_vs_process_message():

301 for (i=0; i<m->nr_conns; i++) {
302 unsigned flags;
303
304 s = (struct ip_vs_sync_conn *)p;
305 flags = ntohs(s->flags);
306 if (!(flags & IP_VS_CONN_F_TEMPLATE))
307 cp = ip_vs_conn_in_get(s->protocol,
308 s->caddr, s->cport,
309 s->vaddr, s->vport);
310 else
311 cp = ip_vs_ct_in_get(s->protocol,
312 s->caddr, s->cport,
313 s->vaddr, s->vport);
314 if (!cp) {
315 cp = ip_vs_conn_new(s->protocol,
316 s->caddr, s->cport,
317 s->vaddr, s->vport,
318 s->daddr, s->dport,
319 flags, NULL);
320 if (!cp) {
321 IP_VS_ERR("ip_vs_conn_new failed\n");
322 return;
323 }
324 cp->state = ntohs(s->state);

template connection entries (used for persistent connections) are
created if they are not available already on the backup node.

Maybe I'm misreading it. I haven't used the synchronisation concept in
years. Do you have any strange entries in your kernlog on either side?

Cheers,
Roberto Nibali, ratz
--
echo
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://www.in-addr.de/mailman/listinfo/lvs-users


MKrauss at hitchhiker

Feb 25, 2006, 11:59 AM

Post #3 of 4 (499 views)
Permalink
Re: syncd [In reply to]

>>template connection entries (used for persistent connections) are
created if they are not available already on the backup node.
>>Maybe I'm misreading it. I haven't used the synchronisation concept
in years. Do you have any strange entries in your kernlog on either side?

I was only testing, but from what i saw is that things are going well
except the persistent stat, on the master node i've set persitence of
60 Mon. and this was taken over with with the "NONE" state of 3.Min
(looks like default) . From the setup i noticed that syncd will only work
if i have the same node and real server config on the backup device with
th VIP flagged down. Its not a big thing just want to tell ......

greets
Matt.


_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://www.in-addr.de/mailman/listinfo/lvs-users


ratz at drugphish

Feb 26, 2006, 2:59 AM

Post #4 of 4 (506 views)
Permalink
Re: syncd [In reply to]

> >>template connection entries (used for persistent connections) are
> created if they are not available already on the backup node.
> >>Maybe I'm misreading it. I haven't used the synchronisation concept
> in years. Do you have any strange entries in your kernlog on either side?
>
> I was only testing, but from what i saw is that things are going well
> except the persistent stat, on the master node i've set persitence of
> 60 Mon. and this was taken over with with the "NONE" state of 3.Min
> (looks like default) .

Indeed, from what I can gather, all connection entries created by sync
messages will have the IP_VS_SYNC_CONN_TIMEOUT set, which is 3*60*HZ.
One of the issue to consider is a possible DoS or replay attack, so
maybe we chose this value because of that. I honestly do not remember.

What would your expectation be regarding the synchronisation behaviour?
We rarely got feedback from people using it, so the more input we get,
the better can this behaviour be adapted.

> From the setup i noticed that syncd will only work
> if i have the same node and real server config on the backup device with
> th VIP flagged down. Its not a big thing just want to tell ......

What do you mean by "VIP flagged down"? Of course you need to have the
same config on each server, anything else would result in
promiscuousness regarding the receiving kernel side.

Best regards,
Roberto Nibali, ratz
--
echo
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://www.in-addr.de/mailman/listinfo/lvs-users

Linux Virtual Server users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.