All Products
Search
Document Center

Realtime Compute for Apache Flink:Manage namespaces

Last Updated:Feb 07, 2025

A namespace is a basic unit for managing deployments in Realtime Compute for Apache Flink. Configurations, deployments, and permissions of each namespace are separately managed. After you purchase a Realtime Compute for Apache Flink workspace, a default namespace is generated in the workspace. The suffix of the namespace is default. You can create multiple namespaces and assign separate resources and permissions to each namespace. This way, the resources and permissions of multiple tenants are isolated among namespaces. This topic describes how to create, go to, view, and delete a namespace.

Prerequisites

Create a namespace

  1. Log on to the management console of Realtime Compute for Apache Flink.

  2. Check that the number of available compute units (CUs) in the desired workspace is greater than 1. For more information about how to reconfigure resources, see Reconfigure resources.

  3. Find the desired workspace and choose More > Add Project in the Actions column.

    Parameter

    Description

    Project Name

    The namespace name can contain lowercase letters, digits, and hyphens (-). The namespace name must start with a lowercase letter and cannot end with a hyphen (-).

    Note
    • The namespace name cannot be the same as the name of an existing namespace.

    • After you create a namespace, you cannot change the name of the namespace.

    CU Type

    The CU type that you must configure for workspaces with cross-zone resources. Valid values:

    • Single zone: Zone-disaster recovery is not supported. A namespace that uses single-zone CUs has the risk of service interruptions due to a single zone failure. Zones in the same region can communicate with each other. The service level agreement (SLA) of the zones ensures that the network latency is less than 3 ms. For more information, see Average Latency among Zones.

    • Cross zone: Cross-zone high availability provides higher availability and zone-disaster recovery. For a namespace that uses cross-zone CUs, if the zone in which a deployment is run fails, the deployment can be resumed in other stable zones of the same region. This ensures the continuity and high availability of deployments. For more information, see Cross-zone high availability.

    Allocate Resources

    A namespace requires at least one CU.

    For a workspace that uses hybrid billing, you can configure only fixed resources when you create a namespace. After you create a namespace, you can configure the maximum number of available elastic resources for the namespace. For more information, see Reconfigure resources.

  4. Click OK.

Go to a namespace

Log on to the management console of Realtime Compute for Apache Flink and use one of the following methods to go to a namespace:

  • Find the desired workspace and click Console in the Actions column. In the upper-left corner of the development console of Realtime Compute for Apache Flink, select the desired namespace.

  • Click the 展开按钮 icon on the left side of the ID of the desired workspace and click the name of the desired namespace.

View and delete a namespace

Log on to the management console of Realtime Compute and click the 展开按钮 icon on the left side of the ID of the desired workspace.

  • To view a namespace: In the namespace list, view the namespace information in columns, such as Status, CU Type, and Created At.

  • To delete a namespace: Find the desired namespace, click Delete in the Actions column. In the message that appears, click OK.

    Important

    After you delete a namespace, deployments and data in the namespace cannot be restored. Proceed with caution.

References

  • After you create a namespace, you can click the name of the namespace to go to the development console of Realtime Compute for Apache Flink to develop a draft. For more information, see Draft development.

  • To allow multiple users to use a namespace to perform operations such as draft development and deployment O&M, you must grant permissions on the namespace to the users. For more information, see Grant permissions on namespaces.

  • For the basic concepts of Realtime Compute for Apache Flink, see Basic concepts.