Ensure fast-POST operations are used on objects
The defacto swift implementation has a feature called "fast-POSTs", which is an optimization that allows POST operations on files to be performed by updating metadata on additional .meta files. The default is to treat all POST opreations as a COPY operation. Since this gluster-swift code stores all metadata directly on the original object file, there is no need to use an inefficient operation such as COPY. BUG XXXXXX: (https://bugzilla.redhat.com/show_bug.cgi?id=XXXXXX) Change-Id: I39f0a682d5344c3f84c5baa8e292227051c061b8 Signed-off-by: Peter Portante <peter.portante@redhat.com> Reviewed-on: http://review.gluster.org/5673 Reviewed-by: Luis Pabon <lpabon@redhat.com> Tested-by: Luis Pabon <lpabon@redhat.com>
This commit is contained in:
parent
01444e6b6d
commit
2542fb2398
@ -16,6 +16,11 @@ log_level = WARN
|
||||
# or delete an account. So leave this off.
|
||||
allow_account_management = false
|
||||
account_autocreate = true
|
||||
# Ensure the proxy server uses fast-POSTs since we don't need to make a copy
|
||||
# of the entire object given that all metadata is stored in the object
|
||||
# extended attributes (no .meta file used after creation) and no container
|
||||
# sync feature to present.
|
||||
object_post_as_copy = false
|
||||
# Only need to recheck the account exists once a day
|
||||
recheck_account_existence = 86400
|
||||
# May want to consider bumping this up if containers are created and destroyed
|
||||
|
Loading…
Reference in New Issue
Block a user