Before you enable the OSS-HDFS service, you need to understand the relationships between the OSS-HDFS service and features of Object Storage Service (OSS). This way, you can properly use the OSS-HDFS service and prevent data loss.
After OSS-HDFS is enabled for a bucket, data that is written by using OSS-HDFS is stored in the .dlsdata/
directory of OSS-HDFS. To ensure the availability of the OSS-HDFS service or prevent data loss, do not perform write operations on the .dlsdata/
directory or on objects in the directory by using methods that are not supported by the OSS-HDFS service. For example, do not perform the following write operations: rename the directory, delete the directory, and delete objects in the directory.
The following table describes risks or considerations when you use OSS features that may involve writes to the .dlsdata/
directory.
Feature | Risk | Description | References |
Retention policy | Data deletion failure | We recommend that you do not enable the OSS-HDFS service and configure retention policies for a bucket at the same time. Assume that OSS-HDFS is enabled for a bucket for which a retention policy is configured. When you use methods supported by OSS-HDFS to delete an object from the | |
Lifecycle rule | Data loss | To configure or modify a lifecycle rule to match all objects in a bucket for which OSS-HDFS is enabled, use the NOT element to exclude the objects that are stored in the ![]() If you want to manage the lifecycle of data stored in OSS-HDFS, use the automatic storage tiering feature of OSS-HDFS. | |
Versioning | Automatic data deletion failures and service exceptions | Do not enable OSS-HDFS and versioning for a bucket. If OSS-HDFS and versioning are enabled for a bucket, OSS-HDFS may not work as expected. To ensure the stability of OSS-HDFS, you need to suspend versioning at the earliest opportunity and configure lifecycle rules to remove delete markers. | |
Delete directories | Data loss | To maintain OSS-HDFS stability and prevent data loss, do not delete the | |
Delete an object | Data loss | To maintain OSS-HDFS stability and prevent data loss, do not delete objects from the | |
Rename directories | Data loss | To maintain OSS-HDFS stability and prevent data loss, do not rename the | |
Rename objects | Data loss | To maintain OSS-HDFS stability and prevent data loss, do not rename objects in the | |
Upload objects | Data loss | To maintain OSS-HDFS stability and prevent data loss, do not upload objects to the | |
Change the storage classes of objects | Delayed data availability and billing changes | We recommend that you do not change the storage classes of objects in the If you change the storage class of an object in the When you change the storage class of an object to IA, Archive, Cold Archive, or Deep Cold Archive, take note of consequential factors such as the minimum billable size (64 KB), minimum storage duration, and data retrieval fees. | |
Bucket Policy | Data access failures, automatic data deletion failures, and unexpected billing | To maintain access to the | |
RAM | Data access failures, automatic data deletion failures, and unexpected billing | When you enable OSS-HDFS for a bucket, the | |
Bucket inventory | Data contamination | To maintain OSS-HDFS availability and prevent data contamination, do not set Inventory Path to | |
Logging | Data contamination | To maintain OSS-HDFS availability and prevent data contamination, do not set Log Prefix to | |
ZIP package extraction | Data contamination and data loss | To maintain OSS-HDFS availability and prevent data contamination, do not set Destination Directory to |