Protocol services

Benefits

Protocol type

CPFS NFS protocol services use the NFSv3 protocol.
Multi-protocol access

CPFS file systems support simultaneous access from CPFS-POSIX and CPFS-NFS clients. Changes made through one client are visible through the other. Both clients enforce the same UGO (User, Group, Other) permissions.
Load balancing

NFS protocol services run as a cluster. The CPFS-NFS client distributes traffic across protocol nodes through load balancing.

Protocol service types

Protocol services come in two types: General-purpose and Cache-accelerated. Cache-accelerated services store hot data in server memory. On a cache hit, bandwidth exceeds the CPFS file system limit and reaches the configured protocol service maximum.

General-purpose: Provides NFS protocol access and directory-level mount targets for General-purpose Edition CPFS file systems. No POSIX client management cluster is required. Free of charge.
Cache-accelerated: Adds server-side LRU memory caching to all General-purpose features. When data is cached, CPFS delivers higher internal bandwidth. Two tiers are available: Cache Type 1 and Cache Type 2, which differ in bandwidth and cache size.

Note
Cache-accelerated is a paid feature in invitational preview. Review pricing in CPFS billing. To ask questions or provide feedback, join DingTalk group 31045006299.

Limits

File system version requirements

Protocol services require CPFS 2.3.0 or later.

Specification limits

Limits	Threshold	Description
Protocol services per file system	1	One per file system.
VPCs for publishing export directories	2	Up to two VPCs per protocol service.
Export directories per protocol service	10	Up to 10 across filesets or directories.
Mounted compute nodes per protocol service	10,000	Up to 10,000 per protocol service.
Concurrently open files	150,000	No more files can open after this limit is reached.

Other limits

Multiple clients can read and write files in a unified namespace. However, when multiple processes concurrently write the same file, write anomalies (overwrites, crossovers, serialization) may occur because NFSv3 does not support Atomic Append.
Network Lock Manager (NLM) is not supported.
NFSv4.x is not supported.

Usage procedure

Create a protocol service to export a fileset or directory from a CPFS file system, install the CPFS-NFS client on a compute node, and mount the file system through an NFS mount target.

Create a protocol service.

Create a protocol service.
Create an export directory.

Create an export directory.
Log on to the ECS instance where you will mount the CPFS file system. For more information about how to connect to an ECS instance, see Connection methods.

Download and install the CPFS-NFS client.

Alibaba Cloud Linux

Download the CPFS-NFS client.

wget https://cpfs-hangzhou-nfs-client.oss-cn-hangzhou.aliyuncs.com/aliyun-alinas-utils-latest.al.noarch.rpm

Install the CPFS-NFS client.

sudo yum install aliyun-alinas-utils-*.rpm

CentOS

Download the CPFS-NFS client.

wget https://cpfs-hangzhou-nfs-client.oss-cn-hangzhou.aliyuncs.com/aliyun-alinas-utils-latest.el.noarch.rpm

Install the CPFS-NFS client.

sudo yum install aliyun-alinas-utils-*.rpm

Ubuntu

Download the CPFS-NFS client.

sudo wget https://cpfs-hangzhou-nfs-client.oss-cn-hangzhou.aliyuncs.com/aliyun-alinas-utils-latest.deb -O /tmp/aliyun-alinas-utils-latest.deb

Install the CPFS-NFS client.

sudo apt-get update
sudo apt-get install /tmp/aliyun-alinas-utils-latest.deb

Debian

Download the CPFS-NFS client.

sudo wget https://cpfs-hangzhou-nfs-client.oss-cn-hangzhou.aliyuncs.com/aliyun-alinas-utils-latest.deb -O /tmp/aliyun-alinas-utils-latest.deb

Install the CPFS-NFS client.

sudo apt-get update
sudo apt-get install /tmp/aliyun-alinas-utils-latest.deb

SUSE

Download the CPFS-NFS client.

wget https://cpfs-hangzhou-nfs-client.oss-cn-hangzhou.aliyuncs.com/aliyun-alinas-utils-latest.lp15.x86_64.rpm

Install the CPFS-NFS client.

sudo zypper --no-gpg-checks install -y aliyun-alinas-utils-*.rpm

Mount the file system.

Mount a file system.

Performance metrics

Performance metrics for General-purpose and Cache-accelerated protocol services:

Protocol service type	Metric	100 MB/s/TiB baseline	200 MB/s/TiB baseline
General-purpose	Throughput	min(100 x Storage capacity (TiB), 20,000) MB/s. Matches the CPFS file system bandwidth.	min(200 x Storage capacity (TiB), 20,000) MB/s. Matches the CPFS file system bandwidth.
	IOPS	Read/Write: min(4,000 x Storage capacity (TiB), 960,000)	Read/Write: min(8,000 x Storage capacity (TiB), 960,000)
	One-way latency	Read latency: 0.8 milliseconds. Write latency: 0.8 milliseconds.	Read latency: 0.6 milliseconds. Write latency: 0.6 milliseconds.
	Maximum throughput of a single client	600 MB/s	600 MB/s
	Maximum IOPS of a single client	Read IOPS: 80,000. Write IOPS: 30,000.	Read IOPS: 80,000. Write IOPS: 30,000.
Cache type	Throughput	The maximum read bandwidth specified during protocol service creation. Maximum: 100 GB/s.	The maximum read bandwidth specified during protocol service creation. Maximum: 100 GB/s.
	IOPS	Read: min(7,500 x Protocol service bandwidth (GB/s), 15,000 x Storage capacity (TiB), 1,900,000) Write: min(4,000 x Storage capacity (TiB), 960,000)	Read: min(7,500 x Protocol service bandwidth (GB/s), 30,000 x Storage capacity (TiB), 1,900,000) Write: min(8,000 x Storage capacity (TiB), 960,000)
	One-way latency	Read latency (cache hit): 0.2 milliseconds. Read latency (cache miss): 0.8 milliseconds. Write latency: 0.8 milliseconds.	Read latency (cache hit): 0.2 milliseconds. Read latency (cache miss): 0.6 milliseconds. Write latency: 0.6 milliseconds.
	Maximum throughput of a single client	1.1 GB/s	1.1 GB/s
	Maximum IOPS of a single client	Read IOPS: 90,000. Write IOPS: 40,000.	Read IOPS: 90,000. Write IOPS: 40,000.