Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-427

Provide a systemd script for MariaDB

        Details

        • Type: Task
        • Status: In Review
        • Priority: Critical
        • Resolution: Unresolved
        • Fix Version/s: 10.1
        • Component/s: None
        • Labels:
        • Sprint:
          10.1.7-1, 10.1.7-2, 10.1.8-1, 10.1.8-3, 10.1.8-4

          Description

          MySQL doesn't provide a systemd (http://www.freedesktop.org/wiki/Software/systemd/) script and thus distributions that are shipping systemd have to provide their own. Not many like this. So should we provide one inside the MariaDB package to be better for distributions than MySQL?

          Some references:

            Gliffy Diagrams

              Attachments

                Issue Links

                blocks

                Bug - A problem which impairs or prevents the functions of the product. MDEV-7752 There is no bootstrap command option for MariaDB Galera Cluster in CentOS 7

                • Major - Major loss of function.
                • Open

                Task - A task that needs to be done. MDEV-5536 Support systemd socket activation

                • Critical - Crashes, loss of data, severe memory leak.
                • In Review

                Task - A task that needs to be done. MDEV-4606 cmake build to be able to choose sysvinit or systemd (or other) init files

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed
                includes

                Bug - A problem which impairs or prevents the functions of the product. MDEV-7694 MariaDB - mysqld cannot start when restarting from systemd

                • Major - Major loss of function.
                • Closed
                relates to

                Task - A task that needs to be done. MDEV-5713 RFE: Add support for systemd notify feature

                • Major - Major loss of function.
                • In Review

                Task - A task that needs to be done. MDEV-6347 Build RHEL7 packages

                • Critical - Crashes, loss of data, severe memory leak.
                • Closed

                  Activity

                  Ascending order - Click to sort in descending order
                  15 older comments
                  Hide
                  Permalink
                  danblack Daniel Black added a comment -

                  Nils Meyer - MDEV-7752 - focuses on Centos7 however something might be applicable for you.

                  Show
                  danblack Daniel Black added a comment - Nils Meyer - MDEV-7752 - focuses on Centos7 however something might be applicable for you.
                  Hide
                  Permalink
                  roidelapluie Julien Pivotto added a comment -

                  would it be possible to ship that for 10.0 as well?

                  Show
                  roidelapluie Julien Pivotto added a comment - would it be possible to ship that for 10.0 as well?
                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment - - edited

                  We'd love to. But as it turned out, users don't like when we add new dependencies to our packages in a GA branch (yes, we've tried). And in these patches MariaDB is linked with libsystemd-daemon.so, so we'll have to add it as a dependency. We cannot do that. I see few options for 10.0:

                  • add the patch nevertheless, but build our packages without systemd. Users would need to compile MariaDB to get systemd support.
                  • bundle libsystemd-daemon sources with 10.0
                  • only implement a minimal systemd support in 10.0 that doesn't require changes in the server

                  What do you think we should do?

                  Either way, I think we'll add systemd support in 10.1 first and then, possibly, backport parts of it to 10.0

                  Show
                  serg Sergei Golubchik added a comment - - edited We'd love to. But as it turned out, users don't like when we add new dependencies to our packages in a GA branch (yes, we've tried). And in these patches MariaDB is linked with libsystemd-daemon.so , so we'll have to add it as a dependency. We cannot do that. I see few options for 10.0: add the patch nevertheless, but build our packages without systemd. Users would need to compile MariaDB to get systemd support. bundle libsystemd-daemon sources with 10.0 only implement a minimal systemd support in 10.0 that doesn't require changes in the server What do you think we should do? Either way, I think we'll add systemd support in 10.1 first and then, possibly, backport parts of it to 10.0
                  Hide
                  Permalink
                  tanj Guillaume Lefranc added a comment -

                  Sergei,

                  I would suggest the third choice, aka minimal systemd support. This is the less intrusive, and to be honest, most people just need minimal support.
                  Let's keep the systemd socket activation for 10.1 as it introduces major changes.

                  Regards,
                  Guillaume

                  Show
                  tanj Guillaume Lefranc added a comment - Sergei, I would suggest the third choice, aka minimal systemd support. This is the less intrusive, and to be honest, most people just need minimal support. Let's keep the systemd socket activation for 10.1 as it introduces major changes. Regards, Guillaume
                  Hide
                  Permalink
                  otto Otto Kekäläinen added a comment -

                  I agree with Sergei Golubchik about being conservative in GA branches. Add well documented systemd scripts to 10.1 and downstream packagers can then choose themselves if they want to take the risk of backporting it somewhere, e.g. to new OS/Linux distro releases.

                  Show
                  otto Otto Kekäläinen added a comment - I agree with Sergei Golubchik about being conservative in GA branches. Add well documented systemd scripts to 10.1 and downstream packagers can then choose themselves if they want to take the risk of backporting it somewhere, e.g. to new OS/Linux distro releases.

                    People

                    • Assignee:
                      svoj Sergey Vojtovich
                      Reporter:
                      colin Colin Charles
                    • Votes:
                      11 Vote for this issue
                      Watchers:
                      19 Start watching this issue

                      Dates

                      • Created:
                        Updated:

                        Agile