Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- 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
Show all
Copied.
Using a Client to Access a ClickHouse Cluster
You can use SQL to access a cluster on an ECS. For details about how to install the client, see Installing the Client.
The VPC and security group of the cluster to be created must be the same as those of the ECS on the public network. Otherwise, the client cannot access the cluster.
Installing the Client
- Prepare a Linux ECS. For details, see Preparing an ECS.
- Log in to the CloudTable management console, click Help in the navigation pane on the left, and click Download Client and Client Verification File on the right of the page to download the client installation package and client verification file.
- Install the client and connect to the cluster.
- Use the SSH login tool to remotely log in to the Linux ECS through the EIP.
For details, see Login Using an SSH Password in the Elastic Cloud Server User Guide.
- Go to the root directory of the SSH login tool.
cd /
- Create a folder in the root directory.
mkdir Folder name
- Go to the directory of the created folder.
cd /Folder name/
- Place the client in the directory.
- Decompress the client package.
tar -zxf Client package name
- Decompress the client verification file to the same directory as the client.
- Decompress the client verification file.
cd <Path for storing the client verification file > tar -xzvf Client_sha256.tar.gz
- Obtain the client verification code.
sha256sum ClickHouse_Client_23.3.tar.gz
- Check the verification code in the client verification file and compare it with the client verification code. A match indicates no tampering, while a mismatch suggests tampering.
less ClickHouse_Client_23.3.tar.gz.sha256
- Decompress the client verification file.
- Load the .so file.
sh install.sh
- Go to the bin directory.
cd bin/
Grant the 700 permission to the directory.
chmod 700 clickhouse
- Connect to the ClickHouse cluster. For details about the port, see Table 1.
Use the following command to connect to a normal cluster.
./clickhouse client --host Private IP address of the cluster --port Port --user admin --password Password
For details about the security cluster connection command. For details, see Connecting to a Security Cluster.
./clickhouse client --host Private IP address of the cluster --port port --user admin --password Password --secure --config-file /root/config.xml
NOTE:
- Private IP address of the cluster: cluster access address on the cluster details page. Replace it with the access address of the cluster you purchased.
- Password: the password set when you purchase the cluster. If there are special characters, use backslashes (\) to escape them. If the password is enclosed in single quotation marks ('), the special characters do not need to be escaped.
Table 1 Custom security rules Direction
Action
Port/Range
Type
Destination/Source Address
Usage
Outbound
Allow
All
IPv4/IPv6
0.0.0.0/0
Permit in the outbound direction
Inbound
Allow
8123
Security group of the CloudTable ClickHouse cluster
ClickHouse HTTP port number
Allow
9000
ClickHouse TCP port number
Allow
8443
ClickHouse HTTPS port number
Allow
9440
Secure TCP security port of ClickHouse
- Use the SSH login tool to remotely log in to the Linux ECS through the EIP.
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