【實踐篇】SpringCloud + Eureka + Mybatis plus 整合分佈式事務Seata

項目簡介

項目使用Spring Cloud 分佈式框架,使用過程中,客戶提出了購買物品時,調用庫存微服務,使用庫存後,調用支付微服務失敗,庫存數據未正常回滾,導致數據兩邊數據不一致的問題。因此決定引入阿里的分佈式事務Seata。
本文邊詳細的介紹一下整合的過程,以及整合過程中遇到的問題。

  • 項目使用到的框架版本
  • SpringBoot : 1.5.13.RELEASE
  • SpringCloud : Edgware.SR3
  • SpringCloud Alibaba : 1.5.1.RELEASE
  • mybatis-plus : 3.1.0
  • druid : 1.1.12
  • seata : 0.9.0
  • mysql : 8.0

選擇對應的版本
可以在 Github上spring-cloud-alibaba的開源項目找到SpringCloud對應的seata版本
SpringCloud江湖

找到項目對應的版本後,下載對應的seata server,下載地址:https://github.com/seata/seata/releases

  • windows下載 seata-server-0.9.0.zip
  • Linux下載 seata-server-0.9.0.tar.gz

配置Seata Server服務

下載完對應的版本後, 將其解壓。可以看到內容如下:

SpringCloud江湖

  • bin:主要放置Seata server的啓動文件
  • conf:主要放置Seata server的配置文件和數據庫表結構
  • lib:主要放置一些依賴的jar包

conf的目錄如下:
SpringCloud江湖

  • db_undo_log.sql:初始化的數據庫的表結構
  • file.conf:Seata server的配置文件
  • registry.conf:Seata server註冊的配置文件

修改conf下的registry.conf文件

registry {
  # file 、nacos 、eureka、redis、zk、consul、etcd3、sofa
  type = "eureka"  # 修改這裏,這裏我使用的時eureka註冊中心,對應下面的eureka配置,其他的配置信息可刪除

  nacos {
    serverAddr = "localhost"
    namespace = ""
    cluster = "default"
  }
  
  # 修改這裏,因爲上面用的是eureka,需要配置下面的eureka註冊信息
  eureka {
    serviceUrl = "http://127.0.0.1:8761/eureka"
    application = "seata-server"
    weight = "1"
  }
  redis {
    serverAddr = "localhost:6379"
    db = "0"
  }
  zk {
    cluster = "default"
    serverAddr = "127.0.0.1:2181"
    session.timeout = 6000
    connect.timeout = 2000
  }
  consul {
    cluster = "default"
    serverAddr = "127.0.0.1:8500"
  }
  etcd3 {
    cluster = "default"
    serverAddr = "http://localhost:2379"
  }
  sofa {
    serverAddr = "127.0.0.1:9603"
    application = "default"
    region = "DEFAULT_ZONE"
    datacenter = "DefaultDataCenter"
    cluster = "default"
    group = "SEATA_GROUP"
    addressWaitTime = "3000"
  }
  file {
    name = "file.conf"
  }
}

config {
  # file、nacos 、apollo、zk、consul、etcd3
  type = "file" # 這裏使用file的配置文件,其餘的可以刪除掉

  nacos {
    serverAddr = "localhost"
    namespace = ""
  }
  consul {
    serverAddr = "127.0.0.1:8500"
  }
  apollo {
    app.id = "seata-server"
    apollo.meta = "http://192.168.1.204:8801"
  }
  zk {
    serverAddr = "127.0.0.1:2181"
    session.timeout = 6000
    connect.timeout = 2000
  }
  etcd3 {
    serverAddr = "http://localhost:2379"
  }
  
  # 使用conf下的file.conf配置
  file {
    name = "file.conf"
  }
}

修改conf下的file.conf文件

transport {
  # tcp udt unix-domain-socket
  type = "TCP"
  #NIO NATIVE
  server = "NIO"
  #enable heartbeat
  heartbeat = true
  #thread factory for netty
  thread-factory {
    boss-thread-prefix = "NettyBoss"
    worker-thread-prefix = "NettyServerNIOWorker"
    server-executor-thread-prefix = "NettyServerBizHandler"
    share-boss-worker = false
    client-selector-thread-prefix = "NettyClientSelector"
    client-selector-thread-size = 1
    client-worker-thread-prefix = "NettyClientWorkerThread"
    # netty boss thread size,will not be used for UDT
    boss-thread-size = 1
    #auto default pin or 8
    worker-thread-size = 8
  }
  shutdown {
    # when destroy server, wait seconds
    wait = 3
  }
  serialization = "seata"
  compressor = "none"
}
service {
  #vgroup->rgroup
  vgroup_mapping.my_test_tx_group = "seata-server"  # 修改這裏,registry.conf文件裏的eureka的application
  #only support single node
  default.grouplist = "127.0.0.1:8091" # 修改這裏,這裏是seata的默認端口號,啓動的時候可以指定端口號,記得對應
  #degrade current not support
  enableDegrade = false
  #disable
  disable = false
  #unit ms,s,m,h,d represents milliseconds, seconds, minutes, hours, days, default permanent
  max.commit.retry.timeout = "-1"
  max.rollback.retry.timeout = "-1"
}

