（三）Installation

Elasticsearch requires at least Java 8. Specifically as of this writing, it is recommended that you use the Oracle JDK version 1.8.0_131. Java installation varies from platform to platform so we won’t go into those details here. Oracle’s recommended installation documentation can be found on Oracle’s website. Suffice to say, before you install Elasticsearch, please check your Java version first by running (and then install/upgrade accordingly if needed):

Elasticsearch至少須要Java 8.具體到撰寫本文時，建議您使用Oracle JDK版本1.8.0_131。 Java安裝因平臺而異，所以咱們不會在此處詳細介紹。能夠在Oracle的網站上找到Oracle推薦的安裝文檔。能夠說，在安裝Elasticsearch以前，請先運行檢查Java版本（而後根據須要進行相應的安裝/升級）：

java -version
echo $JAVA_HOME

Once we have Java set up, we can then download and run Elasticsearch. The binaries are available from www.elastic.co/downloads along with all the releases that have been made in the past. For each release, you have a choice among a zip or tar archive, a DEB or RPM package, or a Windows MSIinstallation package.

一旦咱們設置了Java，咱們就能夠下載並運行Elasticsearch。這些二進制文件能夠從www.elastic.co/downloads得到，以及過去發佈的全部版本。對於每一個版本，您能夠選擇zip或tar存檔，DEB或RPM包或Windows MSI安裝包。

Installation example with tar

使用tar的安裝

For simplicity, let’s use the  tar file.

爲簡單起見，讓咱們使用tar文件。

 

Let’s download the Elasticsearch 6.2.4 tar as follows:

讓咱們下載Elasticsearch 6.2.4 tar以下：

curl -L -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.4.tar.gz

 

Then extract it as follows:

而後提取以下：

tar -xvf elasticsearch-6.2.4.tar.gz

 

It will then create a bunch of files and folders in your current directory. We then go into the bin directory as follows:

而後它會在當前目錄中建立一堆文件和文件夾。而後咱們進入bin目錄，以下所示：

cd elasticsearch-6.2.4/bin

 

And now we are ready to start our node and single cluster:

如今咱們準備啓動咱們的節點和單個集羣：

./elasticsearch

Installation with Homebrew

使用Homebrewedit進行安裝

On macOS, Elasticsearch can also be installed via  Homebrew:

在macOS上，Elasticsearch也能夠經過Homebrew安裝：

brew install elasticsearch

If installation succeeds, Homebrew will finish by saying that you can start Elasticsearch by entering elasticsearch. Do that now. The expected response is described below, under Successfully running node

若是安裝成功，Homebrew將說完你能夠經過輸入elasticsearch來啓動Elasticsearch。如今就這樣作。在成功運行nodeedit下，下面描述了預期的響應

Installation example with MSI Windows Installer

For Windows users, we recommend using the MSI Installer package. The package contains a graphical user interface (GUI) that guides you through the installation process.

對於Windows用戶，咱們建議使用MSI安裝程序包。該軟件包包含一個圖形用戶界面（GUI），可指導您完成安裝過程

 

First, download the Elasticsearch 6.2.4 MSI from https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.4.msi

首先，從https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.4.msi下載Elasticsearch 6.2.4 MSI

 

Then double-click the downloaded file to launch the GUI. Within the first screen, select the deployment directories:

而後雙擊下載的文件以啓動GUI。在第一個屏幕中，選擇部署目錄：

 Then select whether to install as a service or start Elasticsearch manually as needed. To align with the tar example, choose not to install as a service:

而後選擇是做爲服務安裝仍是根據須要手動啓動Elasticsearch。要與tar示例對齊，請選擇不安裝爲服務：

 

 For configuration, simply leave the default values:

對於配置，只需保留默認值：

 

Again, to align with the tar example, uncheck all plugins to not install any plugins:

再次，要與tar示例對齊，請取消選中全部插件以不安裝任何插件：

 

After clicking the install button, Elasticsearch will be installed:

單擊安裝按鈕後，將安裝Elasticsearch：

 

By default, Elasticsearch will be installed at %PROGRAMFILES%\Elastic\Elasticsearch. Navigate here and go into the bin directory as follows:

默認狀況下，Elasticsearch將安裝在％PROGRAMFILES％\ Elastic \ Elasticsearch中。在此處導航並進入bin目錄，以下所示：

with Command Prompt:

使用命令提示符：

cd %PROGRAMFILES%\Elastic\Elasticsearch\bin

 with PowerShell:

