Adds one or more shares to an express synchronization group.
Operation description
When you call this operation, note the following:
Ensure that an express synchronization group is created. If not, you can call the CreateExpressSync operation to create one. The bucket for the express synchronization group must be the same as the bucket for the share.
If the share name that you specify is empty, the request is ignored.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
hcs-sgw:AddSharesToExpressSync |
update |
*All Resource
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| ExpressSyncId |
string |
Yes |
The ID of the express synchronization group. |
sync-0001xv7je357xn8tr*** |
| GatewayShares |
string |
Yes |
The names of gateway shares. You can add multiple shares. The value must be a JSON string that is in the following format: {"Gateway ID1":"Share 1,Share 2","Gateway ID2":"Share 1,Share 2"} |
{"gw-000gwgp0j3jp8cb3t***":"share1,share2","gw-0001b2otnkdzte62j***":"weekly"} |
Response parameters
|
Parameter |
Type |
Description |
Example |
|
object |
|||
| TaskId |
string |
The ID of the task. |
t-0001xv7je357xr6ql*** |
| RequestId |
string |
The ID of the request. |
1EDBC004-6B1C-4511-ACF5-0B4875BA3887 |
| Message |
string |
The description of the request result. |
successful |
| MnsTopic |
string |
The Simple Message Queue (formerly MNS) topic that is used by the express synchronization group. |
|
| MnsQueues |
string |
The Simple Message Queue (formerly MNS) queue that is used by the express synchronization group. |
|
| MnsFullSyncDelay |
integer |
The latency of the first full synchronization. Unit: seconds. |
|
| MnsPublicEndpoint |
string |
The public endpoint of Simple Message Queue (formerly MNS) that is used by the express synchronization group. |
|
| MnsInnerEndpoint |
string |
The internal endpoint of Simple Message Queue (formerly MNS) that is used by the express synchronization group. |
|
| Code |
string |
The status code. A status code of 200 indicates that the request was successful. |
200 |
| Success |
boolean |
Indicates whether the request was successful. |
true |
Examples
Success response
JSON format
{
"TaskId": "t-0001xv7je357xr6ql***",
"RequestId": "1EDBC004-6B1C-4511-ACF5-0B4875BA3887",
"Message": "successful",
"MnsTopic": "",
"MnsQueues": "",
"MnsFullSyncDelay": 0,
"MnsPublicEndpoint": "",
"MnsInnerEndpoint": "",
"Code": "200",
"Success": true
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | EmptyExpressSyncId | You must specify a valid ID for the sync group. | You must specify a valid ID for the sync group. |
| 400 | ExpressSyncNotExist | The specified sync group does not exist. You must specify a valid parameter. | The specified sync group does not exist. You must specify a valid parameter. |
| 400 | ExpressSyncInOperation | The sync group is busy. Try again later. | The sync group is busy. Try again later. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.