[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: little problem with <close-session>
On Thu, Sep 02, 2004 at 11:46:40AM +0200, Eliot Lear wrote:
> I'd like to put a new draft out, but I can't right now because I'm
> blocked on <close-session>. As it stands right now, we are blocked
> because Margaret is concerned about CLOSE_WAIT state consuming resources
> on the manager. This concern arises from the case where one will want
> to make a change across a large number of devices in a short period of
> time. The concern is mitigated by <close-session> because this forces
> the CLOSE_WAIT state to the agent.
>
> On the other hand, <close-session> cannot currently be used by the agent
> because the agent doesn't send commands. So, what's a poor agent to do
> when it wants to gracefully shutdown the connection?
[...]
> Comments?
I am still not sure how serious the problem is we are trying to cure.
How many TCP connections do you have to close per second in order to
run into problems on today's operating systems? Do operators have any
insights to share whether this is a problem with existing CLI scripts?
How many TCP connections do they close per second these days?
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>