diff options
author | Pranith Kumar K <pkarampu@redhat.com> | 2014-01-08 17:01:44 +0530 |
---|---|---|
committer | Niels de Vos <ndevos@redhat.com> | 2014-06-27 01:42:03 -0700 |
commit | efb5af6c1a66fc6d8bebb1c96e8b39d6fa6f8dcd (patch) | |
tree | 866d0052f2980376e04f3adbfd1ac0bd80056ab6 /tests | |
parent | e672e3dd750eeb39ad1cd2eeb0b7b51920928b50 (diff) |
protocol/client: conn-id should be unique when lk-heal is off
Backport of http://review.gluster.org/6669
Problem:
It was observed that in some cases client disconnects
and re-connects before server xlator could detect that a
disconnect happened. So it still uses previous fdtable and ltable.
But it can so happen that in between disconnect and re-connect
an 'unlock' fop may fail because the fds are marked 'bad' in client
xlator upon disconnect. Due to this stale locks remain on the brick
which lead to hangs/self-heals not happening etc.
For the exact bug RCA please look at
https://bugzilla.redhat.com/show_bug.cgi?id=1049932#c0
Fix:
When lk-heal is not enabled make sure connection-id is different for
every setvolume. This will make sure that a previous connection's
resources are not re-used in server xlator.
BUG: 1113894
Change-Id: I5090f832730e4072c4b6b6758e64f757b911bd49
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
Reviewed-on: http://review.gluster.org/8187
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions