Details

    Description

      When a InnoDB data file page is freed, its contents becomes garbage, and any storage allocated in the data file is wasted.

      MariaDB 10.4 introduced an InnoDB redo log record MLOG_INIT_FREE_PAGE for marking pages as freed. In MDEV-12353 (MariaDB 10.5.2), that record was replaced with FREE_PAGE. This record could be treated as no-op, or we can punch a hole for page_compressed=1 tables.

      If innodb_immediate_scrub_data_uncompressed is set, we should initialize the page with zeros. This will replace some of the non-working scrubbing logic (MDEV-8139). The scrubbing will be fixed further in MDEV-8139.

      The following parameters will be deprecated and ignored and the problematic ‘background scrubbing’ code removed:

      • innodb-background-scrub-data-uncompressed
      • innodb-background-scrub-data-compressed
      • innodb-background-scrub-data-interval
      • innodb-background-scrub-data-check-interval

      For page_compressed tables the freed page will be hole-punched

      Attachments

        Issue Links

          Activity

            marko Marko Mäkelä created issue -
            marko Marko Mäkelä made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Fix Version/s 10.5 [ 23123 ]
            Fix Version/s 10.3 [ 22126 ]
            marko Marko Mäkelä made changes -
            NRE Projects RM_105_CANDIDATE RM_104ES_CANDIDATE
            marko Marko Mäkelä made changes -
            Assignee Thirunarayanan Balathandayuthapani [ thiru ] Marko Mäkelä [ marko ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Description When a InnoDB data file page is freed, its contents becomes garbage, and any storage allocated in the data file is wasted.

            We should introduce an InnoDB redo log record for marking pages as freed. This record, say, {{MLOG_PAGE_FREE}}, could be treated as no-op, or we could elect to punch a hole, especially when the {{page_compressed=1}} option is used.

            If scrubbing is enabled, we should initialize the page with zeros. This should replace some of the non-working scrubbing logic (MDEV-8139).
            When a InnoDB data file page is freed, its contents becomes garbage, and any storage allocated in the data file is wasted.

            We should introduce an InnoDB redo log record for marking pages as freed. This record, {{MLOG_INIT_FREE_PAGE}}, could be treated as no-op, or we could elect to punch a hole, especially when the {{page_compressed=1}} option is used.

            If scrubbing is enabled, we should initialize the page with zeros. This should replace some of the non-working scrubbing logic (MDEV-8139).
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Fix Version/s 10.5 [ 23123 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Assignee Marko Mäkelä [ marko ] Thirunarayanan Balathandayuthapani [ thiru ]
            thiru Thirunarayanan Balathandayuthapani made changes -
            Status Confirmed [ 10101 ] In Progress [ 3 ]
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Fix Version/s 10.5 [ 23123 ]
            Fix Version/s 10.4 [ 22408 ]
            thiru Thirunarayanan Balathandayuthapani made changes -
            Fix Version/s 10.5.2 [ 24030 ]
            Fix Version/s 10.5 [ 23123 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -
            Description When a InnoDB data file page is freed, its contents becomes garbage, and any storage allocated in the data file is wasted.

            We should introduce an InnoDB redo log record for marking pages as freed. This record, {{MLOG_INIT_FREE_PAGE}}, could be treated as no-op, or we could elect to punch a hole, especially when the {{page_compressed=1}} option is used.

            If scrubbing is enabled, we should initialize the page with zeros. This should replace some of the non-working scrubbing logic (MDEV-8139).
            When a InnoDB data file page is freed, its contents becomes garbage, and any storage allocated in the data file is wasted.

            MariaDB 10.4 introduced an InnoDB redo log record {{MLOG_INIT_FREE_PAGE}} for marking pages as freed. In MDEV-12353 (MariaDB 10.5.2), that record was replaced with {{FREE_PAGE}}. This record could be treated as no-op, or we can punch a hole for {{page_compressed=1}} tables.

            If {{innodb_immediate_scrub_data_uncompressed}} is set, we should initialize the page with zeros. This will replace some of the non-working scrubbing logic (MDEV-8139). The scrubbing will be fixed further in MDEV-8139.

            The following parameters will be deprecated and ignored and the problematic ‘background scrubbing’ code removed:
            * innodb-background-scrub-data-uncompressed
            * innodb-background-scrub-data-compressed
            * innodb-background-scrub-data-interval
            * innodb-background-scrub-data-check-interval
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            monty Michael Widenius made changes -
            Summary Punch holes when pages are freed Avoid writing freed InnoDB pages
            monty Michael Widenius made changes -
            Description When a InnoDB data file page is freed, its contents becomes garbage, and any storage allocated in the data file is wasted.

            MariaDB 10.4 introduced an InnoDB redo log record {{MLOG_INIT_FREE_PAGE}} for marking pages as freed. In MDEV-12353 (MariaDB 10.5.2), that record was replaced with {{FREE_PAGE}}. This record could be treated as no-op, or we can punch a hole for {{page_compressed=1}} tables.

            If {{innodb_immediate_scrub_data_uncompressed}} is set, we should initialize the page with zeros. This will replace some of the non-working scrubbing logic (MDEV-8139). The scrubbing will be fixed further in MDEV-8139.

            The following parameters will be deprecated and ignored and the problematic ‘background scrubbing’ code removed:
            * innodb-background-scrub-data-uncompressed
            * innodb-background-scrub-data-compressed
            * innodb-background-scrub-data-interval
            * innodb-background-scrub-data-check-interval
            When a InnoDB data file page is freed, its contents becomes garbage, and any storage allocated in the data file is wasted.

            MariaDB 10.4 introduced an InnoDB redo log record {{MLOG_INIT_FREE_PAGE}} for marking pages as freed. In MDEV-12353 (MariaDB 10.5.2), that record was replaced with {{FREE_PAGE}}. This record could be treated as no-op, or we can punch a hole for {{page_compressed=1}} tables.

            If {{innodb_immediate_scrub_data_uncompressed}} is set, we should initialize the page with zeros. This will replace some of the non-working scrubbing logic (MDEV-8139). The scrubbing will be fixed further in MDEV-8139.

            The following parameters will be deprecated and ignored and the problematic ‘background scrubbing’ code removed:
            * innodb-background-scrub-data-uncompressed
            * innodb-background-scrub-data-compressed
            * innodb-background-scrub-data-interval
            * innodb-background-scrub-data-check-interval

            For page_compressed tables the freed page will be hole-punched
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 85945 ] MariaDB v4 [ 153930 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            thiru Thirunarayanan Balathandayuthapani made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            rob.schwyzer@mariadb.com Rob Schwyzer (Inactive) made changes -
            rob.schwyzer@mariadb.com Rob Schwyzer (Inactive) made changes -

            People

              thiru Thirunarayanan Balathandayuthapani
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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