`useConfigs=maxPerformance` causes transactions to fail to commit

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: useConfigs=maxPerformance 导致事务无法提交

| username: tidb狂热爱好者

The useConfigs=maxPerformance will include a set of configurations:


After setting it, the development feedback indicates that transactions cannot be used. Even the simplest transactions cannot be committed, not nested transactions.
Please help analyze the reason.

【TiDB Usage Environment】Production, Testing, Research
【TiDB Version】
【Encountered Problem】
【Reproduction Path】What operations were performed to encounter the problem
【Problem Phenomenon and Impact】


Please provide the version information of each component, such as cdc/tikv, which can be obtained by executing cdc version/tikv-server --version.

| username: xfworld | Original post link

What is the error?

| username: tidb狂热爱好者 | Original post link

The SQL containing transactions cannot be committed or rolled back. To be precise, transactions are no longer supported.

| username: xfworld | Original post link

If using the MySQL client to perform the same SQL processing, is it also unable to commit or rollback?

| username: tidb狂热爱好者 | Original post link

I’ll give it a try.

| username: jansu-dev | Original post link

  1. For JDBC parameter issues, please refer to PingCAP’s official best practices → 开发 Java 应用使用 TiDB 的最佳实践 | PingCAP 文档中心
  2. Are there any anomalies in the tidb.log?
  3. If there are no anomalies in the tidb.log, please provide a reproducible model for troubleshooting and analysis.
| username: tidb狂热爱好者 | Original post link

Okay, I will check the reason.

| username: buddyyuan | Original post link

Check the TiDB logs, there might be some frameworks sending special statements.

| username: tidb狂热爱好者 | Original post link

Okay, let me take a look.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.