You need to enter COS and CFS paths for execution logs (
StdErr) and remote storage mappings in BatchCompute, which is slightly different from access to COS buckets or files in HTTP mode.
For BatchCompute paths, only endpoints in the XML API format are supported as shown below:
The obtained COS endpoint is as shown below:
Prefix BatchCompute paths with
cos:// and suffix them with
Add subdirectories to a bucket path as common file directories. The following figure shows the subdirectories created in the bucket.
For directory mounting, the COS paths are as follows:
cos://batchdemo-125178xxxx.cos.ap-guangzhou.myqcloud.com/logs/ cos://batchdemo-125178xxxx.cos.ap-guangzhou.myqcloud.com/input/ cos://batchdemo-125178xxxx.cos.ap-guangzhou.myqcloud.com/output/
COS has regional attributes. Data transfer between the storage server and Cloud Virtual Machine (CVM) is efficient only when your BatchCompute job and COS bucket are in the same region.
In remote storage mappings, you can configure CFS/NAS paths to automatically mount to a local path as shown below:
An example of an obtained CFS path is
10.66.xxx.xxx. Prefix a BatchCompute path with
Suffix the path with
/and ensure that your CFS/NAS and BatchCompute job are on the same network.