Hide Forgot
REVIEW: https://review.gluster.org/20021 (glusterd: glusterd is releasing the locks before timeout) posted (#1) for review on master by Sanju Rakonde
*** Bug 1568436 has been marked as a duplicate of this bug. ***
REVIEW: https://review.gluster.org/19890 (glusterd: glusterd is releasing the locks before timeout) posted (#6) for review on master by Sanju Rakonde
COMMIT: https://review.gluster.org/19890 committed in master by "Atin Mukherjee" <amukherj> with a commit message- glusterd: glusterd is releasing the locks before timeout Problem: We introduced lock timer in mgmt v3, which will realease the lock after 3 minutes from command execution. Some commands related to heal/profile will take more time to execute. For these comands timeout is set to 10 minutes. As the lock timer is set to 3 minutes glusterd is releasing the lock after 3 minutes. That means locks are released before the command is completed its execution. Solution: Pass a timeout parameter from cli to glusterd, when there is a change in default timeout value(i.e, default timeout value can be changed through command line or for the commands related to profile/heal we will change the default timeout value to 10 minutes.) glusterd will set the lock timer timeout according to the timeout value passed. Change-Id: I7b7a9a4f95ed44aca39ef9d9907f546bca99c69d fixes: bz#1577731 Signed-off-by: Sanju Rakonde <srakonde>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report. glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/