Elasticsearch URLs for various services

1.curl192.168.106.58:9200/_cat/health?v cluster Health View

Epoch Timestamp cluster status node.total node.data shards pri relo init unassign
1400639131 10:25:31 Elasticsearch Green 1 1 18 18 0 0 0

2. Curl 192.168.106.58:9200/_cat/nodes?v Node Health view

Host IP heap.percent ram.percent load node.role Master Name
WENDAH1 192.168.106.58 6.65 D * Primus

3.curl 192.168.106.58:9200/_cat/indices?v List Cluster index

health index        PRI rep docs.count docs.deleted Store.size pri.store.size 
Green  a Utoindex      6   0    1800000            0    854.4 MB        854.4MB&NBSP,
Green  autoindex111   6   0    1400000   &NBS P        0    864.4MB        864.4mb 
Green  product   & nbsp    6   0    3000000            0      1.2GB   & nbsp      1.2gb 

4.curl-xput 192.168.106.58:9200/customer?pretty Creating a customer index pretty representing the print JSON response

{
"Acknowledged": true
}

5.curl-xput 192.168.106.58:9200/customer/external/1?pretty '-d {"name": "JOhn Doe"} ' index data

6.curl-xget 192.168.106.58:9200/customer/external/1?pretty Get Query data

7. Curl-xdelete 192.168.106.58:9200/customer?pretty Delete Index

8.curl-xput 192.168.106.58:9200/customer/external/1?pretty '-d {"name": "JOhn Doe"} ' update index data with ID

< Span style= "LINE-HEIGHT:28PX;" >9.curl-xpost 192.168.106.58:9200/customer/external?pretty '-d {"name": "JOhn Doe"} ' access index data random ID span>

< Span style= "LINE-HEIGHT:28PX;" >10.curl-xdelete 192.168.106.58:9200/customer/external/2?pretty Remove

by ID

11.curl-xdelete ' 192.168.106.58:9200/customer/external/_query?pretty '-d '
{
  "query": {"match": {"name": "John"}}
} ' Delete

from a query

12.curl-xpost ' 192.168.106.58:9200/customer/external/_bulk?pretty '-d '
{"Index": {"_id": "1"}}
{"Name": "John Doe"}
{"Index": {"_id": "2"}}
{"Name": "Jane Doe"}
‘
Curl-xpost ' 192.168.106.58:9200/customer/external/_bulk?pretty '-d '
{"Update": {"_id": "1"}}
{"Doc": {"name": "John Doe becomes Jane Doe"}}
{"Delete": {"_id": "2"}}
‘

Curl-xpost ' 192.168.106.58:9200/bank/account/_bulk?pretty '--data-binary @accounts. JSON read File Bulk index

Bulk Index operations

Curl-xpost ' 192.168.106.58:9200/bank/_search?pretty '-d '
{
"Query": {
"BOOL": {
"Must": [
{"Match": {"Address": "Mill"}},
{"Match": {"Address": "Lane"}}
]
}
}
} ' query DSL (later in detail)

192.168.106.58:9200/_nodes/process?pretty view process information including the number of open files, lock memory, etc.

Index related

Url	Description
/index/_search	Don't explain
/_aliases	Gets or operates an alias for an index
/index/
/index/type/	Create or manipulate types
/index/_mapping	Create or manipulate mapping
/index/_settings	Create or manipulate the settings (Number_of_shards is not changed)
/index/_open	Open an index that is closed
/index/_close	Close Index
/index/_refresh	Refresh index (make new plus content visible to search)
/index/_flush	Refresh Index Commit changes to the Lucene index file and empty Elasticsearch's transaction log, The difference from refresh needs to be studied
/index/_optimize	Optimize Segement, personally think the main is to merge segement
/index/_status	Get status information for an index
/index/_segments	Get the status information for an indexed segments
/index/_explain	Does not perform an actual search, but returns an explanatory message
/index/_analyze	Do not perform actual search, text analysis based on input parameters
/index/type/id	Operation of the specified document, not explained
/index/type/id/_create	Creates a document that returns failure if the file already exists
/index/type/id/_update	Update a file, if the file does not exist, the return fails

DISTRIBUTED

Url	Description
/_cluster/nodes	Get a list of nodes and information in a cluster
/_cluster/health	Get cluster information
/_cluster/state	Get all the information in the cluster (cluster information, node information, mapping information, etc.)

NODES

URL	description
/_nodes/process	I mainly see file descriptor this information
/_nodes/process/stats	statistics (memory, CPU)
/_NODES/JVM	get virtual machine statistics for each node and Configuration information
/_nodes/jvm/stats	More detailed virtual machine information
/_nodes/http	Get individual nodes HTTP information (such as IP address)
/_nodes/http/stats	get statistics on each node handling HTTP requests
/_nodes/t Hread_pool	get various types of thread pools
/_nodes/thread_pool/stats	Get statistics for various types of thread pools

The above operations and can be done through such

/_nodes/${nodeid}/jvm/stats

/_nodes/${nodeip}/jvm/stats

/_nodes/${nodeattribute}/jvm/stats

The form of the operation for the specified node.

 

other

/_template/templatename Create an index configuration template, such as the default mapping

/_percolator/indexname/percolatorname Create percolator (how to translate this word into Chinese is a problem)

/index/type/_percolate/the document specified in the payload is "reversed

conclusion

By listing the URLs, individuals feel that it is helpful to grasp the concept and system structure of the whole elasticsearch, and the next step needs to be researched on the key content (_search must be the key content).

Reference: Http://wwwlouxuemingcom.blog.163.com/blog/static/209747822013287138100/

Elasticsearch URLs for various services