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

S3 Storage Engine should allow to specify port to connect to.

Details

    Description

      S3 Storage engine should allow to specify which port to connect to.

      This will make it easy to connect to e.g. minio, which is using port 9000 by default (See MDEV-23650 for details)

      Attachments

        Issue Links

          Activity

            psergei Sergei Petrunia added a comment - The S3 Storage engine part: https://github.com/MariaDB/server/commit/cd0e4f28fd45433e98f28933bc3ed103b34b64ac The libmarias3 part: https://github.com/mariadb-corporation/libmarias3/pull/91/files

            danblack would you be able to review this?

            psergei Sergei Petrunia added a comment - danblack would you be able to review this?
            danblack Daniel Black added a comment -

            Done. minor changes pushed to S3 tree.

            libmarias3 looks good.

            Optional enhancements:

            Do you think detecting minio and mc in the path along should start minio from the test suite?

            minio server (doesn't auto daemonize)

            mkdir -p /tmp/shared
            MINIO_ACCESS_KEY=minio MINIO_SECRET_KEY=minioadmin minio server /tmp/shared/
            

            minio client initialization / cleanup

            mc  alias set  local  http://127.0.0.1:9000  minio minioadmin
            mc mb --ignore-existing local/storage-engine
            ...
            ...
            mc rm --recursive --force  local/storage-engine
             mc admin service stop local
            

            Thanks for writing it psergey.

            danblack Daniel Black added a comment - Done. minor changes pushed to S3 tree. libmarias3 looks good. Optional enhancements: Do you think detecting minio and mc in the path along should start minio from the test suite? minio server (doesn't auto daemonize) mkdir -p /tmp/shared MINIO_ACCESS_KEY=minio MINIO_SECRET_KEY=minioadmin minio server /tmp/shared/ minio client initialization / cleanup mc alias set local http://127.0.0.1:9000 minio minioadmin mc mb --ignore-existing local/storage-engine ... ... mc rm --recursive --force local/storage-engine mc admin service stop local Thanks for writing it psergey .
            psergei Sergei Petrunia added a comment - Ok, got approval for https://github.com/mariadb-corporation/libmarias3/pull/91 .

            With the patch, I have these tests fail (both on Minio and S3)

            s3.no_s3                                 [ disabled ]  Other failure
            s3.partition                             [ disabled ]  Other failure
            s3.partition_move                        [ disabled ]  Other failure
            s3.replication_mixed                     [ disabled ]  fails
            s3.replication_partition                 [ disabled ]  Crashes
            s3.replication_stmt                      [ disabled ]  fails
            

            psergei Sergei Petrunia added a comment - With the patch, I have these tests fail (both on Minio and S3) s3.no_s3 [ disabled ] Other failure s3.partition [ disabled ] Other failure s3.partition_move [ disabled ] Other failure s3.replication_mixed [ disabled ] fails s3.replication_partition [ disabled ] Crashes s3.replication_stmt [ disabled ] fails

            bb-10.5-mdev23662

            psergei Sergei Petrunia added a comment - bb-10.5-mdev23662

            danblack, re starting Minio - I think starting/stopping minio is a good next step. We could also add logic to detect if it's present and/or get AWS credentials from the environment (or somewhere else?). Need to discuss this with those who run the CI systems.
            I think it's better to deal with this in a separate MDEV entry.

            psergei Sergei Petrunia added a comment - danblack , re starting Minio - I think starting/stopping minio is a good next step. We could also add logic to detect if it's present and/or get AWS credentials from the environment (or somewhere else?). Need to discuss this with those who run the CI systems. I think it's better to deal with this in a separate MDEV entry.

            Pushed what we've had into 10.5

            psergei Sergei Petrunia added a comment - Pushed what we've had into 10.5

            People

              psergei Sergei Petrunia
              psergei Sergei Petrunia
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.