|author||Avra Sengupta <email@example.com>||2013-09-15 17:55:31 +0530|
|committer||Anand Avati <firstname.lastname@example.org>||2013-09-20 11:48:48 -0700|
glusterd: Adding transaction checks for cluster unlock.
While a gluster command holding lock is in execution, any other gluster command which tries to run will fail to acquire the lock. As a result command#2 will follow the cleanup code flow, which also includes unlocking the held locks. As both the commands are run from the same node, command#2 will end up releasing the locks held by command#1 even before command#1 reaches completion. Now we call the unlock routine in the code path, of the cluster has been locked during the same transaction. Signed-off-by: Avra Sengupta <email@example.com> Change-Id: I7b7aa4d4c7e565e982b75b8ed1e550fca528c834 BUG: 1008172 Signed-off-by: Avra Sengupta <firstname.lastname@example.org> Reviewed-on: http://review.gluster.org/5937 Tested-by: Gluster Build System <email@example.com> Reviewed-by: Krishnan Parthasarathi <firstname.lastname@example.org> Reviewed-by: Anand Avati <email@example.com>
Diffstat (limited to 'extras/systemd/glusterd.service.in')
0 files changed, 0 insertions, 0 deletions