Object Storage Service:Store cold data at a low cost using tiered storage in the OSS-HDFS service

Supported regions

JindoSDK version

JindoSDK 6.8.0 or later is required.

If your JindoSDK version is earlier than 6.8.0, you cannot create objects directly in IA, Archive, Cold Archive, or Deep Cold Archive directories. As a workaround, create the object in a Standard directory, then move it using the rename operation.

Tickets required

You must submit a support ticket before using the feature:

• IA, Archive, and Cold Archive: One ticket covers all three classes.

• Deep Cold Archive: Submit a separate ticket.

• First-time activation: If the feature has never been enabled on your account, a single ticket activates all four storage classes.

Conversion size limits

• Converting Archive, Cold Archive, or Deep Cold Archive objects to Standard or IA in one operation: maximum 5 TB total.

• Archive, Cold Archive, or Deep Cold Archive objects in the Processing state at once: maximum 50 TB.

Lifecycle rule safety

Data retrieval fees

Reading IA, Archive, Cold Archive, or Deep Cold Archive objects incurs data retrieval fees. Avoid storing frequently accessed data in these storage classes. See Data processing fees.

Tag fees

Setting a storage policy adds a transition-storage-class tag to each data block. Tags are billed under OSS object tagging rules. See Object tagging fees.

Minimum storage duration

Each storage class has a minimum storage duration. Objects transitioned before reaching the minimum are still charged for the full minimum period.

How the clock is counted varies by target class:

• IA and Archive: The clock is not reset on conversion. Days spent in the prior class count toward the minimum, so prior storage time reduces the remaining obligation.

• Cold Archive and Deep Cold Archive: The clock resets on conversion. The full 180-day minimum applies from the conversion date, regardless of prior storage duration.

Examples:

Step 1: Set up JindoFS SDK

Before you begin, ensure that you have:

• Data written to OSS-HDFS

• JindoSDK 6.8.0 or later installed (see Connect non-EMR clusters to OSS-HDFS)

• A submitted support ticket (see Tickets required)

1. Connect to an Elastic Compute Service (ECS) instance. See Connect to an instance.

2. Download the JindoFS SDK JAR package.

3. Go to the bin directory of the extracted package:

      cd jindofs-sdk-x.x.x-linux/bin/

4. Create a configuration file named jindosdk.cfg in the bin directory:

      [client]
      fs.oss.accessKeyId = <your-access-key-id>
      fs.oss.accessKeySecret = <your-access-key-secret>
      fs.oss.endpoint = cn-hangzhou.oss-dls.aliyuncs.com

   Replace cn-hangzhou.oss-dls.aliyuncs.com with the endpoint for your region.

5. Set the JINDOSDK_CONF_DIR environment variable to the absolute path of the jindosdk.cfg configuration file:

      export JINDOSDK_CONF_DIR=<JINDOSDK_CONF_DIR>

Step 2: Assign a storage policy

Run setStoragePolicy on the directory containing the data to tier. The command tags all objects in that directory for conversion.

Step 3: Enable the feature in the OSS console

1. Log on to the OSS console.

2. In the left-side navigation pane, click Buckets, then click the target bucket name.

3. In the left-side navigation tree, choose Data Lake > OSS-HDFS.

4. On the OSS-HDFS tab, click Configure.

5. In the Basic Settings section of the Automatic Storage Tiering panel, turn on Status. OSS automatically creates lifecycle rules for each tag value. Each rule converts objects in .dlsdata/ that carry the corresponding tag one day after their last modification.

   

6. Click OK.

After enabling the feature:

• OSS loads the lifecycle rules within 24 hours of creation.

• Lifecycle rules run once per day at 08:00 (UTC+8). The exact completion time varies by object count.

• Objects reach their target storage class within at least 48 hours.

setStoragePolicy

./jindofs fs -setStoragePolicy -path <path> -policy <policy>

Assigns a storage policy to all objects in a path.

getStoragePolicy

./jindofs fs -getStoragePolicy -path <path>

Returns the storage policy assigned to a path.

unsetStoragePolicy

./jindofs fs -unsetStoragePolicy -path <path>

Removes the storage policy from a path.

checkStoragePolicy

./jindofs fs -checkStoragePolicy -path <path>

Returns the conversion task status for objects in a path.

Restore Archive or cold-tier objects

./jindofs fs -setStoragePolicy -path <path> -policy <policy> -restoreDays <days>

Temporarily restores Archive, Cold Archive, or Deep Cold Archive objects for direct access.

Before restoring:

• Wait at least two days after applying CLOUD_AR, CLOUD_COLD_AR, or CLOUD_DEEP_COLD_AR before running a restore.

• After restoration starts, Archive objects become readable within several minutes. Cold Archive and Deep Cold Archive objects take several hours.

• After the retention period ends, the object can no longer be read. To extend access, restore again during the retention period—allow at least two days between restoration operations.