[MCOL-3748] Fix fatalHandler usage Created: 2020-01-29  Updated: 2020-03-13  Resolved: 2020-02-12

Status: Closed
Project: MariaDB ColumnStore
Component/s: Storage Manager
Affects Version/s: 1.4.2
Fix Version/s: 1.4.3

Type: Bug Priority: Blocker
Reporter: Patrick LeBlanc (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2020-2

 Description   

fatalHandler() deliberately kills the process using it, need to write a version of it that doesn't do that to use in SM. I think, on all fatal signals, SM has to attempt a shutdown before dying.



 Comments   
Comment by Ben Thompson (Inactive) [ 2020-02-12 ]

To test send various signals with TERM default action (i.e. SIGHUP, SIGINT, SIGTERM). This should result in StorageManager logging a clean shutdown. Finishing with the log line StorageManager Shutdown Complete.

Before these were calling a function that killed the program and dumped a trace file before the shutdown could complete.

Comment by Daniel Lee (Inactive) [ 2020-02-12 ]

Build verified: 1.4.3-1 source
server
commit cbfa2cfc48da12a13957d06c59e6a7651b77aa6a
engine
commit cf668897eff4395cc929abffb0cd87df0305c88b

verified shutdown message in debug.log file.

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