15 Jul
2005
15 Jul
'05
1:20 p.m.
Hi,
I'm just curious about the way SER performs a shutdown. Is there a
graceful shutdown handling? If so, what exactly is done?
IMHO a nice way would be to stop accepting new transactions (rejecting
them with 301 for example to allow them to be resend to another server)
but still accepting messages corresponding to ongoing transactions like
100/180/200 responses and ACK requests. If there are no more incomplete
transactions, the socket could be closed and the process could shut down.
Comments?
Andy
15 Jul
15 Jul
1:38 p.m.
One could possibly do it with external apps via FIFO.
Initially, you would set a gflag (if gflag_set("1") { redirect; break; }}
and then watch fifo/t_stats till current transactions drop to zero.
Eventually, you shut down the process (possible after some period
of time to deal with stateless e2e ACKs).
-jiri
At 11:20 AM 7/15/2005, Andreas Granig wrote:
Hi,
I'm just curious about the way SER performs a shutdown. Is there a graceful shutdown
handling? If so, what exactly is done?
IMHO a nice way would be to stop accepting new transactions (rejecting them with 301 for
example to allow them to be resend to another server) but still accepting messages
corresponding to ongoing transactions like 100/180/200 responses and ACK requests. If
there are no more incomplete transactions, the socket could be closed and the process
could shut down.
Comments?
Andy
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan http://iptel.org/~jiri/
7060
days inactive
7060
days old
2 comments
2 participants
participants (2)
-
Andreas Granig -
Jiri Kuthan