High Available Usage Deployment

High available usage deployment of Seata depends on registry center, configuration center and database.

Seata-Server

The Seata-Server need registry center, and save transaction data into database, for example, use Nacos

  • Modify configuration in registry.conf
  1. registry {
  2.   type = "nacos"
  4.   nacos {
  5.     application = "seata-server"
  6.     serverAddr = "192.168.199.2"
  7.     namespace = ""
  8.     cluster = "default"
  9.     username = ""
  10.     password = ""
  11.   }
  12. }
  14. config {
  15.   type = "nacos"
  17.   nacos {
  18.     serverAddr = "192.168.199.2"
  19.     namespace = ""
  20.     group = "SEATA_GROUP"
  21.     username = ""
  22.     password = ""
  23.   }
  24. }
  • Modify configuration in configuration center
  1. service.vgroupMapping.my_test_tx_group=default
  2. store.mode=db
  3. store.db.datasource=druid
  4. store.db.dbType=mysql
  5. store.db.driverClassName=com.mysql.jdbc.Driver
  6. store.db.url=jdbc:mysql://192.168.199.2:30060/seata?useUnicode=true
  7. store.db.user=root
  8. store.db.password=123456
  • Create table global_table, branch_table, lock_table in database

Please reference script on /script/server/db/

Now, startup multiple seata-server, and then the server is support high available usage.

For example, using Kubernetes deploy, the configuration file like:

  1. apiVersion: v1
  2. kind: Service
  3. metadata:
  4.   name: seata-ha-server
  5.   namespace: default
  6.   labels:
  7.     app.kubernetes.io/name: seata-ha-server
  8. spec:
  9.   type: ClusterIP
  10.   ports:
  11.     - port: 8091
  12.       protocol: TCP
  13.       name: http
  14.   selector:
  15.     app.kubernetes.io/name: seata-ha-server
  17. ---
  19. apiVersion: apps/v1
  20. kind: Deployment
  21. metadata:
  22.   name: seata-ha-server
  23.   namespace: default
  24.   labels:
  25.     app.kubernetes.io/name: seata-ha-server
  26. spec:
  27.   replicas: 3
  28.   selector:
  29.     matchLabels:
  30.       app.kubernetes.io/name: seata-ha-server
  31.   template:
  32.     metadata:
  33.       labels:
  34.         app.kubernetes.io/name: seata-ha-server
  35.     spec:
  36.       containers:
  37.         - name: seata-ha-server
  38.           image: apache/seata-server:2.1.0
  39.           imagePullPolicy: IfNotPresent
  40.           env:
  41.             - name: SEATA_CONFIG_NAME
  42.               value: file:/root/seata-config/registry
  43.           ports:
  44.             - name: http
  45.               containerPort: 8091
  46.               protocol: TCP
  47.           volumeMounts:
  48.             - name: seata-config
  49.               mountPath: /root/seata-config
  50.       volumes:
  51.         - name: seata-config
  52.           configMap:
  53.             name: seata-ha-server-config
  56. ---
  57. apiVersion: v1
  58. kind: ConfigMap
  59. metadata:
  60.   name: seata-ha-server-config
  61. data:
  62.   registry.conf: |
  63.     registry {
  64.         type = "nacos"
  65.         nacos {
  66.           application = "seata-server"
  67.           serverAddr = "192.168.199.2"
  68.         }
  69.     }
  70.     config {
  71.       type = "nacos"
  72.       nacos {
  73.         serverAddr = "192.168.199.2"
  74.         group = "SEATA_GROUP"
  75.       }
  76.     }

You can reference seata-ha-deploy-practice for more detail about practice of HA deploy.