swiftonfile/swiftonfile/swift/common
Prashanth Pai 87de09c9ec Handle non-blocking renames during object PUTs
DiskFile._finalize_put() will now retry renames if it fails with EBUSY
or ESTALE. This is required because for a brief period of time, rename
operation in glusterfs was non-blocking.
Reference: http://review.gluster.org/#/c/13366/

This change also does the following:
* Updates comments to add clarity for operations done and exceptions
  caught in DiskFile.create()
* Handles race between container existance check (memcache) and
  object creation a little more gracefully by logging what really
  happened.

This is port of following change:
http://review.gluster.org/#/c/14118

Change-Id: I1e993f5fed5c75bb77bee0620e1e7104f7f69deb
Signed-off-by: Prashanth Pai <ppai@redhat.com>
2016-05-19 11:45:39 +05:30
..
middleware Remove some dead code 2015-01-19 13:03:51 +05:30
__init__.py changing references of gluster to swiftonfile 2014-07-08 11:04:31 -04:00
constraints.py Allow marker dir objects ending with slash 2015-02-26 12:04:09 +05:30
exceptions.py Handle non-blocking renames during object PUTs 2016-05-19 11:45:39 +05:30
fs_utils.py Remove keyword arguments from os.open call, instead add check for mode bits 2015-10-14 08:57:36 +05:30
utils.py Remove redundant syscalls 2015-11-20 11:12:30 +05:30