Shardingsphere-JDBC5.0.0 + seata1.4.2 Distributed transaction cannot delete undo_log #19517

110117 · 2022-07-25T05:49:34Z

Shardingsphere-JDBC version is 5.0.0
Seata version is 1.4.2

sharding.yml

spring:
  shardingsphere:
    mode:
      type: Standalone
      repository:
        type: File
        props:
          path: ${spring.application.workdir}/.shardingsphere
      overwrite: true
    datasource:
      names: master0,master0slave0,master1,master1slave0
      master0:
        type: com.alibaba.druid.pool.DruidDataSource
        driver-class-name: org.postgresql.Driver
        url: jdbc:postgresql://192.168.1.16:5432/platform-osm?stringtype=unspecified
        username: postgres
        password: postgres
      master0slave0: # only read
        type: com.alibaba.druid.pool.DruidDataSource
        driver-class-name: org.postgresql.Driver
        url: jdbc:postgresql://192.168.1.17:5432/platform?stringtype=unspecified
        username: postgres
        password: postgres
      master1:
        type: com.alibaba.druid.pool.DruidDataSource
        driver-class-name: org.postgresql.Driver
        url: jdbc:postgresql://192.168.1.18:5432/platform?stringtype=unspecified
        username: postgres
        password: postgres
      master1slave0: # only read
        type: com.alibaba.druid.pool.DruidDataSource
        driver-class-name: org.postgresql.Driver
        url: jdbc:postgresql://192.168.1.19:5432/platform?stringtype=unspecified
        username: postgres
        password: postgres
    props:
      sql-show: true
    rules:
      readwrite-splitting:
        load-balancers:
          round-robin:
            type: ROUND_ROBIN
        data-sources:
          ds-0:
            write-data-source-name: master0
            read-data-source-names: master0slave0
            load-balancer-name: round-robin
          ds-1:
            write-data-source-name: master1
            read-data-source-names: master1slave0
            load-balancer-name: round-robin
      sharding:
        key-generators:
          snowflake:
            type: SNOWFLAKE
            props:
              worker-id: ${random.int[0,1023]}
        sharding-algorithms:
          database-inline:
            type: INLINE
            props:
              algorithm-expression: ds-$->{user_id % 2}
          bill-inline:
            type: INLINE
            props:
              algorithm-expression: bill_$->{cost_id % 5}
          bill-log-inline:
            type: INLINE
            props:
              algorithm-expression: bill_log_$->{bid % 5}
        binding-tables:
          - bill,bill_state_log
        broadcast-tables: 
        #分库策略
        default-database-strategy:
          standard:
            sharding-column: user_id
            sharding-algorithm-name: database-inline
        tables:
          chain_bill:
            actual-data-nodes: ds-$->{0..1}.bill_$->{0..4}
            key-generate-strategy:
              column: bid
              key-generator-name: snowflake
            table-strategy:
              standard:
                sharding-column: cost_id
                sharding-algorithm-name: bill-inline
          chain_bill_state_log:
            actual-data-nodes: ds-$->{0..1}.bill_log_$->{0..4}
            key-generate-strategy:
              column: log_id
              key-generator-name: snowflake
            table-strategy:
              standard:
                sharding-column: bid
                sharding-algorithm-name: bill-log-inline

seata.yml

seata:
  enabled: true
  application-id: coor-test
  tx-service-group: test_tx_group  #定义事务分组
  data-source-proxy-mode: AT
  enable-auto-data-source-proxy: false
  use-jdk-proxy: false
  registry:
    type: nacos
    nacos:
      application: seata-server
      server-addr: ${spring.cloud.nacos.discovery.server-addr}
      username: ${spring.cloud.nacos.discovery.username}
      password: ${spring.cloud.nacos.discovery.password}
      namespace: ${spring.cloud.nacos.discovery.namespace}
      group: DEFAULT_GROUP
  config:
    type: file
  service:
    vgroup-mapping:
      king_tx_group: default           
    enable-degrade: false              
    disable-global-transaction: false  
  client:
    rm:
      async-commit-buffer-limit: 10000
      report-retry-count: 5
      table-meta-check-enable: false
      report-success-enable: false
      saga-branch-register-enable: false
      saga-json-parser: fastjson
      saga-retry-persist-mode-update: false
      saga-compensate-persist-mode-update: false
      lock:
        retry-interval: 10
        retry-times: 30
        retry-policy-branch-rollback-on-conflict: true
    tm:
      commit-retry-count: 5
      rollback-retry-count: 5
      default-global-transaction-timeout: 60000
      degrade-check: false
      degrade-check-period: 2000
      degrade-check-allow-times: 10
    undo:
      data-validation: true
      log-serialization: jackson
      log-table: undo_log
      only-care-update-columns: true
      compress:
        enable: true
        type: zip
        threshold: 64k
    load-balance:
      type: RandomLoadBalance
      virtual-nodes: 10
  transport:
    shutdown:
      wait: 3
    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
      worker-thread-size: default
      boss-thread-size: 1
    type: TCP
    server: NIO
    heartbeat: true
    serialization: seata
    compressor: none
    enable-client-batch-send-request: true
  log:
    exception-rate: 100

