Description of configuration options for [app-object-server] in object-server.conf
Configuration option = Default value Description
= Content-Disposition, Content-Encoding, X-Delete-At, X-Object-Manifest, X-Static-Large-Object Comma-separated list of headers that can be set in metadata of an object
= . Prefix to use when automatically creating accounts
= false Allow non-public objects to stay in kernel's buffer cache
= 5242880 Largest object size to keep in buffer cache
= 86400 Maximum time allowed to upload an object
= 512 On PUT requests, sync file every n MB
= 4 Set to restrict the number of concurrent incoming REPLICATION requests; set to 0 for unlimited
= 1.0 If the value of failures / successes of REPLICATION subrequests exceeds this ratio, the overall REPLICATION request will be aborted
= 100 The number of subrequest failures before the replication_failure_ratio is checked
= 15 Number of seconds to wait for an existing replication device lock before giving up.
= True Restricts incoming REPLICATION requests to one per device, replication_currency above allowing. This can help control I/O to each device, but you may wish to set this to False to allow multiple REPLICATION requests (up to the above replication_concurrency setting) per device.
= false If defined, tells server how to handle replication verbs in requests. When set to True (or 1), only replication verbs will be accepted. When set to False, replication verbs will be rejected. When undefined, server will accept any verb in the request.
= /dev/log Location where syslog sends the logs to
= LOG_LOCAL0 Syslog log facility
= INFO Log level
= object-server Label to use when logging
= true Whether or not to log requests
= 0 If > 0, Minimum time in seconds for a PUT or DELETE request to complete
= no No help text available for this option.
= 0 Size of the per-disk thread pool used for performing disk I/O. The default of 0 means to not use a per-disk thread pool. It is recommended to keep this value small, as large values can result in high read latencies due to large queue depths. A good starting point is 4 threads per disk.
= egg:swift#object Entry point of paste.deploy in the server