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

Test S3 Storage engine

    XMLWordPrintable

Details

    Description

      To test S3 Storage engine the following main steps should be performed:

      1. Install libcurl and libxml2-devel libs.
      2. Build MariaDB from the `maria-s3` repository in the mariadb server repo.
      3. Run mysql-test/mtr-aws for `s3` suite.
      4. Run `s3.no_s3` as usual mtr.

      Additional tasks:

      • Create more tests for s3.
      • Do test with big tables.
      • Run complex queries with join with 2,3,4 tables.
      • Do self joins.
      • Test replication when table is created in s3 and data is read from s3. In this case the data is 'shared' so the slave should just instantiate the table, not create it.

      Attachments

        Issue Links

          relates to

          Technical task - A technical task. MDEV-19461 Assertion failure upon altering temporary S3 table

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20834 Engine cannot be altered to S3 from MyISAM for a 110Gb table.

          • Major - Major loss of function.
          • Stalled

          Task - A task that needs to be done. MDEV-22606 Include the S3 storage engine in MariaDB Community Server binary packages

          • Major - Major loss of function.
          • Closed

          Technical task - A technical task. MDEV-19463 Altering sequence to S3 leaves unremovable garbage behind

          • Major - Major loss of function.
          • Closed

          Technical task - A technical task. MDEV-19464 Altering partitioned table into S3 causes an obscure error

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Technical task - A technical task. MDEV-19465 Server crashes in s3_block_read upon IN query

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

          Technical task - A technical task. MDEV-19466 Syntax error in the error message: Expected object ... didn't exists

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Technical task - A technical task. MDEV-19575 Assertion `page_st == 1' failed upon SELECT from S3 table which is being converted into Aria

          • Major - Major loss of function.
          • Closed

          Technical task - A technical task. MDEV-19585 Assertion `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())' failed upon SELECT from S3 table with concurrent BACKUP stage

          • Major - Major loss of function.
          • Closed

          Technical task - A technical task. MDEV-19591 Assertion `!table->pos_in_locked_tables' failed in tc_release_table upon altering table into S3 under lock

          • Major - Major loss of function.
          • Closed

          Activity

            People

              elenst Elena Stepanova
              stepan.patryshev Stepan Patryshev (Inactive)
              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.