client {
  async.commit.buffer.limit = 10000
  lock {
    retry.internal = 10
    retry.times = 30
  }
  report.retry.count = 5
  tm.commit.retry.count = 1
  tm.rollback.retry.count = 1
}

## transaction log store
store {
  ## store mode: file、db
  mode = "file"  # 這裏使用的是file

  ## file store
  file {
    dir = "sessionStore"

    # branch session size , if exceeded first try compress lockkey, still exceeded throws exceptions
    max-branch-session-size = 16384
    # globe session size , if exceeded throws exceptions
    max-global-session-size = 512
    # file buffer size , if exceeded allocate new buffer
    file-write-buffer-cache-size = 16384
    # when recover batch read size
    session.reload.read_size = 100
    # async, sync
    flush-disk-mode = async
  }

  ## database store
  db {
    ## the implement of javax.sql.DataSource, such as DruidDataSource(druid)/BasicDataSource(dbcp) etc.
    datasource = "druid"
    ## mysql/oracle/h2/oceanbase etc.
    db-type = "mysql"
    driver-class-name = "com.mysql.cj.jdbc.Driver"
    url = "jdbc:mysql://192.168.0.65:3306/core"
    user = "root"
    password = "123456"
    min-conn = 1
    max-conn = 3
    global.table = "global_table"
    branch.table = "branch_table"
    lock-table = "lock_table"
    query-limit = 100
  }
}
lock {
  ## the lock store mode: local、remote
  mode = "remote"

  local {
    ## store locks in user's database
  }

  remote {
    ## store locks in the seata's server
  }
}
recovery {
  #schedule committing retry period in milliseconds
  committing-retry-period = 1000
  #schedule asyn committing retry period in milliseconds
  asyn-committing-retry-period = 1000
  #schedule rollbacking retry period in milliseconds
  rollbacking-retry-period = 1000
  #schedule timeout retry period in milliseconds
  timeout-retry-period = 1000
}

transaction {
  undo.data.validation = true
  undo.log.serialization = "jackson"
  undo.log.save.days = 7
  #schedule delete expired undo_log in milliseconds
  undo.log.delete.period = 86400000
  undo.log.table = "undo_log"
}

## metrics settings
metrics {
  enabled = false
  registry-type = "compact"
  # multi exporters use comma divided
  exporter-list = "prometheus"
  exporter-prometheus-port = 9898
}

support {
  ## spring
  spring {
    # auto proxy the DataSource bean
    datasource.autoproxy = false
  }
}

啓動seata server服務

進入bin目錄,如果使用的eureka,需要先啓動eureka server註冊中心,使用其他的,也需要先啓動

SpringCloud江湖

linux下啓動seata server: -p 後面可以指定seata server啓動的端口號

nohup sh seata-server.sh -p 8091 &

啓動後可以看到

windows啓動直接雙擊。

啓動後查看eureka是否註冊到eureka註冊中心。

在系統服務中配置使用Seata

1、首先通過maven引入seata依賴

在pom.xml的dependencyManagement下引用spring-cloud-alibaba

<!-- 引入seata依賴 -->
<dependencies>
    <dependency>
        <groupId>com.alibaba.cloud</groupId>
        <artifactId>spring-cloud-alibaba-seata</artifactId>
        <version>1.5.1.RELEASE</version>
    </dependency>
</dependencies>

<!-- 引入spring-cloud-alibaba-->
<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.alibaba.cloud</groupId>
            <artifactId>spring-cloud-alibaba-dependencies</artifactId>
            <version>1.5.1.RELEASE</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    <dependencies>
</dependencyManagement>

2、對應的service需要在resources目錄下添加registry.conf和file.conf文件

文件對應內容如下:

  • registry.conf
registry {
  # file 、nacos 、eureka、redis、zk、consul、etcd3、sofa
  type = "eureka"

  eureka {
    serviceUrl = "http://127.0.0.1:8761/eureka"   # 注意這裏,對應eureka註冊中心
    application = "seata-server"                  # 注意這裏,對應registry.conf文件裏的eureka的application
    weight = "1"
  }
}

