TDSQL-C for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Suggestions on Usage Specifications
- Kernel Features
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Value-Added Services Billing Overview
- Database Audit
- Audit Rule Template
- Serverless Service
- Serverless Introduction
- Serverless Resource Pack
- Configuration Change
- Operation Guide
- Database Connection
- Configuring Network Address
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Kernel Features
- Managing Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Console Account
- Database Account
- Configuring Custom Password Strength
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Utilization of Columnar Storage Indexes
- Read-Only Analysis Engine
- Feature Limits and Compatibility
- Description of Functions and Operators
- Read-Only Analysis Engine Management
- Data Loading
- Executing Queries
- Exclusive Features
- Performance Optimization
- Performance White Paper
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Performing Backup
- Managing Backup
- Rollback
- Restoring Data from Logical Backups
- Restoring Data Through the Console
- Restoring Data from Snapshot Backup
- Data Migration
- Parallel Query
- Setting Parallel Query
- Database Security and Encryption
- Access and Authorization
- Security Group Management
- TencentDB Security Group Management
- Monitoring and Alarms
- Monitoring
- Alarms
- Monitoring Metric Alarm
- Practical Tutorial
- Data Rollback
- Database/Table-Level Rollback
- Rolling back Entire Cluster
- White Paper
- Security White Paper
- Performance White Paper
- Troubleshooting
- Connection Issues
- API Documentation
- Making API Requests
- Instance APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
DocumentationTDSQL-C for MySQLOperation GuideRead-Only Analysis EngineRead-Only Analysis Engine ManagementBasic Operations Management
Basic Operations Management
Last updated: 2025-01-02 09:48:41
Operations on read-only analysis engine instances are consistent with those on other read-only instances. You can directly perform individual operations on a read-only analysis engine instance. This document introduces the operations supported by read-only analysis engine instances under a TDSQL-C for MySQL cluster.
Prerequisites
You have prepared a read-only analysis engine instance. See Enabling Read-Only Analysis Engine.
The instance is in the running status.
Related Operation Guide
Viewing Instance Information
1. Log in to the TDSQL-C MySQL console and click the target cluster in the cluster list on the left to enter the cluster management page.
2. In the cluster details, locate the read-only analysis engine instance to view the brief information about the read-only analysis engine.
3. In the instance information on the right side of the cluster details page, locate the read-only analysis engine instance, and click Details to enter the details page of the read-only analysis engine instance and view the detailed information about the instance.
Renaming an Instance
The method is consistent with that of read-write instances and read-only instances. See Renaming Instance.
Modifying Security Groups
The method is consistent with that of read-write instances and read-only instances. The only difference is selecting the instance type as read-only analysis engine instance. See Matching Security Group for TencentDB.
Modifying the IP and Port
The method is consistent with that of read-write instances and read-only instances. See Modifying Private Network Address.
Changing Network
The method is consistent with that of read-write instances and read-only instances. See Changing Network.
Enabling/Disabling Public Network Address
The method is consistent with that of read-write instances and read-only instances. See Enabling/Disabling Public Network Address.
Note:
Enabling public network address requires authorization for binding the private IP address with a public IP address. Exposing an instance to the public network presents certain security risks. Therefore, the public network address can be enabled only after the authorization is confirmed.
Public network access is solely for assisting in or developing database management. For business access, use private network access.
Modifying Maintenance Time
The method is consistent with that of read-write instances and read-only instances. See Modifying Instance Maintenance Time.
Deleting and Restoring Instances
When an instance is no longer needed, it can be deleted. For the operation, see Deleting Instance. Once a read-only analysis engine instance is deleted, the instance cannot be accessed, but the data will continue to be loaded from the read-write node to the read-only analysis engine.
After a monthly subscription instance is deleted, it will be moved to the recycle bin and retained for 7 days during which it cannot be accessed. If you want to restore the instance, you can renew it in the recycle bin. For the operation, see Restoring Instance.
After a pay-as-you-go instance is deleted, it will be moved to the recycle bin and retained for 3 days during which it cannot be accessed. If you want to restore the instance, you can renew it in the recycle bin. For the operation, see Restoring Instance.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No