- Documentation
File Storage vePFS
FAQs
DataFlow FAQ
DataFlow FAQ
This article addresses common issues with the DataFlow feature in vePFS file storage for your reference.
How do I resolve directory or Bucket conflicts when creating a DataFlow policy or task?
Check whether another active policy or task is configured with the same directory, or if a parent directory contains nested configurations. For example, Task A is already running with the vePFS path set to /a/b/c and the TOS path set to /bucket1/prefix1/. If you then create Task B with the vePFS path set to /a/b/ and the TOS path set to /bucket2/prefix2, the system will detect a path conflict and prevent the creation of Task B.
How can I improve slow preheating or settling speeds?
For vePFS DataFlow performance specifications, refer to DataFlow specification description. DataFlow based on file lists performs better than path-based configurations. If you have hit the performance limit with path-based configurations, you can use the file list method for preheating or settling. For detailed steps, see Creating manual tasks. How can I prevent data overwrites between multiple DataFlow tasks for different products?
File storage vePFS, Elastic File Storage (EFS), and FileNAS currently support DataFlow. To avoid data overwrites between multiple DataFlow tasks from different products, choose different file system paths and object storage paths when creating DataFlow policies for each product.
Why are actions on TOS not synchronized to vePFS?
- The DataFlow automatic prefetch feature currently only supports the following TOS events:
- tos:ObjectCreated:Origin
- tos:ObjectCreated:CompleteUpload
- tos:ObjectReplication:ObjectCreated
- tos:ObjectReplication:ObjectModified
- tos:ObjectRemoved:Delete
- tos:ObjectRemoved:DeleteMarkerCreated
- tos:LifecycleExpiration:Delete
- tos:LifecycleExpiration:DeleteMarkerCreated
Last updated: 2026.05.19 14:09:10