Networking Forums

Networking Forums > Computer Networking > Linux Networking > [Click the star to watch this topic] how much time i have if i want to migrate a server with clients connected wo clients noticing it

Reply
Thread Tools Display Modes

[Click the star to watch this topic] how much time i have if i want to migrate a server with clients connected wo clients noticing it

 
 
will_u_tellmemore
Guest
Posts: n/a

 
      12-28-2006, 01:21 PM
What i wan to know how much time i have on different systems , if i
decide to migrate a server which has client connected to it and they
should not know about this. I think the answer is dependent upon

1: Platform (linux , BSD, Solaris, Windows)
2: Particular implementation (say linux kernel 2.6 TCP etc)
3: system wide settings related to TCP
4: The state connected client is .

Now please correct me if i am wrong in any of these statements.

1: I believe the TCP as a protocol just suggests few things but doesn't
enforce any specific value on implementation. Different system uses
and have used different values for this .So may i know what are the
values on these platforms. If i reestablish those connections ( by some
way. How ?? keeping this part aside of this discussion as it takes it
away from main question.

2: Things may be changed in implementations on single platform from
time to time . Has this really happened with TCP implementations and
mainly time out values ??

3: At least on linux , we can change these value using proc interface
and it will affect lot of important TCP parameters like
tcp_keepalive_time,tcp_retries1, tcp_retries2
,tcp_syn_retries,tcp_synack_retries . I understand that changes in
these values will change answer my question but isn't it the case ,
that most of the systems will use , default values ??

4: Also , TCP timeout value seem to be different in different TCP
states. In active connect , syn timeout , fin timeout, normal data
transfer timeout are different.

Considering all of these issues , still how much time can we think of
we have in our hand , we have to migrate these connections
transparently.(please assume i will do it some way)

on linux tcp_syn_retries shows default timeout value 180 sec = 3
minutes
same for tcp_synack_retries = 3 minutes
for tcp_fin_timeout = 60 sec 1 minute.
for normal data packet = RTO = some complex measurements ?? But what
is minimum value here ??

I guess for tcp_fin_timeout being so small, i may discard it . Anyway
it is not going to bother about state after getting timeout.
So minimum of timeout value for data transfer and default for
syn/synack timeout i.e. 3 minutes , can i consider this (min val ) as
the time that i have in hand before client TCP notices anything
happening at server side ??

What is minimum timeout value that TCP can have with all default
settings in linux 2.6 and 2.4 kernel ,
after which TCP can start thinking something is wrong at other end ??
And how this is calculated in linux.

Thanks ,
Rohit

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
GPO for time clients richk Windows Networking 1 03-13-2007 06:02 AM
GPO and time clients richk Windows Networking 0 03-12-2007 05:58 PM
Domain clients use another client as time server The Kirschi Windows Networking 1 05-16-2006 11:43 AM
Time Service Not Syncing NT Server and XP Clients Hank Allan Windows Networking 0 12-09-2005 05:59 PM
dns update from dhcp server ok for windows clients, not ok for linux (dhclient) clients Tom Van Overbeke Linux Networking 3 08-07-2003 03:24 PM



1 2 3 4 5 6 7 8 9 10 11