All Products
Search
Document Center

Billing

Last Updated: Jul 07, 2022

This topic describes the billing of resources in Data Lake Formation (DLF), including resource usage for data import, storage of metadata objects, and metadata requests.

Billing items and methods

Billing item

Description

Data ingestion tasks

It is currently in public beta and is free.

Metadata object storage

Accounting is based on the number of stored objects.

It is currently in public beta and is free.

API request

The billing is based on the number of API requests.

It is currently in public beta and is free.

Resource usage for data import

It is currently in public beta and is free.

Storage of metadata objects

  • Metadata objects are databases, tables, partitions, and indexes that are stored in the metadata of a data lake.

  • The first one million metadata objects are stored for free in each month. If the number of metadata objects exceeds one million, the part that exceeds one million metadata objects costs you USD 1 per month for every 100,000 metadata objects. If the number of metadata objects in the excess part is not a multiple of 100,000, the number is rounded up to the nearest multiple of 100,000 for billing.

  • Metadata objects are counted by the month and billed on the first day of each month. Payments are settled on the first day of each month.

Note

It is currently in public beta and is free.

Example:

On January 1, a data lake contains 100 databases, 10,000 tables, 500,000 partitions, and 5,000 indexes.

  • To sum up, a total of 515,100 metadata objects are stored in the data lake on January 1.

  • On January 31, 600,000 partitions are added, whereas the number of databases, tables, and indexes remains unchanged. In this case, a total of 1.1151 million metadata objects are stored in the data lake on January 31.

  • The bill that you receive on February 1 shows that you are charged USD 2 in total. To be specific, you are charged for free for the first one million metadata objects, but USD 2 for the part that exceeds one million metadata objects, which is 115,100 metadata objects.

  • On February 1, USD 2 is deducted from your account as the storage fee that is produced in January for the metadata objects in the data lake.

Metadata requests

  • Metadata requests are requests to create, read, modify, and delete databases, tables, partitions, indexes, and functions in the metadata of a data lake.

  • You can execute DDL statements in the computing engines that are associated with DLF to initiate metadata requests. The computing engines can be E-MapReduce (EMR) Hive, EMR Spark SQL, EMR Presto, and MaxCompute. You can use the DLF console or call API operations to manage metadata objects.

  • The first one million metadata requests are free of charge in each month. If the number of metadata requests exceeds one million, the part that exceeds one million metadata requests costs you USD 1 per month per million. If the number of metadata requests in the excess part is less than or equal to one million, one million is used for billing.

  • Metadata requests are counted by the month and billed on the first day of each month. Payments are settled on the first day of each month.

Note

It is currently in public beta and is free.

Example:

  • In January, the computing engines such as EMR, MaxCompute, and Hologres are used to create and access the metadata in DLF. The number of actual access times is 1.2 million. In this case, you are charged USD 1 in total in January. To be specific, you are charged for free for the first one million metadata requests, but USD 1 for the part that exceeds one million metadata requests, which is 200,000 metadata requests.

  • On February 1, USD 1 is deducted from your account as the fee that is produced in January for requests to manage the metadata in the data lake.

Impact of overdue payments

The tasks that are running and the data in DLF are not affected within 72 hours from the time when you have an overdue payment. However, in the 72-hour period, you cannot perform the following operations:

  1. Create data sources.

  2. Create data import tasks.

  3. Create databases and tables.

  4. Start data import tasks.

If you fail to settle your overdue payment after 72 hours, DLF further limits your access to resources:

  1. DLF stops your tasks that are running.

  2. You cannot call metadata operations.

If you fail to settle your overdue payment after 168 hours, DLF releases or deletes your resources:

  1. DLF deletes the data sources, data import tasks, and metadata objects such as databases, tables, and partitions that are within your Alibaba Cloud account.

  2. You cannot use the DLF console.

Note: The data cannot be recovered after it is released. We recommend that you back up the important data in advance.