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

TokuDB is unable to be built on Linux

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 10.1.30, 10.2.11
    • 10.1.30, 10.2.12, 10.3.3
    • Storage Engine - TokuDB
    • None
    • Linux, OpenBSD, and everything that doesn't implement both F_NOCACHE and O_DIRECT at the same time.
    • 10.1.30

    Description

      In the commit https://github.com/MariaDB/server/commit/685db2c112b9d5d59a78835d444e23cf754cda7f, CMakeLists.txt was changed such that F_NOCACHE is required as an early check for TokuDB.

      F_NOCACHE does not exist on Linux which makes TokuDB inaccessible.

      Please revert or update the storage/tokudb/CMakeLists.txt part of this commit

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14537 TokuDB not recognized for compilation

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14532 apt upgrade fails on TokuDB

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14534 Tokudb stopped working after automatic update

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            People

              sanja Oleksandr Byelkin
              grknight Brian Evans
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.