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

On startup please make MariaDB report it's version number

    Details

      Description

      This may seem really silly but MySQL starts up but doesn't as the first thing that it does report it's version number. If starting up normally the startup time is pretty short so you'll later see this reported once it's listening for connections.

      If the startup takes time, for example on recovery from a crash, you can not be sure which version is actually running.

      A recently lockup triggered me to kill -9 <mysqld_pid> and then upgrade the binaries. I couldn't check from logging for the first 20 minutes if the new binary was the one I expected to be running.

      It's trivial to do this so please make MariaDB report its version number as one of the very first things that it does. Then there's never any confusion.

      [root@myhost ~]# /etc/init.d/mysql  start
      Starting MySQL.141015 10:03:57 mysqld_safe Starting mysqld_wrapper daemon with databases from /path/to/datadir
      ...........................141015 10:04:25 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      141015 10:04:25 [Note] InnoDB: The InnoDB memory heap is disabled
      141015 10:04:25 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      141015 10:04:25 [Note] InnoDB: Memory barrier is not used
      141015 10:04:25 [Note] InnoDB: Compressed tables use zlib 1.2.3
      141015 10:04:25 [Note] InnoDB: Using Linux native AIO
      141015 10:04:25 [Note] InnoDB: Using CPU crc32 instructions
      141015 10:04:25 [Note] InnoDB: Initializing buffer pool, size = 225.0G
      ...........141015 10:04:36 [Note] InnoDB: Completed initialization of buffer pool
      ...141015 10:04:39 [Note] InnoDB: Highest supported file format is Barracuda.
      141015 10:04:39 [Note] InnoDB: Log scan progressed past the checkpoint lsn 250094936720745
      141015 10:04:39 [Note] InnoDB: Database was not shutdown normally!
      141015 10:04:39 [Note] InnoDB: Starting crash recovery.
      141015 10:04:39 [Note] InnoDB: Reading tablespace information from the .ibd files...
      .......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

      Recovery is still ongoing and I still can't be sure from logging which version is actually running now.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                serg Sergei Golubchik
                Reporter:
                simon.mudd Simon J Mudd
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: