This gives the ms_handle_reset call a chance to clean up (for example, by
breaking a con->priv <-> session reference cycle).
Signed-off-by: Sage Weil <sage@inktank.com>
replaced = true;
if (!existing->policy.lossy) {
+ // queue a reset on the old connection
+ msgr->dispatch_queue.queue_reset(connection_state.get());
+
// drop my Connection, and take a ref to the existing one. do not
// clear existing->connection_state, since read_message and
// write_message both dereference it without pipe_lock.