temporalio / temporalio/temporal
High frequency query mysql
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Why does temporal call mysql so frequently, calling mysql more than 2000 times in 30 seconds, and it is under no-load conditions
Will high-frequency operations cause excessive pressure on mysql?
Expected Behavior
nomral operate mysql
Actual Behavior
Data are as follows
SELECT count(user_host) as count_user,user_host from mysql.general_log group by user_host order by count_user DESC;
±-----------±--------------------------------------------+
| count_user | user_host |
±-----------±--------------------------------------------+
| 36772 | temporal[temporal] @ [10.131.136.10] |
| 2625 | n9e_hbs[n9e_hbs] @ [10.131.136.10] |
| 788 | [temporal] @ [10.131.136.10] |
| 567 | root[root] @ localhost |
| 406 | keystone[keystone] @ [10.131.136.20] |
| 306 | root[root] @ [10.131.136.10] |
| 220 | n9e_mon[n9e_mon] @ [10.131.136.10] |
| 112 | region_mgmt[region_mgmt] @ [10.131.136.10] |
| 55 | [root] @ localhost |
| 19 | skyops[skyops] @ [10.131.136.20] |
| 17 | atreus[atreus] @ [10.131.136.10] |
| 14 | skyops[skyops] @ [10.131.136.10] |
| 12 | atreus[atreus] @ [10.131.136.20] |
| 7 | [keystone] @ [10.131.136.20] |
| 3 | [skyops] @ [10.131.136.10] |
| 2 | kingcobra[kingcobra] @ [10.131.136.10] |
| 2 | [atreus] @ [10.131.136.20] |
| 2 | [atreus] @ [10.131.136.10] |
| 1 | [kingcobra] @ [10.131.136.10] |
| 1 | [skyops] @ [10.131.136.20] |
±-----------±--------------------------------------------+
Steps to Reproduce the Problem
SELECT count(user_host) as count_user,user_host from mysql.general_log group by user_host order by count_user DESC;
Specifications
- Version: docker build 1.18.0
- Platform:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing the reported query-frequency measurement with the Docker 1.18.0 build and inspect mysql.general_log for the Temporal entries. Done means identifying the source of the high-frequency queries, determining whether the behavior is expected, and documenting the resulting impact or required change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, mysql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100