[MCOL-4867] DMLProc failed to rollback a txn Created: 2021-09-16  Updated: 2022-06-24  Resolved: 2022-06-24

Status: Closed
Project: MariaDB ColumnStore
Component/s: DMLProc
Affects Version/s: 5.6.2
Fix Version/s: 6.4.1

Type: Task Priority: Major
Reporter: Roman Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MCOL-5105 Reduced systemd timeouts results in c... Closed
Relates
relates to MCOL-4775 DMLproc is unable to complete a rollb... Closed

 Description   

One of the clients has an issue when DMLProc can't rollback the txn

DMLProc[15934]: 41.036025 |0|0|0| I 20 CAL0002: DMLProc starts rollbackAll. 
DMLProc[15934]: 41.074573 |0|0|0| I 20 CAL0002: DMLProc will rollback 1 tables. 
DMLProc[15934]: 41.074667 |0|0|0| I 20 CAL0002: DMLProc is rolling back transaction 77599 
ddlpackageproc[15931]: 41.104014 |0|0|0| C 23 CAL0008: Timer expired

There are two points. The first one DMLProc rollbacks after two minutes of TO somewhere in dmlpackageproc code. The second is that last message uses an incorrect facilityid so that DMLProc sends the message to syslog as ddlpackageproc.

 Comments   
Comment by Rick Pizzi [ 2021-09-16 ]

drrtuy I don't think what you wrote is correct. It looks like DMLProc and ddlpackageproc are two different processes (they have different PID numbers), and the latter sends a SIGTERM to the former (this is seen in systemd logs)...

Comment by Roman [ 2021-09-16 ]

Good point but I asked you in Slack what is the process that has 15931 pid.

Comment by Rick Pizzi [ 2021-09-16 ]

The process is no longer there after DMLproc is killed, so I have no idea.
Should have tried with a "ps" loop but then the issue changed to just erroring out.
If it will repeat I'll try to catch what the offending PID's process name is.

Comment by David Hall (Inactive) [ 2022-06-24 ]

Duplicates MCOL-5105

Generated at Thu Feb 08 02:53:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.