[MDEV-27283] MariaDB S3 storgae - MinIO (Couldn't resolve host name) Created: 2021-12-16  Updated: 2023-01-09

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - S3
Affects Version/s: 10.6.5
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Szabolcs Hegedus Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: MinIO,, S3, storge
Environment:

OS: Debian GNU/Linux 10
MariaDB:

  • mariadb-server-10.6 - 1:10.6.5+maria~buster
  • mariadb-plugin-s3 1:10.6.5+maria~buster


 Description   

I have MinIO S3 storage
Hostname: staging.s3.example.com

MariaDB S3 config:

s3.cnf

[mariadbd]

plugin-maturity = alpha
plugin-load-add = ha_s3
s3=ON
s3-host-name=staging.s3.example.com
s3-protocol-version = Original
s3-bucket=databases-on-object-storage
s3-access-key=mariadb
s3-secret-key=xxxxxxx
s3-region=test-central-1
s3-use-http=OFF
s3-protocol-version=Original

[aria_s3_copy]
s3-host-name=staging.s3.example.com
s3-protocol-version = Original
s3-bucket=databases-on-object-storage
s3-access-key=mariadb
s3-secret-key=xxxxxxx
s3-region=test-central-1
s3-port=80
s3-use-http=ON
s3-protocol-version=Original
verbose=1
op=to

When I try to run the aria_s3_copy test I get the following result:

Command:
aria_s3_copy --force --op=to --database=test --compress --verbose --s3_debug=true --s3_block_size=4M s3_test
Result:
aria_s3_copy: Got error from put_object(test/s3_test/frm): 5 Couldn't resolve host name

Error source:

[libmarias3] /home/buildbot/buildbot/build/mariadb-10.6.5/storage/maria/libmarias3/src/request.c:127 URI: *http://databases-on-object-storage.staging.s3.example.com/test/s3_test/aria*
[libmarias3] /home/buildbot/buildbot/build/mariadb-10.6.5/storage/maria/libmarias3/src/request.c:388 Signature data1: HEAD

[libmarias3] /home/buildbot/buildbot/build/mariadb-10.6.5/storage/maria/libmarias3/src/request.c:605 Header: host:databases-on-object-storage.storage.staging.s3.example.com

Same result when I am trying the *ALTER TABLE old_table ENGINE=S3 *command.

How can it be used the path style?

Example:
https://staging.s3.example.com/databases-on-object-storage

 Comments   
Comment by Daniel Warner [ 2023-01-09 ]

I'm experiencing the same issue. I'm not using Minio or AWS, but another S3 compatible object store and am unable to use the s3 storage engine because our provider does not provide TLS for virtual-hosted style s3 urls. An option to use path-style in the config would be ideal for us, but since this is all within a private cloud, we would also find it useful to disable TLS checking which may allow us to resolve the issue or at least test a bit more. I'm not much of a developer, but it seems like it would be possible to expose the Curl Library's CURLOPT_SSL_VERIFYPEER option as a configurable.

Just thought I'd add to the Jira. Thank you.

Generated at Thu Feb 08 09:51:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.