GitHub PushEvent at 2014-06-27 08:42:23
Repository: glusterfs
Actor: avati
Payload: {"shas":[["efb5af6c1a66fc6d8bebb1c96e8b39d6fa6f8dcd","3d98f31eab06971051372b88e77259b2119ee764@redhat.com","protocol/client: conn-id should be unique when lk-heal is off\n\n        Backport of http://review.gluster.org/6669\n\nProblem:\nIt was observed that in some cases client disconnects\nand re-connects before server xlator could detect that a\ndisconnect happened. So it still uses previous fdtable and ltable.\nBut it can so happen that in between disconnect and re-connect\nan 'unlock' fop may fail because the fds are marked 'bad' in client\nxlator upon disconnect. Due to this stale locks remain on the brick\nwhich lead to hangs/self-heals not happening etc.\n\nFor the exact bug RCA please look at\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1049932#c0\n\nFix:\nWhen lk-heal is not enabled make sure connection-id is different for\nevery setvolume. This will make sure that a previous connection's\nresources are not re-used in server xlator.\n\nBUG: 1113894\nChange-Id: I5090f832730e4072c4b6b6758e64f757b911bd49\nSigned-off-by: Pranith Kumar K <pkarampu@redhat.com>\nReviewed-on: http://review.gluster.org/8187\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Niels de Vos <ndevos@redhat.com>","Pranith Kumar K",true]],"size":1,"ref":"refs/heads/release-3.5","head":"efb5af6c1a66fc6d8bebb1c96e8b39d6fa6f8dcd"}