[MCOL-1694] Add better logging for uncaught exceptions in DDLProc/DMLProc Created: 2018-09-05  Updated: 2019-01-02  Resolved: 2019-01-02

Status: Closed
Project: MariaDB ColumnStore
Component/s: DDLProc, DMLProc
Affects Version/s: None
Fix Version/s: 1.1.7

Type: Bug Priority: Major
Reporter: Andrew Hutchings (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
Sprint: 2018-17, 2018-18, 2018-19, 2018-20, 2018-21

 Description   

DMLProc and DDLProc will both silently end if exceptions are caught in the initialisation phase and some other places in the execution. The following needs to be fixed:

  • Exceptions at the end of ddlproc.cpp need to be logged
  • Exceptions in DMLServer::start() need to be logged
  • Need to check if there are other failure scenarios in these processes that are not logged

 Comments   
Comment by Andrew Hutchings (Inactive) [ 2018-09-07 ]

Exceptions are now logged and process termination happens correctly where appropriate.

Please do not merge until after 1.1.6 is released.

For QA: cannot test this without a either a bad installation or hacking OAM to throw exceptions. Recommend just checking for regressions.

Comment by Daniel Lee (Inactive) [ 2019-01-02 ]

Build verified: 1.1.7-1

Git Commits
server=8220579
engine=88da1b6
Regression passed. Currently there are two regression cases failed, but they are not related to this.

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