Alibaba-based Open-Source Distributed Data Synchronization System installation Configuration documentation otter manager Single Instance configuration, alibabaotter

Alibaba-based Open-Source Distributed Data Synchronization System installation Configuration documentation otter manager Single Instance configuration, alibabaotter

The above is the configuration description. The following is the configuration process: the environment background is that two databases are synchronized to two databases in different regions: A-C and B-D. Five hosts are used in total, 192.168.64.132 ~ 134, 139, 140. Zk is deployed in 192.168.64.132 ~ 134. 134 deploy three instances, 132 and 133 deploy one instance each. The instance type is observer. The node is also in 192.168.64.132 ~ 1 In each configuration on 134. 134 configure two canal instances and managers. 192.168.64.132 ~ 133, 192.168.64.139 ~ 140 deploy one MySQL instance separately. Synchronization rules: 139-> 132, 140-> 133 other configurations are not mentioned here. Briefly describe the configuration on the manager. The internal environment configuration of the server is skipped. Manager Configuration: Step 1. add zk cluster 2. add node 3. add Database:. source database jdbc: mysql: // 192.168.64.139: 3306 B. target jdbc: mysql: // 192.168.64.132: 3306 4. add synchronization table information:. source data table. * B. target data table. * 5. add canal:. provide database IP information 6. add channel: 7. add pipeline:. select node B. select canal 8. add synchronization ing Rule. define the synchronization relationship between the source table and the target table 9. start 10. test Data

Add a zk cluster: Machine Management-> Add zookeeper management: 　　 The cluster list is separated by commas (,) and ends with a colon. 　　 　　 Add node: Machine Management-> Add node management: 　　 Recommended machine port 2088 　　　　 The content in the red box must be the nid ID we mentioned above. 　　 Add the nid to the node on the server and start the node. 　　   Add Database: the default test library is used here. The source and target databases must have the following libraries: character set: [client] default-character-set = utf8 [mysqld] character-set-server = utf8 table: create table 'user' ('id' int (11) not null auto_increment COMMENT 'user id', 'name' varchar (50) not null default ''comment' name ', 'sex' int (1) not null default '0' COMMENT '0 is male, 1 is female, primary key ('id') ENGINE = MyISAM default charset = utf8; 　　　　 　　　　   Configuration data table: 　　 Both the target and source databases must have the same database and table. 　　   Add canal: Two canal instances are configured on a server. Consider the id and port conflict: Add channel: Add pipelin: Add a synchronous image rule: enable synchronization: Test Data: multiple instances and a single instance are the same. In this environment, two source databases use two canal to simulate slave. Canal and node corresponding to different databases. Here we think that the above instance is only a single database ---> a single database. What if there are multiple databases? How can this problem be solved? In fact, they are all the same. You can add a ing table in the same channal --> Pipeline --> ing table. You can also create a database table corresponding to a channal --> Pipeline --> ing table. There are many methods.   Last document: Environment configuration of otter Based on alibaba Open-Source Distributed Data Synchronization System installation and configuration documents