Red Hat Bugzilla – Bug 1005379
Performance test failure because of infinite loop issue when renaming a file
Last modified: 2016-11-08 17:25:15 EST
Description of problem:
From Peter Portante's Fix (http://review.gluster.org/5670) for gluster-swift master (Havana) branch:
Fix infinite loop for temp file renames on ENOENT
For whatever reason, it appears that GlusterFS, or perhaps FUSE can
continuously return ENOENT on a rename system call even when we have
double checked that there is no reason to do so. That is a bug for
that sub system. However, our response to that bug can result in an
infinite loop, which is bad.
This code reduces that to 10 attempts.
In addition, we restructed the open retry loop to match, providing
module constants for the upper bounds of both retry loops.
Peter has been able to see this issue on his multiple node performance tests
for RHS 2.1. The fix needs to be backported to upstream gluster-swift Grizzly
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Fix posted for review: http://review.gluster.org/5848
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
For information on the advisory, and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.