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

Inproved redo log management

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      Solution 1

      innodb_redo_log_file_size_extend_on_startup = 0 | 1 | 2: 0 default

      1 auto_rezise
      Instead of Shutdown in case of wrong redo log size rename ib_logfiles to ib_logfiles.timestamp.old

      2 ignore_configuration

      Ignore configuration parameter and start the server with the size of the existing redo log file

      A sub task could be to check if the redo log are purged before creating them if not start innodb on the old redolog and start to apply change before creating the new redo logs

      Solution 2
      innodb_redo_log_file_max_size
      innodb_redo_log_file_auto_extend

      Like in MSSQL or Sybase the redo logs are not fixed in size and can grow to adapt for big transactions, this task would enable this as we monitor the redolog pointer we extend the redo log file size

      Attachments

        Activity

          People

            Unassigned Unassigned
            stephane@skysql.com VAROQUI Stephane
            Votes:
            3 Vote for this issue
            Watchers:
            6 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.