Changing the M Compatibility Port

Scenarios

GaussDB allows you to use the templatem template to create an M-compatible database. You can enable, disable, or change the M compatibility port for a centralized instance on the console for better compatibility.

Constraints

• M-compatible databases can be created only for centralized instances of version V2.0-8.100 or later and distributed instances of version V2.0-8.200 or later. The distributed instances must be newly created, instead of those upgraded from an earlier version. For details about how to view the instance version, see Checking the DB Engine Version.
• For centralized instances earlier than V2.0-8.210 and distributed instances, only one M-compatible database can be created. For centralized instances of version V2.0-8.210 or later, you can create multiple M-compatible databases.
• M-compatible databases do not support database- and table-level backup and restoration.
• The M compatibility port cannot be changed for GaussDB instances that contain a database named templatem.
• This operation is not allowed for DR instances. To enable the M compatibility port for a DR instance, delete its DR relationship first.
• Enabling the M compatibility port will reboot the DB instance, during which services are interrupted. Perform this operation during off-peak hours.
• The port must have been enabled in the inbound rule of the security group.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > GaussDB.
4. On the Instances page, click the name of the target instance to go to the Basic Information page.
5. In the Network Information area, click or Apply in the Port for M Compatibility field.
   Figure 1 Setting the M compatibility port
   

6. In the displayed dialog box, set the M compatibility port, and click OK.
   • The port ranges from 1024 to 39989, but the following ports that are reserved for system use cannot be used: 2378 to 2380, 2400, 4999 to 5001, 5100, 5500, 5999 to 6001, 6009, 6010, 6500, 8015, 8097, 8098, 8181, 9090, 9100, 9180, 9187, 9200, 12016, 12017, 20049, 20050, 21731, 21732, 32122 to 32126, and 39001
   • The port cannot be a number in the range [Database port, Database port + 10].
   Figure 2 Enabling M compatibility port

   

7. Check the result.

   During the modification, the instance is in the Changing M compatibility port state. After the instance status becomes Available, check the port displayed in the Port for M Compatibility field.