Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gap time between queries during a transaction is calculated as part of sqlExecuteTimeout #1335

Closed
irene-coming opened this issue Aug 20, 2019 · 1 comment
Assignees
Labels
resolve problem has been fixed by developer
Milestone

Comments

@irene-coming
Copy link
Member

  • dble version:
    5.7.21-dble-9.9.9.9-f13a30c4c1af980ecdbda904700c45e166257166-20190819050701

  • preconditions :
    no

  • configs:

schema.xml



rule.xml



server.xml

        <property name="sqlExecuteTimeout">5</property>
  • steps:
    step1. query to dble:
set autocommit=0; -- success
select * from sharding_2; -- success
-- wait >5s
select * from sharding_2; -- fail
  • expect result:
    1.query success, gap time should not calculated in sqlExecuteTimeOut

  • real result:
    1.get error like:
    ERROR 1152 (HY000): Connection {DataHost[172.100.9.6:3306],Schema[db05],threadID[4233]} was closed ,reason is [Connection {DataHost[172.100.9.6:3306],Schema[db05],threadID[4233]} was closed ]

  • supplements:
    1.

@wjl1619
Copy link
Member

wjl1619 commented Nov 11, 2019

verified on version: 5.6.29-dble-9.9.9.9-641d14832fd4b53f9f534191d43d0fa2ac814d69-20191108094031

@wjl1619 wjl1619 closed this as completed Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolve problem has been fixed by developer
Projects
None yet
Development

No branches or pull requests

4 participants