（三）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..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./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 fromhttps://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:

如果一切顺利安装，你应该看到一堆如下所示的消息：

[--16T14::,][INFO ][o.e.n.Node               ] [] initializing ...
[--16T14::,][INFO ][o.e.e.NodeEnvironment    ] [-bjhwl] using [] data paths, mounts [[/ (/dev/sda1)]], net usable_space [.7gb], net total_space [.6gb], spins? [no], types [ext4]
[--16T14::,][INFO ][o.e.e.NodeEnvironment    ] [-bjhwl] heap size [.9gb], compressed ordinary object pointers [true]
[--16T14::,][INFO ][o.e.n.Node               ] [-bjhwl] node name [-bjhwl] derived from node ID; set [node.name] to override
[--16T14::,][INFO ][o.e.n.Node               ] [-bjhwl] version[6.2.], pid[], build[f5daa16/--16T09::.346Z], OS[Linux/4.4.--generic/amd64], JVM[Oracle Corporation/Java HotSpot(TM) -Bit Server VM/1.8.0_60/25.60-b23]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [aggs-matrix-stats]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [ingest-common]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [lang-expression]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [lang-mustache]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [lang-painless]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [percolator]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [reindex]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [transport-netty3]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded module [transport-netty4]
[--16T14::,][INFO ][o.e.p.PluginsService     ] [-bjhwl] loaded plugin [mapper-murmur3]
[--16T14::,][INFO ][o.e.n.Node               ] [-bjhwl] initialized
[--16T14::,][INFO ][o.e.n.Node               ] [-bjhwl] starting ...
[--16T14::,][INFO ][o.e.t.TransportService   ] [-bjhwl] publish_address {192.168.8.112:}, bound_addresses {{192.168.8.112:}
[--16T14::,][WARN ][o.e.b.BootstrapCheck     ] [-bjhwl] max virtual memory areas vm.max_map_count [] likely too low, increase to at least []
[--16T14::,][INFO ][o.e.h.HttpServer         ] [-bjhwl] publish_address {192.168.8.112:}, bound_addresses {[::]:}, {192.168.8.112:}
[--16T14::,][INFO ][o.e.g.GatewayService     ] [-bjhwl] recovered [] indices into cluster_state
[--16T14::,][INFO ][o.e.n.Node               ] [-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的访问。如有必要，可以配置此端口。