Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.4.3
-
None
Description
Build tested: 1.4.3-4 docker image
The goal is to start a ColumnStore docker container, configured to use AWS S3 storage.
When starting a container, the user can do the following:
docker run -d -p 3306:3306 \
-e MARIADB_ROOT_HOST=% \
-e MARIADB_ROOT_PASSWORD=mypassword \
-e USE_S3_STORAGE=1 \
-e S3_BUCKET=your_bucket_name_here \
-e S3_ENDPOINT=your_url_here \
-e S3_ACCESS_KEY_ID=your_id_here \
-e S3_SECRET_ACCESS_KEY=your_key_here \
--name mcs_container mcs_image
There is not an option to specify the region. The storagemanager.cnf file has the region setting commented out. Even if I manually added to the file, the entry would get commented out automatically. Without the region, ColumnStore would fail with the following error in the err.log file:
[root@cb94ff67365a columnstore]# cat err.log
Mar 11 20:27:52 cb94ff67365a StorageManager[309]: S3Storage::putObject(): failed to PUT, server says 'The authorization header is malformed; a non-empty region must be provided in the credential.'. bucket = dleeqadbroot1, key = connectivity_test. Retrying...
Mar 11 20:27:57 cb94ff67365a StorageManager[309]: S3Storage::putObject(): failed to PUT, server says 'The authorization header is malformed; a non-empty region must be provided in the credential.'. bucket = dleeqadbroot1, key = connectivity_test. Retrying...
The end result is system catalog is not created and DBRM is in read-only state.