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

No warning is produced upon startup with incorrect values of max-total-tmp-space-usage or max-tmp-space-usage

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • N/A
    • 11.5(EOL)
    • Server
    • None

    Description

      max_tmp_space_usage and max_total_tmp_space_usage should be multiples of 64K.
      If a value is set differently at runtime, it is adjusted with a warning.

      bb-11.5-monty f551fa75e13dd57b057117c570f2e2414ec6d500

      Query OK, 0 rows affected, 1 warning (0.000 sec)
       
      MariaDB [test]> show warnings;
      +---------+------+--------------------------------------------------------------+
      | Level   | Code | Message                                                      |
      +---------+------+--------------------------------------------------------------+
      | Warning | 1292 | Truncated incorrect max_total_tmp_space_usage value: '32768' |
      +---------+------+--------------------------------------------------------------+
      1 row in set (0.000 sec)
       
      MariaDB [test]> select @@max_total_tmp_space_usage;
      +-----------------------------+
      | @@max_total_tmp_space_usage |
      +-----------------------------+
      |                           0 |
      +-----------------------------+
      1 row in set (0.001 sec)
       
      MariaDB [test]> set global max_total_tmp_space_usage= 100*1024;
      Query OK, 0 rows affected, 1 warning (0.000 sec)
       
      MariaDB [test]> show warnings;
      +---------+------+---------------------------------------------------------------+
      | Level   | Code | Message                                                       |
      +---------+------+---------------------------------------------------------------+
      | Warning | 1292 | Truncated incorrect max_total_tmp_space_usage value: '102400' |
      +---------+------+---------------------------------------------------------------+
      1 row in set (0.000 sec)
       
      MariaDB [test]> select @@max_total_tmp_space_usage;
      +-----------------------------+
      | @@max_total_tmp_space_usage |
      +-----------------------------+
      |                       65536 |
      +-----------------------------+
      1 row in set (0.001 sec)
      

      However, if it's set incorrectly upon startup, the server adjusts it without any warnings in the log/stderr.
      It can lead to unnoticed configuration mistakes, e.g. if somebody sets it to 8 instead of 8G and ends up with no limit at all as it's adjusted to 0.

      Attachments

        Issue Links

          Activity

            People

              monty Michael Widenius
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.