seata.conf


sharding.transaction.seata.at.enable = true  
client {
    application.id = coor-test  
    transaction.service.group = test_tx_group 
}


2022-07-24 11:41:36.857  INFO [appName=coor-test,traceId=,spanId=] io.seata.core.rpc.processor.client.RmUndoLogProcessor - rm handle undo log process:UndoLogDeleteRequest{resourceId='jdbc:postgresql://192.168.1.16:5432/postgres', saveDays=7, branchType=AT}
2022-07-24 11:41:36.858  INFO [appName=coor-test,traceId=,spanId=] io.seata.core.rpc.processor.client.RmUndoLogProcessor - rm handle undo log process:UndoLogDeleteRequest{resourceId='jdbc:postgresql://192.168.1.17:5432/postgres', saveDays=7, branchType=AT}
2022-07-24 11:41:36.861  INFO [appName=coor-test,traceId=,spanId=] io.seata.core.rpc.processor.client.RmUndoLogProcessor - rm handle undo log process:UndoLogDeleteRequest{resourceId='jdbc:postgresql://192.168.1.18:5432/postgres', saveDays=7, branchType=AT}
2022-07-24 11:41:36.861  INFO [appName=coor-test,traceId=,spanId=] io.seata.core.rpc.processor.client.RmUndoLogProcessor - rm handle undo log process:UndoLogDeleteRequest{resourceId='jdbc:postgresql://192.168.1.19:5432/postgres', saveDays=7, branchType=AT}
2022-07-24 11:41:36.881 ERROR [appName=coor-test,traceId=,spanId=] io.seata.rm.RMHandlerAT - Failed to delete expired undo_log, error:ERROR: cannot execute DELETE in a read-only transaction
org.postgresql.util.PSQLException: ERROR: cannot execute DELETE in a read-only transaction
  at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2674)
  at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2364)
  at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:354)
  at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:484)
  at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:404)
  at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:162)
  at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:130)
  at com.alibaba.druid.pool.DruidPooledPreparedStatement.executeUpdate(DruidPooledPreparedStatement.java:255)
  at io.seata.rm.datasource.undo.postgresql.PostgresqlUndoLogManager.deleteUndoLogByLogCreated(PostgresqlUndoLogManager.java:59)
  at io.seata.rm.RMHandlerAT.handle(RMHandlerAT.java:59)
  at io.seata.rm.DefaultRMHandler.handle(DefaultRMHandler.java:73)
  at io.seata.core.protocol.transaction.UndoLogDeleteRequest.handle(UndoLogDeleteRequest.java:70)
  at io.seata.rm.AbstractRMHandler.onRequest(AbstractRMHandler.java:150)
  at io.seata.core.rpc.processor.client.RmUndoLogProcessor.handleUndoLogDelete(RmUndoLogProcessor.java:56)
  at io.seata.core.rpc.processor.client.RmUndoLogProcessor.process(RmUndoLogProcessor.java:51)
  at io.seata.core.rpc.netty.AbstractNettyRemoting.lambda$processMessage$2(AbstractNettyRemoting.java:279)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
  at java.lang.Thread.run(Thread.java:748)
2022-07-24 11:41:36.881 ERROR [appName=coor-test,traceId=,spanId=] io.seata.rm.RMHandlerAT - Failed to delete expired undo_log, error:ERROR: cannot execute DELETE in a read-only transaction
org.postgresql.util.PSQLException: ERROR: cannot execute DELETE in a read-only transaction
  at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2674)
  at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2364)
  at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:354)
  at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:484)
  at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:404)
  at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:162)
  at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:130)
  at com.alibaba.druid.pool.DruidPooledPreparedStatement.executeUpdate(DruidPooledPreparedStatement.java:255)
  at io.seata.rm.datasource.undo.postgresql.PostgresqlUndoLogManager.deleteUndoLogByLogCreated(PostgresqlUndoLogManager.java:59)
  at io.seata.rm.RMHandlerAT.handle(RMHandlerAT.java:59)
  at io.seata.rm.DefaultRMHandler.handle(DefaultRMHandler.java:73)
  at io.seata.core.protocol.transaction.UndoLogDeleteRequest.handle(UndoLogDeleteRequest.java:70)
  at io.seata.rm.AbstractRMHandler.onRequest(AbstractRMHandler.java:150)
  at io.seata.core.rpc.processor.client.RmUndoLogProcessor.handleUndoLogDelete(RmUndoLogProcessor.java:56)
  at io.seata.core.rpc.processor.client.RmUndoLogProcessor.process(RmUndoLogProcessor.java:51)
  at io.seata.core.rpc.netty.AbstractNettyRemoting.lambda$processMessage$2(AbstractNettyRemoting.java:279)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
  at java.lang.Thread.run(Thread.java:748)

The text was updated successfully, but these errors were encountered:

terrymanu · 2022-07-25T09:20:10Z

No plan for seata investigate for now, I just set the issue as good amateur issue, please collect this issue if someone interest it.

110117 · 2022-07-25T09:23:19Z

Thank you for your reply

github-actions · 2022-10-08T16:06:30Z

Hello , this issue has not received a reply for several days.
This issue is supposed to be closed.

linghengqian · 2024-02-17T04:45:28Z

You have not written unit tests that expose this Error Log. I suspect you manually changed the isolation level of the transaction, which is not currently supported by the Seata integration. Refer to Bump io.seata:seata-all for testing to 2.0.0 #30146 .
Also, it seems you are using seata's spring boot starter. Using annotations such as io.seata.spring.annotation.GlobalTransactional is not allowed. Refer to SpringCloud+Seata1.5.2+ShardingSphereJDBC5.2.1 SeataATShardingSphereTransactionManager.commit throw null exception #22356 (comment) .
In Add GraalVM Reachability Metadata and corresponding nativeTest for Seata integration #30138, I did integration testing using the Docker Image of seataio/seata-server:1.8.0 and postgres:16.2-bookworm and did not see this kind of Log.

github-actions · 2024-03-28T20:06:58Z

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

linghengqian · 2024-03-28T21:03:11Z

Closed due to not being able to reproduce.

terrymanu added feature: transaction good amateur issue labels Jul 25, 2022

github-actions bot added the status: inactive label Oct 8, 2022

github-actions bot closed this as completed Oct 8, 2022

taojintianxia reopened this Oct 10, 2022

taojintianxia removed the status: inactive label Oct 10, 2022

github-actions bot added the stale label Jul 13, 2023

linghengqian mentioned this issue Feb 16, 2024

Bump io.seata:seata-all for testing to 2.0.0 #30146

Merged

6 tasks

linghengqian added status: need more info and removed stale labels Feb 17, 2024

github-actions bot added the stale label Mar 28, 2024

linghengqian self-assigned this Mar 28, 2024

linghengqian closed this as completed Mar 28, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Shardingsphere-JDBC5.0.0 + seata1.4.2 Distributed transaction cannot delete undo_log #19517

Shardingsphere-JDBC5.0.0 + seata1.4.2 Distributed transaction cannot delete undo_log #19517

110117 commented Jul 25, 2022

terrymanu commented Jul 25, 2022

110117 commented Jul 25, 2022

github-actions bot commented Oct 8, 2022

linghengqian commented Feb 17, 2024 •

edited

Loading

github-actions bot commented Mar 28, 2024

linghengqian commented Mar 28, 2024

Shardingsphere-JDBC5.0.0 + seata1.4.2 Distributed transaction cannot delete undo_log #19517

Shardingsphere-JDBC5.0.0 + seata1.4.2 Distributed transaction cannot delete undo_log #19517

Comments

110117 commented Jul 25, 2022

terrymanu commented Jul 25, 2022

110117 commented Jul 25, 2022

github-actions bot commented Oct 8, 2022

linghengqian commented Feb 17, 2024 • edited Loading

github-actions bot commented Mar 28, 2024

linghengqian commented Mar 28, 2024

linghengqian commented Feb 17, 2024 •

edited

Loading