[MCOL-3313] update is concurrently run with a cpimport table issue Created: 2019-05-15 Updated: 2023-03-06 Resolved: 2023-03-06 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | N/A |
| Affects Version/s: | 1.2.2 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Environment: |
2um 2pm with local query |
||
| Description |
|
Reported by a customer To track an issue where when an update is concurrently run with a cpimport table, the update completes but the cpimport returns 0 rows updated when there is obviously data to load. Local query is enabled this is happening on the PM. I talk to andrew at openworks he knows about it. |
| Comments |
| Comment by David Hill (Inactive) [ 2019-05-21 ] |
|
from customer in the issue originally thought that the cpimport was failing and rolling back. Unless there is something else going on, it does not appears that it is the case. Some of the data is half imported, leaving us with data missing from pm1 while pm2 is fine and vice versa |
| Comment by David Hill (Inactive) [ 2019-05-21 ] |
|
more feedback from customer in the issue Still uncovering the issue. It looks like the update aborted also, we have 2 consecutive update statement, the last assign assign -1. This samples exhibits an abnormal high rate of -1, which indicates the first update stop,or fail , then they get assigned -1 on the second one. |