Merges two adjacent shards that are in the readwrite state. You can specify a shard ID in the request. Then, Log Service locates the adjacent shard and combines the two shards into a single shard.

Usage notes

  • The value of the Host parameter consists of a project name and a Log Service endpoint. You must specify a project in the Host parameter.
  • Each shard has an MD5 value range. and each range is a left-closed, right-open interval in the [BeginKey, EndKey) format. A shard can be in the readwrite (read and write) state or readonly (read-only) state. Log Service allows you to split and merge shards. For more information, see Shard.


OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request headers

The MergeShard operation does not have operation-specific request headers and uses only common request headers. For more information, see Common request parameters.

Request syntax

POST /logstores/{logstore}/shards/{shard}?action=merge HTTP/1.1

Request parameters

Parameter Type Position Required Example Description
project String Host Yes ali-test-project

The name of the project.

logstore String Path Yes ali-test-logstore

The name of the Logstore.

shard String Path Yes 3

The ID of the shard.

Response parameters

Parameter Type Example Description
Server String nginx

The name of the server.

Content-Type String application/json

The content type of the response body.

Content-Length String 0

The content length of the response body.

Connection String close

Indicates whether the connection is persistent. Valid values:

  • close: The connection is non-persistent. A new TCP connection is established for each HTTP request.
  • keep-alive: The connection is persistent. After a TCP connection is established, the connection remains open, and no more time or bandwidth is consumed to establish new connections.
Date String Sun, 27 May 2018 08:25:04 GMT

The time at which the response was returned.

x-log-requestid String 5B0A6B60BB6EE39764D458B5

The unique ID of the request. The ID is generated by the server.

Array of shard

The data structure of the shard.


Sample requests

POST /logstores/ali-test-logstore/shards/{shard}?action=merge HTTP/1.1

Sample success responses

JSON format

HTTP/1.1 200 OK

[ {
  "shardID" : 0,
  "status" : "readwrite",
  "inclusiveBeginKey" : "e0000000000000000000000000000000",
  "exclusiveEndKey" : "ffffffffffffffffffffffffffffffff",
  "serverIp" : "10.0.xx.x",
  "createTime" : 1453949705
}, {
  "shardID" : 1,
  "status" : "readwrite",
  "inclusiveBeginKey" : "e0000000000000000000000000000000",
  "exclusiveEndKey" : "e7000000000000000000000000000000",
  "serverIp" : "10.0.xx.x",
  "createTime" : 1453949705
}, {
  "shardID" : 2,
  "status" : "readwrite",
  "inclusiveBeginKey" : "e7000000000000000000000000000000",
  "exclusiveEndKey" : "ffffffffffffffffffffffffffffffff",
  "serverIp" : "10.0.xx.x",
  "createTime" : 1453949705
} ]

Error codes

For a list of error codes, see Service error codes.







Project does not exist.

The error message returned because the specified project does not exist.



Logstore does not exist.

The error message returned because the specified Logstore does not exist.



invalid shard id.

The error message returned because the specified shard ID is invalid.



can not merge the last shard.

The error message returned because the last shard cannot be merged.



logstore has no shard.

The error message returned because no shards exist in the specified Logstore.



Specified Server Error Message.

The error message returned because an internal server error has occurred.

For more information, see Error codes.