[MDEV-3625] LP:619300 - Got error 177 from storage engine - Too many active concurrent transactions Created: 2010-08-17 Updated: 2015-02-02 Resolved: 2012-10-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Philip Stoev (Inactive) | Assignee: | Michael Widenius |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | Launchpad | ||
| Attachments: |
|
| Description |
|
When executing a DML workload against Maria 5.3 with the aria storage engine, some queries fail with 1030 Got error 177 from storage engine which translates to MySQL error code 177: Too many active concurrent transactions if a breakpoint is placed at handler.cc:2788, the following backtrace is observed: #0 handler::print_error (this=0x99ee0f68, error=177, errflag=0) at handler.cc:2788 In other words, the error seems to be produced by ha_index_next_same() when called by join_read_next_same() |
| Comments |
| Comment by Philip Stoev (Inactive) [ 2010-08-18 ] |
|
Re: Got error 177 from storage engine - Too many active concurrent transactions MALLOC_CHECK_=1 perl runall-new.pl - The .yy and .sql files are located on hasky, in /home/pstoev/bug619300 |
| Comment by Oleksandr Byelkin [ 2011-12-09 ] |
|
Re: Got error 177 from storage engine - Too many active concurrent transactions |
| Comment by Rasmus Johansson (Inactive) [ 2012-02-15 ] |
|
Launchpad bug id: 619300 |
| Comment by Oleksandr Byelkin [ 2012-02-15 ] |
|
Re: Got error 177 from storage engine - Too many active concurrent transactions |