cd $env:PROGRAMFILES\Elastic\Elasticsearch\bin

And now we are ready to start our node and single cluster:

如今咱們準備啓動咱們的節點和單個集羣：

.\elasticsearch.exe

Successfully running node

If everything goes well with installation, you should see a bunch of messages that look like below:

若是一切順利安裝，你應該看到一堆以下所示的消息：

[2016-09-16T14:17:51,251][INFO ][o.e.n.Node               ] [] initializing ...
[2016-09-16T14:17:51,329][INFO ][o.e.e.NodeEnvironment    ] [6-bjhwl] using [1] data paths, mounts [[/ (/dev/sda1)]], net usable_space [317.7gb], net total_space [453.6gb], spins? [no], types [ext4]
[2016-09-16T14:17:51,330][INFO ][o.e.e.NodeEnvironment    ] [6-bjhwl] heap size [1.9gb], compressed ordinary object pointers [true]
[2016-09-16T14:17:51,333][INFO ][o.e.n.Node               ] [6-bjhwl] node name [6-bjhwl] derived from node ID; set [node.name] to override
[2016-09-16T14:17:51,334][INFO ][o.e.n.Node               ] [6-bjhwl] version[6.2.4], pid[21261], build[f5daa16/2016-09-16T09:12:24.346Z], OS[Linux/4.4.0-36-generic/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_60/25.60-b23]
[2016-09-16T14:17:51,967][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [aggs-matrix-stats]
[2016-09-16T14:17:51,967][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [ingest-common]
[2016-09-16T14:17:51,967][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [lang-expression]
[2016-09-16T14:17:51,967][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [lang-mustache]
[2016-09-16T14:17:51,967][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [lang-painless]
[2016-09-16T14:17:51,967][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [percolator]
[2016-09-16T14:17:51,968][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [reindex]
[2016-09-16T14:17:51,968][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [transport-netty3]
[2016-09-16T14:17:51,968][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded module [transport-netty4]
[2016-09-16T14:17:51,968][INFO ][o.e.p.PluginsService     ] [6-bjhwl] loaded plugin [mapper-murmur3]
[2016-09-16T14:17:53,521][INFO ][o.e.n.Node               ] [6-bjhwl] initialized
[2016-09-16T14:17:53,521][INFO ][o.e.n.Node               ] [6-bjhwl] starting ...
[2016-09-16T14:17:53,671][INFO ][o.e.t.TransportService   ] [6-bjhwl] publish_address {192.168.8.112:9300}, bound_addresses {{192.168.8.112:9300}
[2016-09-16T14:17:53,676][WARN ][o.e.b.BootstrapCheck     ] [6-bjhwl] max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
[2016-09-16T14:17:56,731][INFO ][o.e.h.HttpServer         ] [6-bjhwl] publish_address {192.168.8.112:9200}, bound_addresses {[::1]:9200}, {192.168.8.112:9200}
[2016-09-16T14:17:56,732][INFO ][o.e.g.GatewayService     ] [6-bjhwl] recovered [0] indices into cluster_state
[2016-09-16T14:17:56,748][INFO ][o.e.n.Node               ] [6-bjhwl] started

Without going too much into detail, we can see that our node named "6-bjhwl" (which will be a different set of characters in your case) has started and elected itself as a master in a single cluster. Don’t worry yet at the moment what master means. The main thing that is important here is that we have started one node within one cluster.

在不詳細討論的狀況下，咱們能夠看到名爲「6-bjhwl」的節點（在您的狀況下將是一組不一樣的字符）已經啓動並選擇本身做爲單個集羣中的主節點。如今不要擔憂主節點意味着什麼。這裏最重要的是咱們在一個集羣中啓動了一個節點。

 

As mentioned previously, we can override either the cluster or node name. This can be done from the command line when starting Elasticsearch as follows:

如前所述，咱們能夠覆蓋集羣或節點名稱。這能夠在啓動Elasticsearch時從命令行完成，以下所示：

./elasticsearch -Ecluster.name=my_cluster_name -Enode.name=my_node_name

Also note the line marked http with information about the HTTP address ( 192.168.8.112) and port ( 9200) that our node is reachable from. By default, Elasticsearch uses port  9200 to provide access to its REST API. This port is configurable if necessary.

另請注意標有http的行，其中包含有關咱們的節點能夠訪問的HTTP地址（192.168.8.112）和端口（9200）的信息。默認狀況下，Elasticsearch使用端口9200來提供對其REST API的訪問。若有必要，能夠配置此端口。