From bddb3a014af22133d958da96ad32a02f8ff66805 Mon Sep 17 00:00:00 2001 From: Pranith Kumar K Date: Mon, 19 Dec 2011 18:35:19 +0530 Subject: protocol/server: Do connection cleanup if reply fails We observed that after the first connection cleanup happens on DISCONNECT the lock calls in transit are granted or added in blocked locks queue. These locks were never cleaned up after that because no unlock would come up on that connection. This would leave references on that transport so it would never be destroyed. Now, the connection cleanup happens whenever the reply submission fails. Also cleaned up the old code which is not used any more. Change-Id: Ie4fe6f388ed18d9c907cf8ae06b0b7fd0601a660 BUG: 765430 Signed-off-by: Pranith Kumar K Reviewed-on: http://review.gluster.com/809 Tested-by: Gluster Build System Reviewed-by: Jeff Darcy Reviewed-by: Vijay Bellur --- xlators/protocol/server/src/server.h | 2 -- 1 file changed, 2 deletions(-) (limited to 'xlators/protocol/server/src/server.h') diff --git a/xlators/protocol/server/src/server.h b/xlators/protocol/server/src/server.h index 17de0e8d..c8fd5f27 100644 --- a/xlators/protocol/server/src/server.h +++ b/xlators/protocol/server/src/server.h @@ -57,9 +57,7 @@ struct _server_connection { struct list_head list; char *id; int ref; - int active_transports; pthread_mutex_t lock; - char disconnected; fdtable_t *fdtable; struct _lock_table *ltable; xlator_t *bound_xl; -- cgit