config {
  # file、nacos 、apollo、zk、consul、etcd3
  type = "file"

  file {
    name = "file.conf"
  }
}
  • file.conf
transport {
  # tcp udt unix-domain-socket
  type = "TCP"
  #NIO NATIVE
  server = "NIO"
  #enable heartbeat
  heartbeat = true
  #thread factory for netty
  thread-factory {
    boss-thread-prefix = "NettyBoss"
    worker-thread-prefix = "NettyServerNIOWorker"
    server-executor-thread-prefix = "NettyServerBizHandler"
    share-boss-worker = false
    client-selector-thread-prefix = "NettyClientSelector"
    client-selector-thread-size = 1
    client-worker-thread-prefix = "NettyClientWorkerThread"
    # netty boss thread size,will not be used for UDT
    boss-thread-size = 1
    #auto default pin or 8
    worker-thread-size = 8
  }
  shutdown {
    # when destroy server, wait seconds
    wait = 3
  }
  serialization = "seata"
  compressor = "none"
}
service {
  #vgroup->rgroup
  vgroup_mapping.my_test_tx_group = "seata-server"   # 注意這裏,對應registry.conf文件裏的eureka的application
  #only support single node
  default.grouplist = "127.0.0.1:8761:8091"          # 修改這裏,對應seata server的ip和端口號
  #degrade current not support
  enableDegrade = false
  #disable
  disable = false
}

client {
  async.commit.buffer.limit = 10000
  lock {
    retry.internal = 10
    retry.times = 30
  }
  report.retry.count = 5
  tm.commit.retry.count = 1
  tm.rollback.retry.count = 1
}
transaction {
  undo.data.validation = true
  undo.log.serialization = "jackson"
  undo.log.save.days = 7
  #schedule delete expired undo_log in milliseconds
  undo.log.delete.period = 86400000
  undo.log.table = "undo_log"
}

support {
  ## spring
  spring {
    # auto proxy the DataSource bean
    datasource.autoproxy = false
  }
}

3、修改對應微服務下的application.yml配置文件

spring:
   cloud:
     alibaba:
       seata:
         tx-service-group: my_test_tx_group

4、創建數據庫undo_log表

在每個業務庫中創建以下數據庫表,表明可以修改,修改後記得修改對應的配置

