- 1.2.1.
/
- 1.2.2.
/_active_tasks
- 1.2.3.
/_all_dbs
- 1.2.4.
/_dbs_info
- 1.2.5.
/_cluster_setup
- 1.2.6.
/_db_updates
- 1.2.7.
/_membership
- 1.2.8.
/_replicate
- 1.2.9.
/_scheduler/jobs
- 1.2.10.
/_scheduler/docs
- 1.2.11.
/_node/{node-name}
- 1.2.12.
/_node/{node-name}/_stats
- 1.2.13.
/_node/{node-name}/_prometheus
- 1.2.14.
/_node/{node-name}/_system
- 1.2.15.
/_node/{node-name}/_restart
- 1.2.16.
/_search_analyze
- 1.2.17.
/_utils
- 1.2.18.
/_up
- 1.2.19.
/_uuids
- 1.2.20.
/favicon.ico
- 1.2.21.
/_reshard
1.2.1. /
GET
/
Accessing the root of a CouchDB instance returns meta information about the instance. The response is a JSON structure containing information about the server, including a welcome message and the version of the server.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Status Codes: |
|
Request:
GET / HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 179
Content-Type: application/json
Date: Sat, 10 Aug 2013 06:33:33 GMT
Server: CouchDB (Erlang/OTP)
{
"couchdb": "Welcome",
"uuid": "85fb71bf700c17267fef77535820e371",
"vendor": {
"name": "The Apache Software Foundation",
"version": "1.3.1"
},
"version": "1.3.1"
}
1.2.2. /_active_tasks
Changed in version 2.1.0: Because of how the scheduling replicator works, continuous replication jobs could be periodically stopped and then started later. When they are not running they will not appear in the _active_tasks
endpoint
GET
/_active_tasks
List of running tasks, including the task type, name, status and process ID. The result is a JSON array of the currently running tasks, with each task being described with a single object. Depending on operation type set of response object fields might be different.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
GET /_active_tasks HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 1690
Content-Type: application/json
Date: Sat, 10 Aug 2013 06:37:31 GMT
Server: CouchDB (Erlang/OTP)
[
{
"changes_done": 64438,
"database": "mailbox",
"pid": "<0.12986.1>",
"progress": 84,
"started_on": 1376116576,
"total_changes": 76215,
"type": "database_compaction",
"updated_on": 1376116619
},
{
"changes_done": 14443,
"database": "mailbox",
"design_document": "c9753817b3ba7c674d92361f24f59b9f",
"pid": "<0.10461.3>",
"progress": 18,
"started_on": 1376116621,
"total_changes": 76215,
"type": "indexer",
"updated_on": 1376116650
},
{
"changes_done": 5454,
"database": "mailbox",
"design_document": "_design/meta",
"pid": "<0.6838.4>",
"progress": 7,
"started_on": 1376116632,
"total_changes": 76215,
"type": "indexer",
"updated_on": 1376116651
},
{
"checkpointed_source_seq": 68585,
"continuous": false,
"doc_id": null,
"doc_write_failures": 0,
"docs_read": 4524,
"docs_written": 4524,
"missing_revisions_found": 4524,
"pid": "<0.1538.5>",
"progress": 44,
"replication_id": "9bc1727d74d49d9e157e260bb8bbd1d5",
"revisions_checked": 4524,
"source": "mailbox",
"source_seq": 154419,
"started_on": 1376116644,
"target": "http://mailsrv:5984/mailbox",
"type": "replication",
"updated_on": 1376116651
}
]
1.2.3. /_all_dbs
GET
/_all_dbs
Returns a list of all the databases in the CouchDB instance.
Request Headers: | |
---|---|
| |
Query Parameters: | |
| |
Response Headers: | |
| |
Status Codes: |
|
Request:
GET /_all_dbs HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 52
Content-Type: application/json
Date: Sat, 10 Aug 2013 06:57:48 GMT
Server: CouchDB (Erlang/OTP)
[
"_users",
"contacts",
"docs",
"invoices",
"locations"
]
1.2.4. /_dbs_info
New in version 2.2.
POST
/_dbs_info
Returns information of a list of the specified databases in the CouchDB instance. This enables you to request information about multiple databases in a single request, in place of multiple GET /{db} requests.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Request JSON Object: | |
| |
Status Codes: |
|
Request:
POST /_dbs_info HTTP/1.1
Accept: application/json
Host: localhost:5984
Content-Type: application/json
{
"keys": [
"animals",
"plants"
]
}
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Type: application/json
Date: Sat, 20 Dec 2017 06:57:48 GMT
Server: CouchDB (Erlang/OTP)
[
{
"key": "animals",
"info": {
"db_name": "animals",
"update_seq": "52232",
"sizes": {
"file": 1178613587,
"external": 1713103872,
"active": 1162451555
},
"purge_seq": 0,
"doc_del_count": 0,
"doc_count": 52224,
"disk_format_version": 6,
"compact_running": false,
"cluster": {
"q": 8,
"n": 3,
"w": 2,
"r": 2
},
"instance_start_time": "0"
}
},
{
"key": "plants",
"info": {
"db_name": "plants",
"update_seq": "303",
"sizes": {
"file": 3872387,
"external": 2339,
"active": 67475
},
"purge_seq": 0,
"doc_del_count": 0,
"doc_count": 11,
"disk_format_version": 6,
"compact_running": false,
"cluster": {
"q": 8,
"n": 3,
"w": 2,
"r": 2
},
"instance_start_time": "0"
}
}
]
1.2.5. /_cluster_setup
New in version 2.0.
GET
/_cluster_setup
Returns the status of the node or cluster, per the cluster setup wizard.
Request Headers: | |
---|---|
| |
Query Parameters: | |
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
The state
returned indicates the current node or cluster state, and is one of the following:
cluster_disabled
: The current node is completely unconfigured.single_node_disabled
: The current node is configured as a single (standalone) node ([cluster] n=1
), but either does not have a server-level admin user defined, or does not have the standard system databases created. If theensure_dbs_exist
query parameter is specified, the list of databases provided overrides the default list of standard system databases.single_node_enabled
: The current node is configured as a single (standalone) node, has a server-level admin user defined, and has theensure_dbs_exist
list (explicit or default) of databases created.cluster_enabled
: The current node has[cluster] n
> 1, is not bound to127.0.0.1
and has a server-level admin user defined. However, the full set of standard system databases have not been created yet. If theensure_dbs_exist
query parameter is specified, the list of databases provided overrides the default list of standard system databases.cluster_finished
: The current node has[cluster] n
> 1, is not bound to127.0.0.1
, has a server-level admin user defined and has theensure_dbs_exist
list (explicit or default) of databases created.
Request:
GET /_cluster_setup HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
X-CouchDB-Body-Time: 0
X-Couch-Request-ID: 5c058bdd37
Server: CouchDB/2.1.0-7f17678 (Erlang OTP/17)
Date: Sun, 30 Jul 2017 06:33:18 GMT
Content-Type: application/json
Content-Length: 29
Cache-Control: must-revalidate
{"state":"cluster_enabled"}
POST
/_cluster_setup
Configure a node as a single (standalone) node, as part of a cluster, or finalise a cluster.
Request Headers: | |
---|---|
| |
Request JSON Object: | |
|
No example request/response included here. For a worked example, please see The Cluster Setup API.
1.2.6. /_db_updates
New in version 1.4.
GET
/_db_updates
Returns a list of all database events in the CouchDB instance. The existence of the _global_changes
database is required to use this endpoint.
Request Headers: | |
---|---|
| |
Query Parameters: | |
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
The results
field of database updates:
JSON Object: |
|
---|
Request:
GET /_db_updates HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Type: application/json
Date: Sat, 18 Mar 2017 19:01:35 GMT
Etag: "C1KU98Y6H0LGM7EQQYL6VSL07"
Server: CouchDB/2.0.0 (Erlang OTP/17)
Transfer-Encoding: chunked
X-Couch-Request-ID: ad87efc7ff
X-CouchDB-Body-Time: 0
{
"results":[
{"db_name":"mailbox","type":"created","seq":"1-g1AAAAFReJzLYWBg4MhgTmHgzcvPy09JdcjLz8gvLskBCjMlMiTJ____PyuDOZExFyjAnmJhkWaeaIquGIf2JAUgmWQPMiGRAZcaB5CaePxqEkBq6vGqyWMBkgwNQAqobD4h"},
{"db_name":"mailbox","type":"deleted","seq":"2-g1AAAAFReJzLYWBg4MhgTmHgzcvPy09JdcjLz8gvLskBCjMlMiTJ____PyuDOZEpFyjAnmJhkWaeaIquGIf2JAUgmWQPMiGRAZcaB5CaePxqEkBq6vGqyWMBkgwNQAqobD4hdQsg6vYTUncAou4-IXUPIOpA7ssCAIFHa60"},
],
"last_seq": "2-g1AAAAFReJzLYWBg4MhgTmHgzcvPy09JdcjLz8gvLskBCjMlMiTJ____PyuDOZEpFyjAnmJhkWaeaIquGIf2JAUgmWQPMiGRAZcaB5CaePxqEkBq6vGqyWMBkgwNQAqobD4hdQsg6vYTUncAou4-IXUPIOpA7ssCAIFHa60"
}
1.2.7. /_membership
New in version 2.0.
GET
/_membership
Displays the nodes that are part of the cluster as cluster_nodes
. The field all_nodes
displays all nodes this node knows about, including the ones that are part of the cluster. The endpoint is useful when setting up a cluster, see Node Management
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Status Codes: |
|
Request:
GET /_membership HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Type: application/json
Date: Sat, 11 Jul 2015 07:02:41 GMT
Server: CouchDB (Erlang/OTP)
Content-Length: 142
{
"all_nodes": [
"node1@127.0.0.1",
"node2@127.0.0.1",
"node3@127.0.0.1"
],
"cluster_nodes": [
"node1@127.0.0.1",
"node2@127.0.0.1",
"node3@127.0.0.1"
]
}
1.2.8. /_replicate
POST
/_replicate
Request, configure, or stop, a replication operation.
Request Headers: | |
---|---|
| |
Request JSON Object: | |
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
The specification of the replication request is controlled through the JSON content of the request. The JSON should be an object with the fields defining the source, target and other options.
The Replication history is an array of objects with following structure:
JSON Object: |
|
---|
1.2.8.1. Replication Operation
The aim of the replication is that at the end of the process, all active documents on the source database are also in the destination database and all documents that were deleted in the source databases are also deleted (if they exist) on the destination database.
Replication can be described as either push or pull replication:
Pull replication is where the
source
is the remote CouchDB instance, and thetarget
is the local database.Pull replication is the most useful solution to use if your source database has a permanent IP address, and your destination (local) database may have a dynamically assigned IP address (for example, through DHCP). This is particularly important if you are replicating to a mobile or other device from a central server.
Push replication is where the
source
is a local database, andtarget
is a remote database.
1.2.8.2. Specifying the Source and Target Database
You must use the URL specification of the CouchDB database if you want to perform replication in either of the following two situations:
- Replication with a remote database (i.e. another instance of CouchDB on the same host, or a different host)
- Replication with a database that requires authentication
For example, to request replication between a database local to the CouchDB instance to which you send the request, and a remote database you might use the following request:
POST http://couchdb:5984/_replicate HTTP/1.1
Content-Type: application/json
Accept: application/json
{
"source" : "recipes",
"target" : "http://coucdb-remote:5984/recipes",
}
In all cases, the requested databases in the source
and target
specification must exist. If they do not, an error will be returned within the JSON object:
{
"error" : "db_not_found"
"reason" : "could not open http://couchdb-remote:5984/ol1ka/",
}
You can create the target database (providing your user credentials allow it) by adding the create_target
field to the request object:
POST http://couchdb:5984/_replicate HTTP/1.1
Content-Type: application/json
Accept: application/json
{
"create_target" : true
"source" : "recipes",
"target" : "http://couchdb-remote:5984/recipes",
}
The create_target
field is not destructive. If the database already exists, the replication proceeds as normal.
1.2.8.3. Single Replication
You can request replication of a database so that the two databases can be synchronized. By default, the replication process occurs one time and synchronizes the two databases together. For example, you can request a single synchronization between two databases by supplying the source
and target
fields within the request JSON content.
POST http://couchdb:5984/_replicate HTTP/1.1
Accept: application/json
Content-Type: application/json
{
"source" : "recipes",
"target" : "recipes-snapshot",
}
In the above example, the databases recipes
and recipes-snapshot
will be synchronized. These databases are local to the CouchDB instance where the request was made. The response will be a JSON structure containing the success (or failure) of the synchronization process, and statistics about the process:
{
"ok" : true,
"history" : [
{
"docs_read" : 1000,
"session_id" : "52c2370f5027043d286daca4de247db0",
"recorded_seq" : 1000,
"end_last_seq" : 1000,
"doc_write_failures" : 0,
"start_time" : "Thu, 28 Oct 2010 10:24:13 GMT",
"start_last_seq" : 0,
"end_time" : "Thu, 28 Oct 2010 10:24:14 GMT",
"missing_checked" : 0,
"docs_written" : 1000,
"missing_found" : 1000
}
],
"session_id" : "52c2370f5027043d286daca4de247db0",
"source_last_seq" : 1000
}
1.2.8.4. Continuous Replication
Synchronization of a database with the previously noted methods happens only once, at the time the replicate request is made. To have the target database permanently replicated from the source, you must set the continuous
field of the JSON object within the request to true.
With continuous replication changes in the source database are replicated to the target database in perpetuity until you specifically request that replication ceases.
POST http://couchdb:5984/_replicate HTTP/1.1
Accept: application/json
Content-Type: application/json
{
"continuous" : true
"source" : "recipes",
"target" : "http://couchdb-remote:5984/recipes",
}
Changes will be replicated between the two databases as long as a network connection is available between the two instances.
1.2.8.5. Canceling Continuous Replication
You can cancel continuous replication by adding the cancel
field to the JSON request object and setting the value to true. Note that the structure of the request must be identical to the original for the cancellation request to be honoured. For example, if you requested continuous replication, the cancellation request must also contain the continuous
field.
For example, the replication request:
POST http://couchdb:5984/_replicate HTTP/1.1
Content-Type: application/json
Accept: application/json
{
"source" : "recipes",
"target" : "http://couchdb-remote:5984/recipes",
"create_target" : true,
"continuous" : true
}
Must be canceled using the request:
POST http://couchdb:5984/_replicate HTTP/1.1
Accept: application/json
Content-Type: application/json
{
"cancel" : true,
"continuous" : true
"create_target" : true,
"source" : "recipes",
"target" : "http://couchdb-remote:5984/recipes",
}
Requesting cancellation of a replication that does not exist results in a 404 error.
1.2.9. /_scheduler/jobs
GET
/_scheduler/jobs
List of replication jobs. Includes replications created via /_replicate endpoint as well as those created from replication documents. Does not include replications which have completed or have failed to start because replication documents were malformed. Each job description will include source and target information, replication id, a history of recent event, and a few other things.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Query Parameters: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
GET /_scheduler/jobs HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 1690
Content-Type: application/json
Date: Sat, 29 Apr 2017 05:05:16 GMT
Server: CouchDB (Erlang/OTP)
{
"jobs": [
{
"database": "_replicator",
"doc_id": "cdyno-0000001-0000003",
"history": [
{
"timestamp": "2017-04-29T05:01:37Z",
"type": "started"
},
{
"timestamp": "2017-04-29T05:01:37Z",
"type": "added"
}
],
"id": "8f5b1bd0be6f9166ccfd36fc8be8fc22+continuous",
"info": {
"changes_pending": 0,
"checkpointed_source_seq": "113-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE01ygQLsZsYGqcamiZjKcRqRxwIkGRqA1H-oSbZgk1KMLCzTDE0wdWUBAF6HJIQ",
"doc_write_failures": 0,
"docs_read": 113,
"docs_written": 113,
"missing_revisions_found": 113,
"revisions_checked": 113,
"source_seq": "113-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE01ygQLsZsYGqcamiZjKcRqRxwIkGRqA1H-oSbZgk1KMLCzTDE0wdWUBAF6HJIQ",
"through_seq": "113-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE01ygQLsZsYGqcamiZjKcRqRxwIkGRqA1H-oSbZgk1KMLCzTDE0wdWUBAF6HJIQ"
},
"node": "node1@127.0.0.1",
"pid": "<0.1850.0>",
"source": "http://myserver.com/foo",
"start_time": "2017-04-29T05:01:37Z",
"target": "http://adm:*****@localhost:15984/cdyno-0000003/",
"user": null
},
{
"database": "_replicator",
"doc_id": "cdyno-0000001-0000002",
"history": [
{
"timestamp": "2017-04-29T05:01:37Z",
"type": "started"
},
{
"timestamp": "2017-04-29T05:01:37Z",
"type": "added"
}
],
"id": "e327d79214831ca4c11550b4a453c9ba+continuous",
"info": {
"changes_pending": null,
"checkpointed_source_seq": 0,
"doc_write_failures": 0,
"docs_read": 12,
"docs_written": 12,
"missing_revisions_found": 12,
"revisions_checked": 12,
"source_seq": "12-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE1lzgQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSexgk4yMkhITjS0wdWUBADfEJBg",
"through_seq": "12-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE1lzgQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSexgk4yMkhITjS0wdWUBADfEJBg"
},
"node": "node2@127.0.0.1",
"pid": "<0.1757.0>",
"source": "http://myserver.com/foo",
"start_time": "2017-04-29T05:01:37Z",
"target": "http://adm:*****@localhost:15984/cdyno-0000002/",
"user": null
}
],
"offset": 0,
"total_rows": 2
}
1.2.10. /_scheduler/docs
Changed in version 2.1.0: Use this endpoint to monitor the state of document-based replications. Previously needed to poll both documents and _active_tasks
to get a complete state summary
Changed in version 3.0.0: In error states the “info” field switched from being a string to being an object
GET
/_scheduler/docs
List of replication document states. Includes information about all the documents, even in completed
and failed
states. For each document it returns the document ID, the database, the replication ID, source and target, and other information.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Query Parameters: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
The info
field of a scheduler doc:
JSON Object: |
|
---|
Request:
GET /_scheduler/docs HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Content-Type: application/json
Date: Sat, 29 Apr 2017 05:10:08 GMT
Server: Server: CouchDB (Erlang/OTP)
Transfer-Encoding: chunked
{
"docs": [
{
"database": "_replicator",
"doc_id": "cdyno-0000001-0000002",
"error_count": 0,
"id": "e327d79214831ca4c11550b4a453c9ba+continuous",
"info": {
"changes_pending": 15,
"checkpointed_source_seq": "60-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYEyVygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSSpgk4yMkhITjS0wdWUBAENCJEg",
"doc_write_failures": 0,
"docs_read": 67,
"docs_written": 67,
"missing_revisions_found": 67,
"revisions_checked": 67,
"source_seq": "67-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE2VygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSepgk4yMkhITjS0wdWUBAEVKJE8",
"through_seq": "67-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE2VygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSepgk4yMkhITjS0wdWUBAEVKJE8"
},
"last_updated": "2017-04-29T05:01:37Z",
"node": "node2@127.0.0.1",
"source_proxy": null,
"target_proxy": null,
"source": "http://myserver.com/foo",
"start_time": "2017-04-29T05:01:37Z",
"state": "running",
"target": "http://adm:*****@localhost:15984/cdyno-0000002/"
},
{
"database": "_replicator",
"doc_id": "cdyno-0000001-0000003",
"error_count": 0,
"id": "8f5b1bd0be6f9166ccfd36fc8be8fc22+continuous",
"info": {
"changes_pending": null,
"checkpointed_source_seq": 0,
"doc_write_failures": 0,
"docs_read": 12,
"docs_written": 12,
"missing_revisions_found": 12,
"revisions_checked": 12,
"source_seq": "12-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE1lzgQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSexgk4yMkhITjS0wdWUBADfEJBg",
"through_seq": "12-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE1lzgQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSexgk4yMkhITjS0wdWUBADfEJBg"
},
"last_updated": "2017-04-29T05:01:37Z",
"node": "node1@127.0.0.1",
"source_proxy": null,
"target_proxy": null,
"source": "http://myserver.com/foo",
"start_time": "2017-04-29T05:01:37Z",
"state": "running",
"target": "http://adm:*****@localhost:15984/cdyno-0000003/"
}
],
"offset": 0,
"total_rows": 2
}
GET
/_scheduler/docs/{replicator_db}
Get information about replication documents from a replicator database. The default replicator database is _replicator
but other replicator databases can exist if their name ends with the suffix /_replicator
.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Query Parameters: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
The info
field of a scheduler doc:
JSON Object: |
|
---|
Request:
GET /_scheduler/docs/other/_replicator HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Content-Type: application/json
Date: Sat, 29 Apr 2017 05:10:08 GMT
Server: Server: CouchDB (Erlang/OTP)
Transfer-Encoding: chunked
{
"docs": [
{
"database": "other/_replicator",
"doc_id": "cdyno-0000001-0000002",
"error_count": 0,
"id": "e327d79214831ca4c11550b4a453c9ba+continuous",
"info": {
"changes_pending": 0,
"checkpointed_source_seq": "60-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYEyVygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSSpgk4yMkhITjS0wdWUBAENCJEg",
"doc_write_failures": 0,
"docs_read": 67,
"docs_written": 67,
"missing_revisions_found": 67,
"revisions_checked": 67,
"source_seq": "67-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE2VygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSepgk4yMkhITjS0wdWUBAEVKJE8",
"through_seq": "67-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE2VygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSepgk4yMkhITjS0wdWUBAEVKJE8"
},
"last_updated": "2017-04-29T05:01:37Z",
"node": "node2@127.0.0.1",
"source_proxy": null,
"target_proxy": null,
"source": "http://myserver.com/foo",
"start_time": "2017-04-29T05:01:37Z",
"state": "running",
"target": "http://adm:*****@localhost:15984/cdyno-0000002/"
}
],
"offset": 0,
"total_rows": 1
}
GET
/_scheduler/docs/{replicator_db}/{docid}
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
The info
field of a scheduler doc:
JSON Object: |
Request: |
---|
GET /_scheduler/docs/other/_replicator/cdyno-0000001-0000002 HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Content-Type: application/json
Date: Sat, 29 Apr 2017 05:10:08 GMT
Server: Server: CouchDB (Erlang/OTP)
Transfer-Encoding: chunked
{
"database": "other/_replicator",
"doc_id": "cdyno-0000001-0000002",
"error_count": 0,
"id": "e327d79214831ca4c11550b4a453c9ba+continuous",
"info": {
"changes_pending": 0,
"checkpointed_source_seq": "60-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYEyVygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSSpgk4yMkhITjS0wdWUBAENCJEg",
"doc_write_failures": 0,
"docs_read": 67,
"docs_written": 67,
"missing_revisions_found": 67,
"revisions_checked": 67,
"source_seq": "67-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE2VygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSepgk4yMkhITjS0wdWUBAEVKJE8",
"through_seq": "67-g1AAAACTeJzLYWBgYMpgTmHgz8tPSTV0MDQy1zMAQsMckEQiQ1L9____szKYE2VygQLsBsZm5pZJJpjKcRqRxwIkGRqA1H-oSepgk4yMkhITjS0wdWUBAEVKJE8"
},
"last_updated": "2017-04-29T05:01:37Z",
"node": "node2@127.0.0.1",
"source_proxy": null,
"target_proxy": null,
"source": "http://myserver.com/foo",
"start_time": "2017-04-29T05:01:37Z",
"state": "running",
"target": "http://adm:*****@localhost:15984/cdyno-0000002/"
}
1.2.11. /_node/{node-name}
GET
/_node/{node-name}
The /_node/{node-name}
endpoint can be used to confirm the Erlang node name of the server that processes the request. This is most useful when accessing /_node/_local
to retrieve this information. Repeatedly retrieving this information for a CouchDB endpoint can be useful to determine if a CouchDB cluster is correctly proxied through a reverse load balancer.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Status Codes: |
|
Request:
GET /_node/_local HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 27
Content-Type: application/json
Date: Tue, 28 Jan 2020 19:25:51 GMT
Server: CouchDB (Erlang OTP)
X-Couch-Request-ID: 5b8db6c677
X-CouchDB-Body-Time: 0
{"name":"node1@127.0.0.1"}
1.2.12. /_node/{node-name}/_stats
GET
/_node/{node-name}/_stats
The _stats
resource returns a JSON object containing the statistics for the running server. The object is structured with top-level sections collating the statistics for a range of entries, with each individual statistic being easily identified, and the content of each statistic is self-describing.
Statistics are sampled internally on a configurable interval. When monitoring the _stats
endpoint, you need to use a polling frequency of at least twice this to observe accurate results. For example, if the interval is 10 seconds, poll _stats
at least every 5 seconds.
The literal string _local
serves as an alias for the local node name, so for all stats URLs, {node-name}
may be replaced with _local
, to interact with the local node’s statistics.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Status Codes: |
|
Request:
GET /_node/_local/_stats/couchdb/request_time HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 187
Content-Type: application/json
Date: Sat, 10 Aug 2013 11:41:11 GMT
Server: CouchDB (Erlang/OTP)
{
"value": {
"min": 0,
"max": 0,
"arithmetic_mean": 0,
"geometric_mean": 0,
"harmonic_mean": 0,
"median": 0,
"variance": 0,
"standard_deviation": 0,
"skewness": 0,
"kurtosis": 0,
"percentile": [
[
50,
0
],
[
75,
0
],
[
90,
0
],
[
95,
0
],
[
99,
0
],
[
999,
0
]
],
"histogram": [
[
0,
0
]
],
"n": 0
},
"type": "histogram",
"desc": "length of a request inside CouchDB without MochiWeb"
}
The fields provide the current, minimum and maximum, and a collection of statistical means and quantities. The quantity in each case is not defined, but the descriptions below provide sufficient detail to determine units.
Statistics are reported by ‘group’. The statistics are divided into the following top-level sections:
couch_log
: Logging subsystemcouch_replicator
: Replication scheduler and subsystemcouchdb
: Primary CouchDB database operationsfabric
: Cluster-related operationsglobal_changes
: Global changes feedmem3
: Node membership-related statisticspread
: CouchDB file-related exceptionsrexi
: Cluster internal RPC-related statistics
The type of the statistic is included in the type
field, and is one of the following:
counter
: Monotonically increasing counter, resets on restarthistogram
: Binned set of values with meaningful subdivisions. Scoped to the current collection interval.gauge
: Single numerical value that can go up and down
You can also access individual statistics by quoting the statistics sections and statistic ID as part of the URL path. For example, to get the request_time
statistics within the couchdb
section for the target node, you can use:
GET /_node/_local/_stats/couchdb/request_time HTTP/1.1
This returns an entire statistics object, as with the full request, but containing only the requested individual statistic.
1.2.13. /_node/{node-name}/_prometheus
GET
/_node/{node-name}/_prometheus
The _prometheus
resource returns a text/plain response that consolidates our /_node/{node-name}/_stats, and /_node/{node-name}/_system endpoints. The format is determined by Prometheus. The format version is 2.0.
Request:
GET /_node/_local/_prometheus HTTP/1.1
Accept: text/plain
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 187
Content-Type: text/plain; version=2.0
Date: Sat, 10 May 2020 11:41:11 GMT
Server: CouchDB (Erlang/OTP)
# TYPE couchdb_couch_log_requests_total counter
couchdb_couch_log_requests_total{level="alert"} 0
couchdb_couch_log_requests_total{level="critical"} 0
couchdb_couch_log_requests_total{level="debug"} 0
couchdb_couch_log_requests_total{level="emergency"} 0
couchdb_couch_log_requests_total{level="error"} 0
couchdb_couch_log_requests_total{level="info"} 8
couchdb_couch_log_requests_total{level="notice"} 51
couchdb_couch_log_requests_total{level="warning"} 0
# TYPE couchdb_couch_replicator_changes_manager_deaths_total counter
couchdb_couch_replicator_changes_manager_deaths_total 0
# TYPE couchdb_couch_replicator_changes_queue_deaths_total counter
couchdb_couch_replicator_changes_queue_deaths_total 0
# TYPE couchdb_couch_replicator_changes_read_failures_total counter
couchdb_couch_replicator_changes_read_failures_total 0
# TYPE couchdb_couch_replicator_changes_reader_deaths_total counter
couchdb_couch_replicator_changes_reader_deaths_total 0
# TYPE couchdb_couch_replicator_checkpoints_failure_total counter
couchdb_couch_replicator_checkpoints_failure_total 0
# TYPE couchdb_couch_replicator_checkpoints_total counter
couchdb_couch_replicator_checkpoints_total 0
# TYPE couchdb_couch_replicator_cluster_is_stable gauge
couchdb_couch_replicator_cluster_is_stable 1
# TYPE couchdb_couch_replicator_connection_acquires_total counter
couchdb_couch_replicator_connection_acquires_total 0
# TYPE couchdb_couch_replicator_connection_closes_total counter
couchdb_couch_replicator_connection_closes_total 0
# TYPE couchdb_couch_replicator_connection_creates_total counter
couchdb_couch_replicator_connection_creates_total 0
# TYPE couchdb_couch_replicator_connection_owner_crashes_total counter
couchdb_couch_replicator_connection_owner_crashes_total 0
# TYPE couchdb_couch_replicator_connection_releases_total counter
couchdb_couch_replicator_connection_releases_total 0
# TYPE couchdb_couch_replicator_connection_worker_crashes_total counter
couchdb_couch_replicator_connection_worker_crashes_total 0
# TYPE couchdb_couch_replicator_db_scans_total counter
couchdb_couch_replicator_db_scans_total 1
# TYPE couchdb_couch_replicator_docs_completed_state_updates_total counter
couchdb_couch_replicator_docs_completed_state_updates_total 0
# TYPE couchdb_couch_replicator_docs_db_changes_total counter
couchdb_couch_replicator_docs_db_changes_total 0
# TYPE couchdb_couch_replicator_docs_dbs_created_total counter
couchdb_couch_replicator_docs_dbs_created_total 0
# TYPE couchdb_couch_replicator_docs_dbs_deleted_total counter
couchdb_couch_replicator_docs_dbs_deleted_total 0
# TYPE couchdb_couch_replicator_docs_dbs_found_total counter
couchdb_couch_replicator_docs_dbs_found_total 2
# TYPE couchdb_couch_replicator_docs_failed_state_updates_total counter
couchdb_couch_replicator_docs_failed_state_updates_total 0
# TYPE couchdb_couch_replicator_failed_starts_total counter
couchdb_couch_replicator_failed_starts_total 0
# TYPE couchdb_couch_replicator_jobs_adds_total counter
couchdb_couch_replicator_jobs_adds_total 0
# TYPE couchdb_couch_replicator_jobs_crashed gauge
couchdb_couch_replicator_jobs_crashed 0
# TYPE couchdb_couch_replicator_jobs_crashes_total counter
couchdb_couch_replicator_jobs_crashes_total 0
# TYPE couchdb_couch_replicator_jobs_duplicate_adds_total counter
couchdb_couch_replicator_jobs_duplicate_adds_total 0
# TYPE couchdb_couch_replicator_jobs_pending gauge
couchdb_couch_replicator_jobs_pending 0
# TYPE couchdb_couch_replicator_jobs_removes_total counter
couchdb_couch_replicator_jobs_removes_total 0
# TYPE couchdb_couch_replicator_jobs_running gauge
couchdb_couch_replicator_jobs_running 0
# TYPE couchdb_couch_replicator_jobs_starts_total counter
couchdb_couch_replicator_jobs_starts_total 0
# TYPE couchdb_couch_replicator_jobs_stops_total counter
couchdb_couch_replicator_jobs_stops_total 0
# TYPE couchdb_couch_replicator_jobs_total gauge
couchdb_couch_replicator_jobs_total 0
# TYPE couchdb_couch_replicator_requests_total counter
couchdb_couch_replicator_requests_total 0
# TYPE couchdb_couch_replicator_responses_failure_total counter
couchdb_couch_replicator_responses_failure_total 0
# TYPE couchdb_couch_replicator_responses_total counter
couchdb_couch_replicator_responses_total 0
# TYPE couchdb_couch_replicator_stream_responses_failure_total counter
couchdb_couch_replicator_stream_responses_failure_total 0
# TYPE couchdb_couch_replicator_stream_responses_total counter
couchdb_couch_replicator_stream_responses_total 0
# TYPE couchdb_couch_replicator_worker_deaths_total counter
couchdb_couch_replicator_worker_deaths_total 0
# TYPE couchdb_couch_replicator_workers_started_total counter
couchdb_couch_replicator_workers_started_total 0
# TYPE couchdb_auth_cache_requests_total counter
couchdb_auth_cache_requests_total 0
# TYPE couchdb_auth_cache_misses_total counter
couchdb_auth_cache_misses_total 0
# TYPE couchdb_collect_results_time_seconds summary
couchdb_collect_results_time_seconds{quantile="0.5"} 0.0
couchdb_collect_results_time_seconds{quantile="0.75"} 0.0
couchdb_collect_results_time_seconds{quantile="0.9"} 0.0
couchdb_collect_results_time_seconds{quantile="0.95"} 0.0
couchdb_collect_results_time_seconds{quantile="0.99"} 0.0
couchdb_collect_results_time_seconds{quantile="0.999"} 0.0
couchdb_collect_results_time_seconds_sum 0.0
couchdb_collect_results_time_seconds_count 0
# TYPE couchdb_couch_server_lru_skip_total counter
couchdb_couch_server_lru_skip_total 0
# TYPE couchdb_database_purges_total counter
couchdb_database_purges_total 0
# TYPE couchdb_database_reads_total counter
couchdb_database_reads_total 0
# TYPE couchdb_database_writes_total counter
couchdb_database_writes_total 0
# TYPE couchdb_db_open_time_seconds summary
couchdb_db_open_time_seconds{quantile="0.5"} 0.0
couchdb_db_open_time_seconds{quantile="0.75"} 0.0
couchdb_db_open_time_seconds{quantile="0.9"} 0.0
couchdb_db_open_time_seconds{quantile="0.95"} 0.0
couchdb_db_open_time_seconds{quantile="0.99"} 0.0
couchdb_db_open_time_seconds{quantile="0.999"} 0.0
couchdb_db_open_time_seconds_sum 0.0
couchdb_db_open_time_seconds_count 0
# TYPE couchdb_dbinfo_seconds summary
couchdb_dbinfo_seconds{quantile="0.5"} 0.0
couchdb_dbinfo_seconds{quantile="0.75"} 0.0
couchdb_dbinfo_seconds{quantile="0.9"} 0.0
couchdb_dbinfo_seconds{quantile="0.95"} 0.0
couchdb_dbinfo_seconds{quantile="0.99"} 0.0
couchdb_dbinfo_seconds{quantile="0.999"} 0.0
couchdb_dbinfo_seconds_sum 0.0
couchdb_dbinfo_seconds_count 0
# TYPE couchdb_document_inserts_total counter
couchdb_document_inserts_total 0
# TYPE couchdb_document_purges_failure_total counter
couchdb_document_purges_failure_total 0
# TYPE couchdb_document_purges_success_total counter
couchdb_document_purges_success_total 0
# TYPE couchdb_document_purges_total_total counter
couchdb_document_purges_total_total 0
# TYPE couchdb_document_writes_total counter
couchdb_document_writes_total 0
# TYPE couchdb_httpd_aborted_requests_total counter
couchdb_httpd_aborted_requests_total 0
# TYPE couchdb_httpd_all_docs_timeouts_total counter
couchdb_httpd_all_docs_timeouts_total 0
# TYPE couchdb_httpd_bulk_docs_seconds summary
couchdb_httpd_bulk_docs_seconds{quantile="0.5"} 0.0
couchdb_httpd_bulk_docs_seconds{quantile="0.75"} 0.0
couchdb_httpd_bulk_docs_seconds{quantile="0.9"} 0.0
couchdb_httpd_bulk_docs_seconds{quantile="0.95"} 0.0
couchdb_httpd_bulk_docs_seconds{quantile="0.99"} 0.0
couchdb_httpd_bulk_docs_seconds{quantile="0.999"} 0.0
couchdb_httpd_bulk_docs_seconds_sum 0.0
couchdb_httpd_bulk_docs_seconds_count 0
...remaining couchdb metrics from _stats and _system
If an additional port config option is specified, then a client can call this API using that port which does not require authentication. This option is false``(OFF) by default. When the option ``true``(ON), the default ports for a 3 node cluster are ``17986
, 27986
, 37986
. See Configuration of Prometheus Endpoint for details.
GET /_node/_local/_prometheus HTTP/1.1
Accept: text/plain
Host: localhost:17986
1.2.14. /_node/{node-name}/_system
GET
/_node/{node-name}/_system
The _system
resource returns a JSON object containing various system-level statistics for the running server. The object is structured with top-level sections collating the statistics for a range of entries, with each individual statistic being easily identified, and the content of each statistic is self-describing.
The literal string _local
serves as an alias for the local node name, so for all stats URLs, {node-name}
may be replaced with _local
, to interact with the local node’s statistics.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Status Codes: |
|
Request:
GET /_node/_local/_system HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 187
Content-Type: application/json
Date: Sat, 10 Aug 2013 11:41:11 GMT
Server: CouchDB (Erlang/OTP)
{
"uptime": 259,
"memory": {
...
}
These statistics are generally intended for CouchDB developers only.
1.2.15. /_node/{node-name}/_restart
POST
/_node/{node-name}/_restart
This API is to facilitate integration testing only it is not meant to be used in production
Status Codes: |
|
---|
1.2.16. /_search_analyze
New in version 3.0.
POST
/_search_analyze
Tests the results of Lucene analyzer tokenization on sample text.
Parameters: |
|
---|---|
Status Codes: |
|
Request:
POST /_search_analyze HTTP/1.1
Host: localhost:5984
Content-Type: application/json
{"analyzer":"english", "text":"running"}
Response:
{
"tokens": [
"run"
]
}
1.2.17. /_utils
GET
/_utils
Accesses the built-in Fauxton administration interface for CouchDB.
Response Headers: | |
---|---|
| |
Status Codes: |
|
GET
/_utils/
Response Headers: | |
---|---|
| |
Status Codes: |
|
1.2.18. /_up
New in version 2.0.
GET
/_up
Confirms that the server is up, running, and ready to respond to requests. If maintenance_mode is true
or nolb
, the endpoint will return a 404 response.
Response Headers: | |
---|---|
| |
Status Codes: |
|
Response:
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 16
Content-Type: application/json
Date: Sat, 17 Mar 2018 04:46:26 GMT
Server: CouchDB/2.2.0-f999071ec (Erlang OTP/19)
X-Couch-Request-ID: c57a3b2787
X-CouchDB-Body-Time: 0
{"status":"ok"}
1.2.19. /_uuids
Changed in version 2.0.0.
GET
/_uuids
Requests one or more Universally Unique Identifiers (UUIDs) from the CouchDB instance. The response is a JSON object providing a list of UUIDs.
Request Headers: | |
---|---|
| |
Query Parameters: | |
| |
Response Headers: | |
| |
Status Codes: |
|
Request:
GET /_uuids?count=10 HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Content-Length: 362
Content-Type: application/json
Date: Sat, 10 Aug 2013 11:46:25 GMT
ETag: "DGRWWQFLUDWN5MRKSLKQ425XV"
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Server: CouchDB (Erlang/OTP)
{
"uuids": [
"75480ca477454894678e22eec6002413",
"75480ca477454894678e22eec600250b",
"75480ca477454894678e22eec6002c41",
"75480ca477454894678e22eec6003b90",
"75480ca477454894678e22eec6003fca",
"75480ca477454894678e22eec6004bef",
"75480ca477454894678e22eec600528f",
"75480ca477454894678e22eec6005e0b",
"75480ca477454894678e22eec6006158",
"75480ca477454894678e22eec6006161"
]
}
The UUID type is determined by the UUID algorithm setting in the CouchDB configuration.
The UUID type may be changed at any time through the Configuration API. For example, the UUID type could be changed to random
by sending this HTTP request:
PUT http://couchdb:5984/_node/nonode@nohost/_config/uuids/algorithm HTTP/1.1
Content-Type: application/json
Accept: */*
"random"
You can verify the change by obtaining a list of UUIDs:
{
"uuids" : [
"031aad7b469956cf2826fcb2a9260492",
"6ec875e15e6b385120938df18ee8e496",
"cff9e881516483911aa2f0e98949092d",
"b89d37509d39dd712546f9510d4a9271",
"2e0dbf7f6c4ad716f21938a016e4e59f"
]
}
1.2.20. /favicon.ico
GET
/favicon.ico
Binary content for the favicon.ico site icon.
Response Headers: | |
---|---|
| |
Status Codes: |
|
1.2.21. /_reshard
New in version 2.4.
GET
/_reshard
Returns a count of completed, failed, running, stopped, and total jobs along with the state of resharding on the cluster.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
GET /_reshard HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"completed": 21,
"failed": 0,
"running": 3,
"state": "running",
"state_reason": null,
"stopped": 0,
"total": 24
}
GET
/_reshard/state
Returns the resharding state and optional information about the state.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
GET /_reshard/state HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"reason": null,
"state": "running"
}
PUT
/_reshard/state
Change the resharding state on the cluster. The states are stopped
or running
. This starts and stops global resharding on all the nodes of the cluster. If there are any running jobs, they will be stopped when the state changes to stopped
. When the state changes back to running
those job will continue running.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Request JSON Object: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
PUT /_reshard/state HTTP/1.1
Accept: application/json
Host: localhost:5984
{
"state": "stopped",
"reason": "Rebalancing in progress"
}
Response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"ok": true
}
GET
/_reshard/jobs
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
GET /_reshard/jobs HTTP/1.1
Accept: application/json
Response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"jobs": [
{
"history": [
{
"detail": null,
"timestamp": "2019-03-28T15:28:02Z",
"type": "new"
},
{
"detail": "initial_copy",
"timestamp": "2019-03-28T15:28:02Z",
"type": "running"
},
...
],
"id": "001-171d1211418996ff47bd610b1d1257fc4ca2628868def4a05e63e8f8fe50694a",
"job_state": "completed",
"node": "node1@127.0.0.1",
"source": "shards/00000000-1fffffff/d1.1553786862",
"split_state": "completed",
"start_time": "2019-03-28T15:28:02Z",
"state_info": {},
"target": [
"shards/00000000-0fffffff/d1.1553786862",
"shards/10000000-1fffffff/d1.1553786862"
],
"type": "split",
"update_time": "2019-03-28T15:28:08Z"
},
...
],
"offset": 0,
"total_rows": 24
}
GET
/_reshard/jobs/{jobid}
Get information about the resharding job identified by jobid
.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
GET /_reshard/jobs/001-171d1211418996ff47bd610b1d1257fc4ca2628868def4a05e63e8f8fe50694a HTTP/1.1
Accept: application/json
Response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"id": "001-171d1211418996ff47bd610b1d1257fc4ca2628868def4a05e63e8f8fe50694a",
"job_state": "completed",
"node": "node1@127.0.0.1",
"source": "shards/00000000-1fffffff/d1.1553786862",
"split_state": "completed",
"start_time": "2019-03-28T15:28:02Z",
"state_info": {},
"target": [
"shards/00000000-0fffffff/d1.1553786862",
"shards/10000000-1fffffff/d1.1553786862"
],
"type": "split",
"update_time": "2019-03-28T15:28:08Z",
"history": [
{
"detail": null,
"timestamp": "2019-03-28T15:28:02Z",
"type": "new"
},
{
"detail": "initial_copy",
"timestamp": "2019-03-28T15:28:02Z",
"type": "running"
},
...
]
}
POST
/_reshard/jobs
Depending on what fields are specified in the request, one or more resharding jobs will be created. The response is a json array of results. Each result object represents a single resharding job for a particular node and range. Some of the responses could be successful and some could fail. Successful results will have the "ok": true
key and and value, and failed jobs will have the "error": "{error_message}"
key and value.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Request JSON Object: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
POST /_reshard/jobs HTTP/1.1
Accept: application/json
Content-Type: application/json
{
"db": "db3",
"range": "80000000-ffffffff",
"type": "split"
}
Response:
HTTP/1.1 201 Created
Content-Type: application/json
[
{
"id": "001-30d7848a6feeb826d5e3ea5bb7773d672af226fd34fd84a8fb1ca736285df557",
"node": "node1@127.0.0.1",
"ok": true,
"shard": "shards/80000000-ffffffff/db3.1554148353"
},
{
"id": "001-c2d734360b4cb3ff8b3feaccb2d787bf81ce2e773489eddd985ddd01d9de8e01",
"node": "node2@127.0.0.1",
"ok": true,
"shard": "shards/80000000-ffffffff/db3.1554148353"
}
]
DELETE
/_reshard/jobs/{jobid}
If the job is running, stop the job and then remove it.
Response JSON Object: | |
---|---|
| |
Status Codes: |
|
Request:
DELETE /_reshard/jobs/001-171d1211418996ff47bd610b1d1257fc4ca2628868def4a05e63e8f8fe50694a HTTP/1.1
Response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"ok": true
}
GET
/_reshard/jobs/{jobid}/state
Returns the running state of a resharding job identified by jobid
.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Request JSON Object: | |
| |
Status Codes: |
|
Request:
GET /_reshard/jobs/001-b3da04f969bbd682faaab5a6c373705cbcca23f732c386bb1a608cfbcfe9faff/state HTTP/1.1
Accept: application/json
Host: localhost:5984
Response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"reason": null,
"state": "running"
}
PUT
/_reshard/jobs/{jobid}/state
Change the state of a particular resharding job identified by jobid
. The state can be changed from stopped
to running
or from running
to stopped
. If an individual job is stopped
via this API it will stay stopped
even after the global resharding state is toggled from stopped
to running
. If the job is already completed
its state will stay completed
.
Request Headers: | |
---|---|
| |
Response Headers: | |
| |
Request JSON Object: | |
| |
Response JSON Object: | |
| |
Status Codes: |
|
Request:
PUT /_reshard/state/001-b3da04f969bbd682faaab5a6c373705cbcca23f732c386bb1a608cfbcfe9faff/state HTTP/1.1
Accept: application/json
Host: localhost:5984
{
"state": "stopped",
"reason": "Rebalancing in progress"
}
Response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"ok": true
}