This topic describes common questions and solutions in object storage management.
How do I rotate the AccessKey (AK) and SecretKey (SK) for object storage?
The method for rotating an AK/SK depends on the credential holder. Select the corresponding management path:
- Update the credentials for the OBServer process to access object storage: The OBServer process has two types of object storage access credentials, both of which are updated by executing
ALTER SYSTEMstatements:- Data storage access credentials: Updated by executing the
ALTER SYSTEM CHANGE SHARED_STORAGE_DESTstatement. - Log storage access credentials: Updated by modifying the
logservice_access_pointparameter. - For more information, see Update object storage access credentials.
- Data storage access credentials: Updated by executing the
- Update the credentials for LogService to access object storage: Rotate the credentials by using the
ls_ctrl rotate-akcommand. For more information, see Rotate LogService access credentials.
When does the old AK become invalid after modifying the object storage AK/SK?
After the cluster is replaced with a new AK, the old AK is not immediately removed from the cluster. You must wait at least one hour before deleting the old AK.
What should I do if adding object storage fails?
Adding object storage may fail for the following reasons:
- Object storage service unreachable: Check network connectivity and confirm the Endpoint address is correct.
- Insufficient AK/SK permissions: Ensure the AK/SK has the necessary permissions to access object storage.
- Unsupported object storage type: Currently, only object storages compatible with the S3 protocol (such as Alibaba Cloud OSS and Huawei Cloud OBS) and the Azure Blob protocol are supported.
How do I monitor I/O bandwidth usage for object storage?
You can view the GV$OB_SHARED_STORAGE_QUOTA view to understand I/O access resource information for object storage.
Can I modify the object storage bucket associated with a cluster?
No. The object storage buckets for data storage and log storage are specified only when a cluster is created and cannot be modified while the cluster is running. You must ensure that the configured object storage buckets remain valid throughout the lifecycle of the cluster, including the bucket existence status and access permissions. If a bucket is deleted, its access permissions change, or its credentials expire, the cluster cannot read or write data normally, which directly affects the normal operation of the cluster.