（七）Create an Index

Now let’s create an index named "customer" and then list all the indexes again:

如今让咱们建立一个名为“customer”的索引，而后再次列出全部索引：

PUT /customer?pretty
GET /_cat/indices?v

The first command creates the index named "customer" using the PUT verb. We simply append pretty to the end of the call to tell it to pretty-print the JSON response (if any).

第一个命令使用PUT动词建立名为“customer”的索引。咱们只是简单地追加到调用的结尾，告诉它打印JSON响应（若是有的话）。

And the response:

health status index    uuid                   pri rep docs.count docs.deleted store.size pri.store.size
yellow open   customer 95SQ4TSUT7mWBT7VNHH67A   5   1          0            0       260b           260b

The results of the second command tells us that we now have 1 index named customer and it has 5 primary shards and 1 replica (the defaults) and it contains 0 documents in it.

第二个命令的结果告诉咱们，咱们如今有一个名为customer的索引，它有5个主分片和1个副本（默认值），而且它包含0个文档。

 

You might also notice that the customer index has a yellow health tagged to it. Recall from our previous discussion that yellow means that some replicas are not (yet) allocated. The reason this happens for this index is because Elasticsearch by default created one replica for this index. 

您可能还注意到客户索引标记了黄色运行情况。回想一下咱们以前的讨论，黄色表示某些副本还没有（还没有）分配。此索引起生这种状况的缘由是由于默认状况下Elasticsearch为此索引建立了一个副本。

 

Since we only have one node running at the moment, that one replica cannot yet be allocated (for high availability) until a later point in time when another node joins the cluster. Once that replica gets allocated onto a second node, the health status for this index will turn to green.

因为咱们目前只有一个节点在运行，所以在另外一个节点加入集群的较晚时间点以前，尚没法分配一个副本（用于高可用性）。将该副本分配到第二个节点后，此索引的运行情况将变为绿色。