Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- Service Overview
- Billing
- Getting Started
-
User Guide
-
HBase User Guide
-
HBase Cluster Management
- Overview
- Managing Clusters
- Preparing an ECS
- Using HBase
- HBase Cold and Hot Data Separation
- HBase Thrift Server
- HBase Security Channel Encryption
- HBase Batch Data Import
- HBase Monitoring Clusters
- Self-Healing from HBase Hotspotting
- Global Secondary Indexes
-
HBase Cluster Management
-
ClickHouse User Guide
-
ClickHouse Cluster Management
- Overview
- Managing ClickHouse Clusters
- Using ClickHouse
- Migrating ClickHouse Data
- ClickHouse User Management
- ClickHouse Role Management
- ClickHouse Slow Query Management
- Configuring Secure Channel Encryption for ClickHouse Clusters
- Application of ClickHouse Cold and Hot Data Separation
- ClickHouse Monitoring Clusters
-
ClickHouse Cluster Management
- Permissions Management
- Audit Logs
- Cluster Log Management
-
HBase User Guide
-
Developer Guide
- HBase Application Development Guide
- ClickHouse Application Development Guide
-
FAQs
-
General
- What Services Does a CloudTable Cluster Provide?
- Why Do I Choose CloudTable Service?
- How Do I Prepare for Creating a CloudTable HBase Cluster?
- What Should I Pay Attention to When Using CloudTable Service?
- What Compression Algorithms Are Supported by CloudTable HBase Clusters?
- Can I Stop CloudTable Service?
- Which Programming Languages Are Supported by HBase External APIs in CloudTable?
- How Do I Determine the Number of Faulty RegionServers?
- What Special Characters Does CloudTable HBase Support?
- What Can I Do If the Index Table Does Not Match the Data Table After CloudTable Data Is Deleted?
- What Should I Do If Concurrent Tasks Run Slowly When Python Accesses CloudTable Through Thrift?
- How do I view the TTL attribute of HBase shell?
- Why Are My Server Resources Released?
- How Do I Delete a Cluster?
- How Do I Stop Services and Release Resources?
-
Connection and Access
- How Do I Access a CloudTable Cluster?
- Can I Use SSH to Access Computing Nodes of CloudTable?
- Why Can't I Access HBase After the ZK Address Is Configured?
- Why Is the Error "Will not attempt to authenticate using SASL (unknown error)" Reported When Connecting to HBase?
- How Do I View the IP Address Corresponding to a Domain Name in a CloudTable Link?
- How Do I Access CloudTable from Other Cloud Services?
- Can I Configure the hbase-site.xml File?
- How Do I Query the Creation Time of a Table in CloudTable HBase?
-
Data Read/Write
- Is Raw Data Stored in CloudTable HBase?
- Why Can't I Write Data to HBase?
- What Is the Maximum Size of Data Written to the HBase Cluster?
- How Do I Check the Daily Incremental Data in HBase Tables?
- What Should I Do If an Error Is Reported When I Access the CloudTable HBase Cluster?
- How Do I Delete the Backup Table of the ZooKeeper Node in the ClickHouse Cluster?
- What Should I Do If a Database Missing Error Occurs When a Table Is Created in the ClickHouse Cluster?
- Billing FAQs
-
General
- General Reference
Copied.
Using HBase Shell to Access a Cluster
You can use the HBase shell to access a cluster by deploying a client in one click or manually installing a client on an ECS. You are advised to use the one-click client deployment method. If a secure channel is enabled for the cluster, connect to the cluster by referring to connecting to an HBase cluster in security mode.
Deploying a Client in One Click
- Prepare a Linux ECS.
Using a one-click client deployment tool. The recommended Linux ECS operating systems are EulerOS, CentOS, Ubuntu, and SUSE. For details, see Preparing an ECS.
- Download the one-click client deployment tool.
Use the SSH login tool (such as PuTTY) to remotely log in to the Linux ECS through the EIP and run the following command to obtain the one-click deployment tool.
curl -O -k "https://cloudtable-publish.obs.myhuaweicloud.com/cloudtable-client/quick_start_hbase_shell.sh"
NOTE:
- This command applies to HBase 2.x.
- Obtain a cluster access address.
Log in to the CloudTable console and choose Cluster Management. In the cluster list, locate the required cluster and obtain the address in the Access Address (Intranet) column. The parameter value is the cluster access address, as shown in Figure 1.
- Use the tool to deploy the client.
Replace $zookeeper_address in the following command with the ZK link you obtained in 3. Then, run the command on the CLI of the ECS to deploy the client in one click.
- Commands for one-click client deployment for common clusters:
source quick_start_hbase_shell.sh $zookeeper_address
- Commands for one-click client deployment for common clusters:
- Start the shell to access the cluster.
After you run the source command to automatically deploy the client, the HBase shell is automatically started. You can also run the bin/hbase shell command to start the HBase shell to access the cluster.
Manually Installing a Client
- Prepare a Linux ECS.
For details, see the following content in Preparing an ECS.
- Download the client.
Log in to the CloudTable management console. In the navigation pane on the left, choose Help. On the right of the page, click Download Client to download the client installation package.
Figure 2 Downloading the client - Install the client and verify the client.
- Use a file transfer tool (such as WinSCP) to upload the client installation package to the Linux ECS.
- Use the SSH login tool (such as PuTTY) to log in to the Linux ECS through the EIP.
For details about how to log in to the Linux ECS, see Logging In to a Linux ECS > Login Using an SSH Password in the Elastic Cloud Server User Guide.
Run the following command to decompress the client installation package:
cd <Path of the client installation package> tar xzvf hbase-1.3.1-bin.tar.gz
cd <Path of the client installation package> tar xzvf hbase-2.4.14-bin.tar.gz
<Path of the client installation package>: Replace it with the actual path.
- Configure the ZooKeeper address in a configuration file.
In the decompression directory of the client installation package, open the hbase/conf/hbase-site.xml file and set the following parameters:
- hbase.zookeeper.quorum: The value of this parameter is the access address (Intranet) of the cluster found in the cluster list.
Log in to the CloudTable console and choose Cluster Management. In the cluster list, locate the required cluster and obtain the address in the Access Address (Intranet) column. See the following figure.
Figure 3 ZK link - mapreduce.cluster.local.dir: Check whether the configuration item exists. If the configuration item does not exist, add it.
The configuration example is as follows:
<configuration> <property> <name>hbase.zookeeper.quorum</name> <value>xxx-zk1.cloudtable.com,xxx-zk2.cloudtable.com,xxx-zk3.cloudtable.com</value> </property> <property> <name>mapreduce.cluster.local.dir</name> <value>${hadoop.tmp.dir}/mapred/local</value> </property> </configuration>
- hbase.zookeeper.quorum: The value of this parameter is the access address (Intranet) of the cluster found in the cluster list.
- Start the shell to access the cluster.
Run the bin/hbase shell command to start the shell to access the cluster.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot