[MXS-599] Give signal handling an overhaul. Created: 2016-03-03  Updated: 2022-01-31  Resolved: 2022-01-31

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Johan Wikman Assignee: Johan Wikman
Resolution: Won't Do Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-2584 Race condition between startup/shutdo... Closed
Sprint: MXS-SPRINT-87

 Description   

The signal handling in MaxScale should get an overhaul. In many signal handlers things are done that really should not be done in signal handling context.

Rework things so that the signal handlers only receive the signal, and then do the real stuff in non-signal context.



 Comments   
Comment by markus makela [ 2020-10-19 ]

This might not be relevant anymore now that the MainWorker does the shutdown in MaxScale 2.5. The fatal signal handling still has lots of non-signal-safe code but this is a more complex task to solve (and probably should be a separate issue).

Comment by Johan Wikman [ 2022-01-31 ]

Lots has happened since this was created. Let's create a new more specific one if there turns out to be reason for it.

Generated at Thu Feb 08 04:00:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.