Manage Proxy Instance
Manage Proxy Instances
- Login RDS Admin Console。
- Select the region where the instance is located at the upper left corner of the console page.
- Click the target Proxy Instance Name, enter the proxy instance details page, where you can perform management operations such as restarting ,releasing etc. (for more methods of releasing the instance, refer to Release Instances).
Modify the proxy instance name
The account number and database of the proxy instance are all synchronized through the master instance, so the name of the proxy instance can be modified synchronously by modifying the name of the master instance.
- Login RDS Admin Console。
- Select the region where the instance is located at the upper left corner of the console page.
- Method I: find the target instance, move the mouse onto the Instance Name, then click the edit icon behind teh instance name to modify it immediately.
- Method II: click the target Proxy Instance Name to enter the detailed page of proxy instance, click the button Change behind the Name, then modify the name in the window that pops up, and then click OK to save the modification.
Create and manage agent account number
- Login RDS Admin Console。
- Select the region where the instance is located at the upper left corner of the console page.
- Click the target Proxy Instance Name to enter the details page of proxy instance.
- Click the Account Management Button on the left side of the page to enter the account management page.
- Click theCreate Special Account of Proxy Instance on the top of the page to enter the page of creating special account.
-
After entering the account creation page, you can set the database account number and password, and authorize the relevant database.
Parameter Description Database account number Fill in the account name. The requirements are as follows:
• 8~10 characters.
• start with a letter and end with a letter or number.
• composed of lowercase letters, numbers or underscores.Database authorization authorize one or more databases for the account.
• select one or more databases in the Database Name column on the left;
• Select the Read and Write or Read Only privileges for database in the Privilege Setting column on the right.Password • 6-32 characters.
• composed of letters, numbers and at lease two kinds of special characters (such as !@#%^_).Confirm password Enter the password again: Remarks Not required, note relevant information of this account for the convenience of subsequent account management. Support up to 256 characters. - Click OK, after successful creation, you can see that "Account Type" is anProxy Instance Account and you can modify the account password on the account list page, modify the privileges and delete account.
Description:
- After creating a special account for proxy instance, you need to connect to the proxy instance with the proxy account and password.
- The special account of the proxy instance will be automatically synchronized to the master instance when it is being created.
You can also Go Back to Master Instance Account Management for account creation and managment operations. Specific operations can be found in Create Account.
Monitor and alarm
- Login RDS Admin Console.
- Select the region where the instance is located at the upper left corner of the console page.
- Click the target Proxy Instance Name to enter the details page of proxy instance.
- Click Monitor on the left side of the page to view the number of query requests, number of update requests and number of connections. For specific operations, please refer to Monitoring and Alarm.
Security Management
- Login RDS Admin Console.
- Select the region where the instance is located at the upper left corner of the console page.
- Click the target Proxy Instance Name to enter the details page of proxy instance.
- Click the Security on the left side of the page to enter the security page. You can set the white list and DB firewall for the proxy instance. For specific operations, please refer to White List Management, DB Firewall.
Cluster Management
Users can view the status of the master instance and the read-only instance in the cluster on the cluster management page of the proxy instance, and control whether the read-only instance in the clusters that read and write are separated undertakes the business traffic by opening or closing the traffic switch of the read-only instance.
Precautions
- Only one proxy instance can be bound to a master instance.
- After purchasing the read-only instance, you need to manually open the read traffic bearing function of the instance.
- You can open the read-only instance read traffic bearing function through the proxy instance page or through your business codes.
View cluster instance information
On the cluster management page, the master instance and read-only instance bound to the current proxy instance will be displayed, that is, the information of the master instance and all read-only instances belonging to the same cluster. On the cluster management page, you can set whether the bound master instance and read-only instance bear read traffic.
Set the read traffic weight of the instance
- Login RDS Admin Console。
- Select the region where the instance is located at the upper left corner of the console page.
- Click the target Proxy Instance Name to enter the details page of proxy instance.
- Click theCluster Management on the left side of the page to enter the cluster management page.
- Click the Set Weight button in the operation bar to allocate the read traffic ratio borne by the master instance and the read-only instance. The read traffic weight is set to 5 options from 1 to 5, the larger the number, the greater the read traffic weight borne by the corresponding instance is. After setting, the ratio of the read traffic weight numbers in the master instance and the read-only instance is the ratio of the read traffic borne by each instance that read and write are separated.
Example of setting read traffic weight
Master instance binds 1 read-only instance
In the following page, the proxy instance purchased by the user is bound with a master instance and a read-only instance, and the read traffic settings of the master instance and the read-only instance are all turned on.
At the same time, the user sets the read traffic weight of the master instance as 1 and the read traffic weight of the read-only instance as 3. Under this setting, the ratio of read traffic undertaken by the master instance to the read-only instance is 1: 3, that is, the master instance bears 1/4 of the read traffic, and the read-only instance bears 3/4 of the read traffic.
Master instance binds more than one read-only instance
If you buy multiple read-only instances for the master instance and set the read traffic ratio borne by the instance through the proxy instance, the final read traffic ratio rule will remain unchanged from the ratio rule of buying only one read-only instance.
If you buy three read-only instances for one master instance, and set the read traffic weight of the master instance to 1 through the bound proxy instance, and the read traffic weights of the three proxy instances are respectively 2, 2 and 2, then the read traffic ratio of the master instance to the read-only instance realized by the read-write separation function is as follows: 1:2:2:2, that is, the master instance bears 1/7 read traffic, and the three read-only instances bear 2/7 read traffic respectively.