检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Figure 3 Modifying access across CIDR blocks To ensure the ECS and the DB instance can communicate with each other, configure the connection by referring to VPC Peering Connection Overview. Parent topic: Connections
An ECS is available. For details, see Purchasing an ECS. GNU Compiler Collection (GCC) has been installed on the ECS. The created ECS is in the same region, AZ, VPC, and security group as the GeminiDB Redis instance.
Test Environment Region: CN-Hong Kong AZ: AZ1 Elastic Cloud Server (ECS): s3.2xlarge.2 flavor with 8 vCPUs, 16 GB of memory, and CentOS 7.5 64-bit image Replica set specifications: All specifications described in Table 1 Table 1 Replica set specifications Replica Set No.
<instance_ip> If you access an instance from an ECS, instance_ip is the private IP address of the instance. If you access an instance through an EIP, instance_ip is the EIP that has been bound to the instance.
To ensure the ECS and the instance can communicate with each other, configure the connection by referring to VPC Peering Connection Overview. Response Parameters Status code: 202 Table 4 Response body parameters Parameter Type Description job_id String Task ID.
Migration Performance Reference Migration environment Source: Deploy InfluxDB and the migration tool on an ECS with 4 vCPUs and 16 GB of memory.
Great Convenience Ready to use out of the box You can create an instance on the console and access the instance using an ECS over a private network to reduce response time and avoid the cost of using a public network.
Migration Performance Reference Environment: The source LevelDB and leveldb-port are deployed on a Huawei Cloud ECS with 4 vCPUs and 16 GB memory. The target DB is a three-node GeminiDB Redis instance with 2 vCPUs and 8 GB memory.
Migration Performance Reference Environment: Pika (single node) and pika-port are deployed on an ECS with 8 vCPUs and 32 GB memory on Huawei Cloud. The target DB is a three-node GeminiDB Redis instance with 8 vCPUs and 16 GB memory.
An ECS is available. For details, see Purchasing an ECS. GNU Compiler Collection (GCC) has been installed on the ECS. The created ECS is in the same region, AZ, VPC, and security group as the GeminiDB Redis instance.
Redis-full-check must be deployed on the ECS, and the ECS is connected to the source and destination databases. During incremental migration, data may be inconsistent due to network latency between the source and destination databases.
You can download the tool to an ECS and use CLI to facilitate migration. Required Permissions Ensure that the database port is enabled in the security group of the GeminiDB Redis instance. Migration Scenarios Table 1 Migration scenarios No.
An ECS is available. For details, see Purchasing an ECS. GNU Compiler Collection (GCC) has been installed on the ECS. The created ECS is in the same region, AZ, VPC, and security group as the GeminiDB Redis instance.
Start the open-source Redis 5.0 single-node process on the ECS to load the AOF file and wait till the process is started. Ensure that the startup directory of the open-source Redis is the same as the directory containing the AOF file.
GeminiDB Redis cluster specifications Region CN East-Shanghai1 AZ type Deployment across AZ 1, AZ 2, and AZ 3 vCPUs of nodes 16 Nodes 20 Total storage space 2 TB ECS specifications AZ type AZ 1 Specifications c7.4xlarge.2, 3 PCS vCPUs 16 Memory 32 GiB Operating System (OS) CentOS
For details about how to create an ECS, see Purchasing an ECS in Getting Started with Elastic Cloud Server. The Spark environment has been installed on the ECS. Procedure Obtain the private IP address and port number of the GeminiDB Cassandra instance.
A Linux ECS is used as an example. Non-SSL Connection If you connect to an instance over an unencrypted connection, disable SSL first. Otherwise, an error is reported. For details about how to disable SSL, see Configuring an SSL Connection.
If you want to connect to an instance using an ECS over a private network, ensure that the instance and the ECS are in the same VPC. If they are not, create a VPC peering connection between them. Subnet A subnet where your instance is created.
If you want to connect to an instance using an ECS over a private network, ensure that the instance and the ECS are in the same VPC. If they are not, create a VPC peering connection between them for access. Subnet A subnet where your instance is created.
If you want to connect to an instance using an ECS over a private network, ensure that the GeminiDB Cassandra instance and the ECS are in the same VPC. If they are not, create a VPC peering connection between them.