mirror of
https://github.com/minio/minio.git
synced 2025-01-13 16:03:21 -05:00
556a51120c
No locks are ever left in memory, we also have a periodic interval of clearing stale locks anyways. The lock instrumentation was not complete and was seldom used. Deprecate this for now and bring it back later if it is really needed. This also in-turn seems to improve performance slightly. |
||
---|---|---|
.. | ||
README.md |
管理REST API
认证
- AWS signatureV4
- 我们使用
minio
作为区域。 这里区域仅用于签名计算。
##管理接口
-
Service
- Restart
- Status
- SetCredentials
-
Locks
- List
- Clear
-
Healing
服务管理接口
-
Restart
- POST /?service
- x-minio-operation: restart
- Response: On success 200
-
Status
- GET /?service
- x-minio-operation: status
- Response: On success 200, return json formatted object which contains StorageInfo and ServerVersion structures
-
SetCredentials
- GET /?service
- x-minio-operation: set-credentials
- Response: Success 200
- Possible error responses
- ErrMethodNotAllowed
<Error> <Code>MethodNotAllowed</Code> <Message>The specified method is not allowed against this resource.</Message> <Key></Key> <BucketName></BucketName> <Resource>/</Resource> <RequestId>3L137</RequestId> <HostId>3L137</HostId> </Error>
- ErrAdminBadCred
<Error> <Code>XMinioBadCred</Code> <Message>XMinioBadCred</Message> <Key></Key> <BucketName></BucketName> <Resource>/</Resource> <RequestId>3L137</RequestId> <HostId>3L137</HostId> </Error>
- ErrInternalError
<Error> <Code>InternalError</Code> <Message>We encountered an internal error, please try again.</Message> <Key></Key> <BucketName></BucketName> <Resource>/</Resource> <RequestId>3L137</RequestId> <HostId>3L137</HostId> </Error>
修复
- ListBucketsHeal
- GET /?heal
- x-minio-operation: list-buckets