A namespace can be optimized for all namespace access protocols or for cloud protocols only. Optimization for all protocols is required if clients will be using the WebDAV, CIFS, NFS, or SMTP protocol to access the namespace.
Optimization only for cloud protocols increases the ingest rate for the namespace but also configures the namespace to ingest objects exclusively through the cloud protocols (REST and the S3 compatible API). This setting is recommended if clients will be using only cloud protocols to access the namespace.
Only cloud-optimized namespaces can allow erasure coding. Also, only cloud-optimized namespaces support multipart uploads with the S3 compatible API.
You can change the protocol optimization setting for a namespace from optimized only for cloud protocols to optimized for all protocols only if all of these are true:
- The namespace does not contain any objects.
- The namespace does not allow erasure coding.
- The namespace is not configured for unbalanced directories.
- The namespace is not configured to use S3 Object Lock.
You can change the protocol optimization setting from optimized for all protocols to optimized only for cloud protocols only if the namespace doesn't have any noncloud protocols enabled.
A system administrator can change a tenant from not being able to choose whether namespaces allow erasure coding to being able to do this. After this change occurs, when you enable cloud optimization for a preexisting namespace that was not cloud optimized and that did not allow erasure coding, the namespace is automatically configured to allow erasure coding.
- To view the protocol optimization setting for a namespace, you need the monitor or administrator role.
- To change the protocol optimization setting for a namespace, you need the administrator role.