Details
-
Task
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.1.7-1, 10.1.7-2, 10.1.8-1, 10.1.8-3
Description
Supporting socket activation would make each of the following possible for admins:
- Cleaner restarts (the listener socket stays open persistently)
- Network namespace isolation, disallowing any network access beyond the inherited listener port (and connections accepted from it).
- Lazy startup for densely hosted instances. (It's also possible with socket activation to start it eagerly, as usual.)
- Running MariaDB on privileged ports without having to start it initially as root
- Non-racy startup for services (like a PHP site) that depend on connecting to MariaDB. Because systemd opens listener sockets early in boot, they're available even while MariaDB is starting
- Deeper integration into coming network support in future systemd releases
Some examples in C are here:
http://0pointer.de/blog/projects/socket-activation.html
I am willing to sponsor development of this feature.
Attachments
Issue Links
- includes
-
MDEV-4606 cmake build to be able to choose sysvinit or systemd (or other) init files
- Closed
- is blocked by
-
MDEV-427 Provide a systemd script for MariaDB
- Closed
- relates to
-
MDEV-5713 RFE: Add support for systemd notify feature
- Closed
-
MDEV-25233 Review shutdown patterns in systemd service units
- Open
-
MDEV-25282 Auto-shutdown on idle when socket-activated
- Stalled
-
MDEV-6347 Build RHEL7 packages
- Closed
-
MDEV-6536 make --bind=hostname to listen on both IPv6 and IPv4 addresses
- Closed
- links to