Page Comparison

"static"

Zeroconf is not supported.

server1 server2 server3

Space or comma delimited list of IP addresses or host names of the storage cluster nodes.

80

Integer socket port number for SCSP on the storage nodes.

The name of the storage cluster.

indexer1 indexer2 indexer3

Space or comma delimited list of the Elasticsearch metadata index servers used by the storage cluster. Must be from the same ES cluster: do not mix old and new clusters.

Required for the S3 protocol and for Content Metering

9200

The socket port on which the Elasticsearch servers listen.

91

Provide these credentials for the storage cluster to enable Gateway version and component information to be included in the cluster health report that provides proactive support from DataCore. (v6.0)

Required when using [cluster_admin].

0.0.0.0

Set to the IP address of the network interface connected to the storage cluster subnet when using a multi-homed Gateway. The value must be defined as a non-default value when using a multi-homed Gateway server such as one connected to a front-end client network and a back-end storage network.

100

The maximum number of open connections to a specific storage node.

250

The maximum number of open connections to allow. This includes both active and idle connections.

60

The time in seconds allowed to connect to a node.

120

The time in seconds allowed for an active connection to deliver data.

120

The time in seconds an idle socket is allowed to remain in the connection pool.

120

The time in seconds an indexer socket is allowed to remain in the connection pool. This affects the ability to list larger buckets. (v7.1)

30

The time in seconds to wait for client response after a 100 continue reply.

"immediate"

Controls whether synchronous (immediate, using replicate on write) or asynchronous (delayed) data protection is requested when writing to the storage cluster.

Values:

• "immediate" (for replicate on write) - requires storage cluster setting of scsp.replicateOnWrite=true

• "delayed" (disables replicate on write) - requires storage cluster setting of scsp.replicateOnWrite=false 

See Configuring ROW Replicate On Write

true

When enabled, the Gateway rejects any SCSP write (PUT, POST, COPY, APPEND) that includes a deletable=no/false lifepoint. This restriction applies to both named and unnamed (alias and immutable) objects. The request is refused with a 400 error message, "Unable to write undeletable object".

false

The protocol must be explicitly enabled. Values are: "true", "false".

0.0.0.0

The IP address of the network interface to which the listening socket binds. Defaults to all interfaces.

80

Integer socket port number for protocol.

80
443

Optional, one or both. Allows Gateway to be used either behind a proxy or within a Docker environment, taking effect when X-Forwarded-Proto is found on the request. Gateway uses X-Forwarded-Proto to determine which port to use. (v5.4)

true

Improves compatibility with S3 clients and software libraries that expect consistent listings (despite the documented nature of listings to be eventually consistent). Can be disabled to boost write throughput (especially for small objects), if listing consistency is not critical. (v5.2.1)

Exceptions to synchronous indexing:

• Deletes of manifests for canceled multipart uploads are done asynchronously.

• On a delete, when there is not enough space on the local node to write a delete marker for a named object, Swarm writes to another node and indexes asynchronously.

• On a rename, Swarm indexes the new name synchronously, but the old name is deleted asynchronously.

• On a parallel write complete, the init stream is deleted asynchronously.

The Amazon S3 GET Bucket Location request returns the AWS region in which the bucket is located.
By default, Gateway returns an empty value for the location, which S3 clients interpret as us-east-1. If another region is required, there are two options:

• Supply the location in the bucket creation operation using LocationConstraint.

• Set the region option in the Gateway configuration file to the preferred region. This applies to all buckets unless the location is specified during creation.

If you require the behavior prior to Content Gateway 7.10.2 of returning the cluster name, set region to that cluster name.

Set forcedDomain to the name of an existing domain to force Content Gateway to use that domain for S3 requests regardless of the incoming Host or X-Forwarded-Host header. This allows S3 clients to use gateway hostnames or IP addresses as the endpoint instead of requiring the endpoint to be a domain name. The S3 clients must use the "bucket in path" style of access for all requests, not the “bucket in Host” style. This feature is supported since v7.10.7.