The development and O&M standards of ApsaraDB for Redis are provided for your reference.
Management methods
Method
Description
ApsaraDB for Redis console
The ApsaraDB for Redis console is a web application that is used to manage instances.
It provides a variety of O&M and management features to help you manage instances
in a convenient and visual manner.
API operations and SDKs
O&M engineers: ApsaraDB for Redis provides a wide range of API operations for you
to manage instances. For example, you can call the CreateInstance operation to create an instance. You can also call the API operations of different
Alibaba Cloud services to implement complex custom features.
Business developers: You can use client-integrated SDKs to run database commands to
manage data in instances. For example, you can run the SET command to set the value of a key.
ApsaraDB for Redis provides multiple data migration solutions based on Data Transmission
Service (DTS) to allow you to migrate data in different scenarios.
ApsaraDB for Redis provides multiple data synchronization solutions based on DTS.
These solutions apply to scenarios including data synchronization from self-managed
databases to Alibaba Cloud, active geo-redundancy, disaster recovery, and data analysis.
This topic provides answers to some frequently asked questions about data migration
and data synchronization, such as what the differences between data migration and
data synchronization are, how different solutions work, and how to troubleshoot issues.
You can receive notifications for events such as instance migrations and version upgrades
by phone call, email, or internal message or by using ApsaraDB for Redis console.
You can view event types, regions, considerations, and affected instances. You can
also change the scheduled switchover time.
ApsaraDB for Redis is integrated with CloudMonitor. You can configure alert rules
for ApsaraDB for Redis in the CloudMonitor console. Alerts are immediately generated
when thresholds are exceeded or when events are detected. This allows you to make
informed business decisions.
The lifecycle of an instance starts when the instance is created and ends when the
instance is released. A lifecycle contains stages such as configuration changes, major
version upgrades, minor version updates, and restarts.
You can change the virtual private cloud (VPC) or vSwitch in which an instance is
deployed. For example, you can change the VPC of an instance to the VPC where an Elastic
Compute Service (ECS) instance is deployed, or change the vSwitch to which an instance
is connected to the vSwitch to which an ECS instance is connected. This way, the instance
can communicate with the ECS instance over the internal network.
You can switch the network type of an instance from the classic network to VPC. Then,
clients can communicate with the instance within the same VPC. This ensures higher
security and lower network latency.
You can modify the endpoints and ports of instances. For example, you can modify ports
to improve the security of connections. You can also change the endpoint of a new
instance to the endpoint of the original instance. This way, you do not need to modify
the connection information on your application.
By default, ApsaraDB for Redis provides internal endpoints. To access an instance
over the Internet, you must apply for a public endpoint for the instance.
You can apply for a private endpoint for a cluster instance and use the endpoint to
directly access backend data shards. This connection method is similar to the method
used to connect to a native Redis cluster. Compared with the proxy mode, the direct
connection mode reduces the routing time and accelerates the response of ApsaraDB
for Redis.
ApsaraDB for Redis allows you to specify values for specific parameters based on your
business requirements. The supported parameters vary with engine version and architecture.
ApsaraDB for Redis supports automatic switchovers from master nodes to replica nodes.
You can also manually switch workloads from master nodes to replica nodes. This allows
you to perform disaster recovery drills in real time. You can switch the node roles
for an instance that is deployed across multiple zones based on your business deployment.
This way, your applications can connect to the nearest nodes.
ApsaraDB for Redis allows you to restart or rebuild a proxy node. This way, you can
perform real-time disaster recovery drills. You can also perform proactive O&M tasks
when the service is unavailable or when a high latency occurs.
If the current zone in which your instance is deployed has insufficient resources
for a specification upgrade or if you want to improve the disaster recovery capabilities
for the instance, you can migrate the instance to another zone in the ApsaraDB for
Redis console.
You can set the maintenance window to off-peak hours and perform O&M operations such
as configuration changes during the maintenance window. This way, you can prevent
impacts on business caused by transient connections.
ApsaraDB for Redis allows you to create multiple database accounts for an instance.
You can grant these accounts different permissions such as read-only and read/write
permissions. This helps you flexibly manage instances to minimize accidental operations
and improve data security.
To connect to an instance by using a client, you must add the IP address of the client
to a whitelist of the instance. Proper use and management of whitelists ensure secure
access to instances.
To enhance data transmission security, you can enable SSL encryption for your instances
and install SSL certificates that are issued by certificate authorities (CAs) to your
applications. SSL encryption can encrypt network connections at the transport layer.
This improves data security and ensures data integrity.
To enable password-free access for an instance, make sure that the client that you
want to connect to the instance and the instance are deployed in the same VPC. This
way, the client can access the instance without using passwords. After password-free
access is enabled, you can still use a username and a password to connect to the instance.
ApsaraDB for Redis supports a variety of performance monitoring metrics. You can query
the monitoring data of an instance during a specific period of time in the previous
month. This helps you gain insights into the status of the instance and troubleshoot
issues.
ApsaraDB for Redis provides real-time monitoring to help you understand the operational
status of an instance. This topic describes how the monitoring metrics work and their
limits.
ApsaraDB for Redis allows you to view the performance trends of an instance during
a specific period of time. The performance trend metrics include CPU utilization,
memory usage, queries per second (QPS), total number of connections, response time,
network traffic, and key hit ratio.
ApsaraDB for Redis allows you to view the real-time performance of an instance. The
real-time performance metrics include CPU utilization, memory usage, QPS, network
traffic, servers, keys, clients, and connections.
ApsaraDB for Redis allows you to view sessions between an instance and clients in
real time. A session contains statistics about clients, the commands that are run,
and connection durations. You can also close abnormal sessions based on business requirements.
The offline key analysis feature can analyze backup files of ApsaraDB for Redis and
find large keys in your instances. This feature allows you to view instance information
such as the memory usage, distribution, and expiration time of keys. You can optimize
your instances based on the analyses. This feature helps you resolve issues such as
insufficient memory and performance degradation that are caused by the skewed distribution
of keys.
In ApsaraDB for Redis, the keys that are frequently accessed are called hotkeys. Improper
management of hotkeys may cause congestion and degrade service performance. ApsaraDB
for Redis allows you to view hotkeys in an instance in real time.
You can create a diagnostic report for an instance within a specified period of time.
Diagnostic reports help you evaluate the status of an instance by using metrics such
as performance level, skewed request distribution, and slow logs. Diagnostic reports
also help you identify exceptions in an instance.
ApsaraDB for Redis is integrated with CloudMonitor. You can configure alert rules
for ApsaraDB for Redis in the CloudMonitor console. Alerts are immediately generated
after specified thresholds are exceeded or exceptions are detected. This allows you
to troubleshoot issues at the earliest opportunity.
A new version of the audit log feature is released by ApsaraDB for Redis. The new
version is integrated with Log Service and allows you to view, analyze online, and
export log data. The new version helps you gain insights into the security and performance
of instances.
Issues such as connection timeouts that are caused by slow queries degrade service
performance. The slow log feature allows you to identify the IP addresses of clients
that sent the query requests to troubleshoot issues.
ApsaraDB for Redis offers high performance, high security, high availability, and
diverse architectures. An increasing number of applications run ApsaraDB for Redis
as their database engine for persistent storage. ApsaraDB for Redis provides a variety
of solutions that allow you to back up or restore data in different scenarios.
This topic describes how to troubleshoot performance issues and provides improvement
solutions. In the examples, high CPU utilization, high memory usage, and high bandwidth
usage issues are troubleshot.
This topic provides answers to some frequently asked questions about the features,
usage, connection methods, data persistence mechanisms, and parameters of ApsaraDB
for Redis.
