id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
502	remove peers from client's table upon DeadReferenceError	warner		"it looks like, once a peer has disconnected, the client doesn't ever remove the {{{RemoteReference}}} from its table. As a result, we keep getting new {{{DeadReferenceErrors}}} forever, which creates a lot of Incidents and log traffic.

There is a related problem, in which a silent partition (one in which you have to wait for TCP to notice the problem) can result in dozens of remote messages being queued (especially if these are the readvs from a deep-stats or deep-check). All of these messages will errback at about the same time (in sequential turns) when the disconnect is finally discovered, and removing the peer from the table won't help this. We'd need some significant changes to the connection model (perhaps a completely non-connection-oriented model), and some layering violations, to allow the higer level to say ""nevermind: I don't need this message delivered anymore"".
"	defect	closed	major	1.3.0	code-network	1.2.0	fixed