Server Merging
1. Function Description
Server merging, which focuses on the scenario where multiple zone servers and their related storage data are merged into a single zone server. This function is commonly used at present.
2. Application Scenarios
When the activity of the zone server decreases or when a product operation is proposed, server merging can be used. Server merging copies table data from one zone to another zone.（Note: Only DBAs have permission to operate batch copying of table data. If business cooperation is required, DBAs should be contacted for operation）
3. Instructions
Select cluster, app, game zones (optional), tables (optional), and then batch copy table data.
4. Notations
- It is recommended to stop data access to the source server during server merging, especially write operations.
- Server merging requires early consideration of primary key conflicts. And it is necessary to pay attention to all error logs encountered in copying table data transactions. The common error that may occur is a primary key conflict.
- Generally, there is a time limit for server merging. So the relocation time for copying table data needs to be evaluated in advance;
- It is generally recommended to stop taking the service for server merging.
- The capacity of the target end of the cooperative server and the supported QPS both require the DBA to communicate with the business in advance and evaluate whether it can meet expectations.
- Use the "Copy Table Data" function to collaborate between two zones. If the same table in two zones has the same key, the processing logic is as follows: </br>Assuming copying table data from Zone 1 to Zone 2 for Table A. So for data with the same key in Table A for Zone 1 and Zone 2, the data in Zone 2 will be kept unchanged and will not be copied from Zone 1 to Zone 2. And there will be no relevant prompts on the transaction page. </br>Please be aware of this logic by the DBA and unify it with the business plan. Cooperative servers should avoid situations where two zones have the same table key conflicts. If there must be a key conflict, here is the following suggestion: If you want to preserve the data in Zone 1 as much as possible, you should operate Zone 2 to Zone 1 server. If you want to preserve the data in Zone 2 as much as possible, you should operate Zone 1 to Zone 2 server.