| << Back to previous view |
|
[QB-3692] quickbuild's run build give us "Deadlock found when trying to get lock" error frequently.
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 10.0.15 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Cheolhee Jeon | Assigned To: | Robin Shen |
| Resolution: | Incomplete | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | ubuntu 16.04 LTS ( Linux (3.10.0-1127.el7.x86_64 ) / mysql 5.7.30 | ||
| Description |
|
Hello,
We've got "Deadlock" Errors on our Quickbuild server, when users are trying to run their build. I've looked forward our server's console.log file, and it saids "Deadlock found when trying to get lock". Here's the logs that I've found, below. mysql tables in use 1, locked 1 LOCK WAIT 2 lock struct(s), heap size 1136, 1 row lock(s) MySQL thread id 30, OS thread handle 139904000202496, query id 42624890 10.166.111.60 quick_admin updating /* update com.pmease.quickbuild.model.Configuration */ update QB_CONFIGURATION set QB_STATUS_DATE='2021-03-23 11:13:53.773' where QB_ID=35 *** (1) WAITING FOR THIS LOCK TO BE GRANTED: RECORD LOCKS space id 86 page no 68 n bits 80 index PRIMARY of table `QUICKBUILD`.`QB_CONFIGURATION` trx id 4568257 lock_mode X locks rec but not gap waiting Record lock, heap no 7 PHYSICAL RECORD: n_fields 53; compact format; info bits 0 So, the question is, Is there any solution exist that we can resolve this problem? I know this problem belongs to DB side, but on the other hand, this deadlock issue comes from the table that quickbuild uses. So, I'm wondering if there's any solution that you have in mind. Please let me know with joyful answer. :) Thanks, Nick. |
| Comments |
| Comment by Robin Shen [ 29/Mar/21 08:43 AM ] |
| Is this happening occasionally or consistently? Are you able to reproduce with a sample database? |
| Comment by Cheolhee Jeon [ 30/Mar/21 02:16 AM ] |
|
Hello Robin,
Thx for quick reply. Unfortunately, We can't reproduce Deadlock error on our side for now. Also, It didn't happen till now. (It happened twice on 24th, Mar.) Should I need to make test server/agent and test until I get this message? Thx. |
| Comment by Robin Shen [ 30/Mar/21 12:51 PM ] |
| Yes, set up a test server to find the reproducing procedure will help a lot. Thx! |
| Comment by Cheolhee Jeon [ 31/Mar/21 05:21 AM ] |
|
Hello Robin,
There was bit misunderstanding counting these errors.. I've just found few more same errors between 24th, Mar and 27th, Mar. Fortunately, It didn't happen anymore, till now. Anyway, I'll set up test server and trying my best for getting same error as possible. But I'm not sure it will happen soon or not. So could you kindly hold this issues till I get this error? Thx. |
| Comment by Robin Shen [ 31/Mar/21 07:06 AM ] |
| Yes, of course |
| Comment by Cheolhee Jeon [ 02/Apr/21 06:20 AM ] |
|
Hello, Robin,
We've got Deadlock error, right before an hour ago. what should I do with this error? Thx. P.S : Thx for waiting :) |
| Comment by Robin Shen [ 02/Apr/21 09:29 AM ] |
| Is the database backup running at that time? |
| Comment by Cheolhee Jeon [ 06/Apr/21 07:40 AM ] |
| sorry for late answer.. , no database's backup time is on 09:00 AM (GMT+9) |
| Comment by Robin Shen [ 06/Apr/21 11:39 PM ] |
| If you can reproduce this issue with a minimal test database, it may help a lot. |