[MDEV-16399] Spider Crashes Server After Multiple INSERT SELECTS Created: 2018-06-05 Updated: 2019-04-30 Resolved: 2019-04-30 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Spider |
| Affects Version/s: | 10.3.7 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Adam Hilton | Assignee: | Kentoku Shiba (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows Server 2012 R2 64-bit |
||
| Description |
|
We use php to iterate through what we call PointIDs under SiteIDs to generate a sub-sampled table called `trendrecord_extract` (InnoDB) from a spider table called tr. In 10.2.14 this query worked fine completing all necessary iterations SiteIDs and PointIDs without a problem. In 10.3.7 the query now results in a server crash consistently part-way through the php loop resulting in the following error log output. To be clear, the queries we sending from php will iterate through specific SiteID and PointID combinations utilizing the same connection and be fine for the first couple iterations and then consistently crash; we had no such issue in 10.2.14. There is no specific SiteID-PointID combination that results in the crash. The following query that appears in the error below was executed fine after the server was brought back online.
|
| Comments |
| Comment by Kentoku Shiba (Inactive) [ 2019-04-29 ] |
|
adamh |
| Comment by Adam Hilton [ 2019-04-29 ] |
|
I do not. The only thing unique about this operation, compared to others that we routinely do, was the fact that it was INSERT-SELECT happening in quick succession by the same connection. We have been in 10.2 since running into this issue. I still wouldn't call this repeatable though, so you're welcome to close this issue for now. I'll re-open it if/when we move to 10.3 and experience it again. - Thanks |
| Comment by Kentoku Shiba (Inactive) [ 2019-04-30 ] |
|
Thanks. It's closed for now. Please reopen when it is reproduce. |