tencent cloud

Elastic MapReduce

  • Release Notes and Announcements
  • Product Introduction
  • Purchase Guide
    • EMR on CVM Billing Instructions
    • EMR on TKE Billing Instructions
    • EMR Serverless HBase Billing Instructions
    • EMR Serverless TCBase Billing Overview
  • Getting Started
  • EMR on CVM Operation Guide
    • Planning Cluster
    • Administrative rights
    • Configuring Cluster
    • Managing Cluster
    • Managing Service
    • Monitoring and Alarms
    • TCInsight
  • EMR on TKE Operation Guide
  • EMR Serverless HBase Operation Guide
  • EMR Serverless TCBase Operation Guide
  • EMR Development Guide
    • Hadoop Development Guide
    • Spark Development Guide
    • Hbase Development Guide
    • Phoenix on Hbase Development Guide
    • Hive Development Guide
    • Presto Development Guide
    • Sqoop Development Guide
    • Hue Development Guide
    • Oozie Development Guide
    • Flume Development Guide
    • Kerberos Development Guide
    • Knox Development Guide
    • Alluxio Development Guide
    • Kylin Development Guide
    • Livy Development Guide
    • Kyuubi Development Guide
    • Zeppelin Development Guide
    • Hudi Development Guide
    • Superset Development Guide
    • Impala Development Guide
    • Druid Development Guide
    • TensorFlow Development Guide
    • Kudu Development Guide
    • Ranger Development Guide
    • Kafka Development Guide
    • StarRocks Development Guide
    • Flink Development Guide
    • JupyterLab Development Guide
    • MLflow Development Guide
  • Practical Tutorial
    • Practice of EMR on CVM Ops
    • Data Migration
    • Practical Tutorial on Custom Scaling
  • API Documentation
    • History
    • Introduction
    • API Category
    • Making API Requests
    • Cluster Resource Management APIs
    • Cluster Services APIs
    • User Management APIs
    • Information Query APIs
    • Scaling APIs
    • Configuration APIs
    • Other APIs
    • Cluster Lifecycle APIs
    • Serverless HBase APIs
    • YARN Resource Scheduling APIs
    • Data Types
    • Error Codes
  • FAQs
    • EMR on CVM
  • Service Level Agreement
  • Contact Us

Creating an Instance

Download
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-07-14 12:12:44

Overview

This document introduces the directions and related configuration for creating an EMR Serverless HBase instance through the EMR console.

Preparations

1. The EMR service has been authorized with the service role EMR_QCSRole.
2. The user has instance creation permissions.

Directions

Log in to the EMR Serverless HBase console. Click create instance on the EMR Serverless HBase instance list page, and complete the related configuration on the purchase page. When the instance status in the instance list shows as running, it means the instance has been successfully created.
Configuration Item
Configuration Item Description
Region
The physical data center where the instance is deployed. Each data center is independent and private, networks of the cloud services between different data centers do not interconnect.
Note: After the instance is created, the region cannot be changed. Select carefully. For supported purchase regions, see Billing Overview.
Instance name
Set the instance name to distinguish instances for different purposes.
Billing mode
Only pay-as-you-go and monthly subscription billing modes are supported.
Deployment mode
Support single-AZ deployment, Multi-AZ Deployment and Dual-Active Deployment.
Instance network
Select the corresponding private network in the region. If there is none, click create network to create one.
Availability zone and subnet
Select the availability zone and subnet for instance deployment.
Note: After the instance is created, the availability zone cannot be changed. Select carefully.
Storage type
Select the storage type, Standard Cloud Storage or Performance Cloud Storage.
Node specifications
Select the appropriate single node specification and number of nodes.
Storage capacity
Each node comes with a storage capacity of 100 GiB by default, adjustable in multiples of 100 GiB.
Node count
Set the node count, with a minimum of 3 nodes per instance.
Tag
Tencent Cloud tags can be used to differentiate the purposes of different instances. Besides, cost allocation can be done by tags.



도움말 및 지원

문제 해결에 도움이 되었나요?

피드백