-- the table to store seata xid data
-- 0.7.0+ add context
-- you must to init this sql for you business databese. the seata server not need it.
-- 此腳本必須初始化在你當前的業務數據庫中,用於AT 模式XID記錄。與server端無關(注:業務數據庫)
-- 注意此處0.3.0+ 增加唯一索引 ux_undo_log
drop table `undo_log`;
CREATE TABLE `undo_log` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `branch_id` bigint(20) NOT NULL,
  `xid` varchar(100) NOT NULL,
  `context` varchar(128) NOT NULL,
  `rollback_info` longblob NOT NULL,
  `log_status` int(11) NOT NULL,
  `log_created` datetime NOT NULL,
  `log_modified` datetime NOT NULL,
  `ext` varchar(100) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `ux_undo_log` (`xid`,`branch_id`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;

5、將數據源交於druid自動配置(必須)

禁用Springboot的dataSources自動裝配,在啓動項添加以下配置

@SpringBootApplication(exclude = DataSourceAutoConfiguration.class)

創建dataSources數據源控制:DataSourceConfig.java

import com.alibaba.druid.pool.DruidDataSource;
import com.baomidou.mybatisplus.autoconfigure.MybatisPlusProperties;
import com.baomidou.mybatisplus.core.MybatisConfiguration;
import com.baomidou.mybatisplus.core.config.GlobalConfig;
import com.baomidou.mybatisplus.extension.injector.LogicSqlInjector;
import com.baomidou.mybatisplus.extension.plugins.PaginationInterceptor;
import com.baomidou.mybatisplus.extension.spring.MybatisSqlSessionFactoryBean;
import io.seata.rm.datasource.DataSourceProxy;
import org.apache.ibatis.logging.stdout.StdOutImpl;
import org.apache.ibatis.plugin.Interceptor;
import org.apache.ibatis.session.SqlSessionFactory;
import org.apache.ibatis.type.JdbcType;
import org.mybatis.spring.transaction.SpringManagedTransactionFactory;
import org.springframework.boot.context.properties.ConfigurationProperties;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.context.annotation.Primary;
import org.springframework.core.io.support.PathMatchingResourcePatternResolver;
import javax.sql.DataSource;

@Configuration
public class DataSourceConfig {

    @Bean
    @ConfigurationProperties(prefix = "spring.datasource")
    public DataSource druidDataSource(){
        DruidDataSource druidDataSource = new DruidDataSource();
        return druidDataSource;
    }

    @Primary
    @Bean("dataSource")
    public DataSourceProxy dataSource(DataSource druidDataSource){
        return new DataSourceProxy(druidDataSource);
    }

    @Bean
    public SqlSessionFactory sqlSessionFactory(DataSourceProxy dataSourceProxy)throws Exception{
        MybatisSqlSessionFactoryBean sqlSessionFactoryBean = new MybatisSqlSessionFactoryBean();

        // 配置mybatis-plus的分頁
        PaginationInterceptor paginationInterceptor = new PaginationInterceptor();
        Interceptor[] plugins = {paginationInterceptor};
        sqlSessionFactoryBean.setPlugins(plugins);

        sqlSessionFactoryBean.setDataSource(dataSourceProxy);
        sqlSessionFactoryBean.setMapperLocations(new PathMatchingResourcePatternResolver()
                .getResources("classpath*:/mapper/*.xml"));
        // 配置spring的本地事務
        sqlSessionFactoryBean.setTransactionFactory(new SpringManagedTransactionFactory());

        // 配置mybatis-plus的邏輯刪除
        sqlSessionFactoryBean.setGlobalConfig(new GlobalConfig().setSqlInjector(new LogicSqlInjector()));

        // 配置mybatis-plus的log打印
        MybatisConfiguration cfg = new MybatisConfiguration();
        cfg.setJdbcTypeForNull(JdbcType.NULL);
        cfg.setMapUnderscoreToCamelCase(true);
        cfg.setCacheEnabled(false);
        cfg.setLogImpl(StdOutImpl.class);
        sqlSessionFactoryBean.setConfiguration(cfg);

        return sqlSessionFactoryBean.getObject();
    }
}

編寫測試用例

準備兩個測試的微服務(cloud-iqs,cloud-usc),這裏只是測試效果用,實際根據業務需求來。

編寫controller:

@ApiOperation("test seata, flag爲1,正常提交  爲2:cloud-iqs失敗, 爲3:cloud-usc失敗")
@GetMapping("/testSeata")
public R testSeata(int flag){
    purOrderService.testSeata(flag);
    return R.ok();
}

編寫service:

// seata分佈式無使用GlobalTransactional註解
@GlobalTransactional
@Override
public void testSeata(int flag) {
    System.out.println(RootContext.getXID());
    TransExpense transExpense = new TransExpense();
    transExpense.setType("111");
    transExpenseMapper.insert(transExpense);

    // 通過fegin調用cloud-usc
    R r =  uscFeginClient.testSeata(flag);

    if(r.getCode() != 200){
        throw new RuntimeException(r.getMsg());
    }

    if(flag == 2){
        throw new RuntimeException("cloud-iqs fail");
    }
}

編寫fegin:

@GetMapping(value = "user/testSeata", consumes = MediaType.ALL_VALUE)
R testSeata(@RequestParam("flag") int flag);

編寫fegin調用的controller:

@ApiOperation(value = "testSeata")
@GetMapping(value = "testSeata")
public R testSeata(int flag){
    System.out.println("----------------------------------------------------user");
    User user = new User();
    user.setAccount(new Date().toString());
    user.setPassword("22222222222");
    userService.save(user);

    if(flag == 3){
        throw new RuntimeException("cloud-usc fail");
    }
    return R.ok();
}

測試seata分佈式事務

模擬cloud-iqs失敗

使用swagger2調用

SpringCloud江湖

查看數據庫對應表結構:

usc庫:

SpringCloud江湖

iqs庫:
SpringCloud江湖

模擬cloud-usc失敗

使用swagger2調用

SpringCloud江湖

查看數據庫對應表結構:

usc庫:

SpringCloud江湖

iqs庫:

SpringCloud江湖

模擬成功

使用swagger2調用

SpringCloud江湖

查看數據庫對應表結構:

usc庫:

SpringCloud江湖
iqs庫:

SpringCloud江湖

本文到此結束了,後續文章會陸續更新,文檔會同步在CSDN和GitHub保持同步更新。有問題請留言

CSDN:https://blog.csdn.net/qq_34988304/category_8820134.html

Github文檔:https://github.com/hack-feng/Java-Notes/tree/master/src/note/SpringCloud

GitHub源碼:https://github.com/hack-feng/Spring-Cloud-Edgware.git

發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章