本地英文版地址: ../en/starting-elasticsearch.html
启动 Elasticsearch 的方法因安装方式而异。
归档安装包 (.tar.gz
)
如果你是使用 .tar.gz
包 安装的 Elasticsearch,可以从命令行启动 Elasticsearch。
从命令行运行 Elasticsearch
可以从命令行启动 Elasticsearch,如下所示:
./bin/elasticsearch
如果你对 Elasticsearch 密钥库进行了密码保护,系统会提示你输入密钥库的密码。 更多详细信息请参考 安全设置。
默认情况下,Elasticsearch 在前台运行,将其日志打印到标准输出(STDOUT
),并且可以通过按 Ctrl-C
来停止。
所有与 Elasticsearch 打包在一起的脚本都需要一个支持数组的 Bash 版本,并假设 Bash 的存放位置是 /bin/bash
。
因此,Bash 应该可以直接或通过符号链接在这个路径上使用。
作为守护程序运行
要将 Elasticsearch 作为守护进程运行,请在命令行中指定 -d
,并使用 -p
选项将进程 ID 记录在一个文件中:
./bin/elasticsearch -d -p pid
如果你对 Elasticsearch 密钥库进行了密码保护,系统会提示你输入密钥库的密码。 更多详细信息请参考 安全设置。
日志信息可以在$ES_HOME/logs/
目录中找到。
要关闭 Elasticsearch,终止 pid
文件中记录的进程 ID:
pkill -F pid
归档安装包 (.zip
)
如果你是在 Windows 上使用 .zip
包 安装的 Elasticsearch,可以从命令行启动 Elasticsearch。
如果你想让 Elasticsearch 在系统启动时自动启动,不需要任何用户交互,那么请 在 Windows 上把 Elasticsearch 作为服务安装。
从命令行运行 Elasticsearch
可以从命令行启动 Elasticsearch,如下所示:
.\bin\elasticsearch.bat
如果你对 Elasticsearch 密钥库进行了密码保护,系统会提示你输入密钥库的密码。 更多详细信息请参考 安全设置。
默认情况下,Elasticsearch 在前台运行,将其日志打印到标准输出(STDOUT
),并且可以通过按 Ctrl-C
来停止。
Debian安装包
安装后不会自动启动 Elasticsearch。
如何启动和停止 Elasticsearch 取决于你的系统使用 SysV init
还是 systemd
(在较新的发行版中使用)。
可以通过运行以下命令来判断哪个正在被使用:
ps -p 1
使用 SysV init
运行 Elasticsearch
使用 update-rc.d
命令将 Elasticsearch 配置为在系统启动时自动启动:
sudo update-rc.d elasticsearch defaults 95 10
可以使用 service
命令启动和停止 Elasticsearch:
sudo -i service elasticsearch start sudo -i service elasticsearch stop
如果 Elasticsearch 由于任何原因无法启动,它会将失败的原因打印到 STDOUT。
日志文件可以在 /var/log/elasticsearch/
位置找到。
使用 systemd
运行 Elasticsearch
要将 Elasticsearch 配置为在系统启动时自动启动,请运行以下命令:
sudo /bin/systemctl daemon-reload sudo /bin/systemctl enable elasticsearch.service
Elasticsearch 可按如下方式启动和停止:
sudo systemctl start elasticsearch.service sudo systemctl stop elasticsearch.service
这些命令不提供关于 Elasticsearch 是否成功启动的反馈。
相反,这些信息将被写入位于 /var/log/elasticsearch/
的日志文件中。
如果你对 Elasticsearch 密钥库进行了密码保护,则需要使用本地文件和 systemd 环境变量向 systemd
提供密钥库密码。
该本地文件在存在时应受到保护,一旦 Elasticsearch 启动并运行,可以安全地删除该文件。
echo "keystore_password" > /path/to/my_pwd_file.tmp chmod 600 /path/to/my_pwd_file.tmp sudo systemctl set-environment ES_KEYSTORE_PASSPHRASE_FILE=/path/to/my_pwd_file.tmp sudo systemctl start elasticsearch.service
默认情况下,Elasticsearch 服务不在 systemd
日志中记录信息。
要启用journalctl
日志记录,必须从 elasticsearch.service
文件的 ExecStart
命令行中删除 --quiet
选项。
启用 systemd
日志记录时,可以使用 journalctl
命令获得日志记录信息:
要跟踪日志,执行:
sudo journalctl -f
要列出 elasticsearch 服务的日志记录:
sudo journalctl --unit elasticsearch
要列出从给定时间开始的 elasticsearch 服务的日志记录:
sudo journalctl --unit elasticsearch --since "2016-10-30 18:17:16"
更多命令行选项,请查看 man journalctl
或者 https://www.freedesktop.org/software/systemd/man/journalctl.html。
Docker 镜像
如果安装了 Docker 镜像,可以从命令行启动 Elasticsearch。 根据你使用的是开发模式还是生产模式,方法不同。 参考 Docker Run。
Windows MSI 安装包
如果你是在 Windows 上使用 .msi
安装包安装的 Elasticsearch,可以从命令行启动 Elasticsearch。
如果你想让它在没有任何用户交互的情况下在系统启动时自动启动,请 在 Windows 上将 Elasticsearch 作为服务安装。
从命令行运行 Elasticsearch
如果没有作为服务安装并配置为在安装完成时启动,则可以在安装后从命令行启动 Elasticsearch,如下所示:
.\bin\elasticsearch.exe
命令行终端将显示类似如下的输出:

默认情况下,Elasticsearch 在前台运行,除了 LOGSDIRECTORY
目录中的 <cluster name>.log
文件之外,其还将日志打印到 STDOUT
,且可以通过按 Ctrl-C
来停止。
RPM 安装包
安装后不会自动启动 Elasticsearch。
如何启动和停止 Elasticsearch 取决于你的系统使用 SysV init
还是 systemd
(在较新的发行版中使用)。
可以通过运行以下命令来判断哪个正在被使用:
ps -p 1
使用 SysV init
运行 Elasticsearch
使用 chkconfig
命令将 Elasticsearch 配置为在系统启动时自动启动:
sudo chkconfig --add elasticsearch
可以使用 service
命令启动和停止Elasticsearch:
sudo -i service elasticsearch start sudo -i service elasticsearch stop
如果 Elasticsearch 由于任何原因无法启动,它会将失败的原因打印到 STDOUT。
日志文件可以在 /var/log/elasticsearch/
位置找到。
使用 systemd
运行 Elasticsearch
要将 Elasticsearch 配置为在系统启动时自动启动,请运行以下命令:
sudo /bin/systemctl daemon-reload sudo /bin/systemctl enable elasticsearch.service
Elasticsearch 可按如下方式启动和停止:
sudo systemctl start elasticsearch.service sudo systemctl stop elasticsearch.service
这些命令不提供关于 Elasticsearch 是否成功启动的反馈。
相反,这些信息将被写入位于 /var/log/elasticsearch/
的日志文件中。
如果你对 Elasticsearch 密钥库进行了密码保护,则需要使用本地文件和 systemd 环境变量向 systemd
提供密钥库密码。
该本地文件在存在时应受到保护,一旦 Elasticsearch 启动并运行,可以安全地删除该文件。
echo "keystore_password" > /path/to/my_pwd_file.tmp chmod 600 /path/to/my_pwd_file.tmp sudo systemctl set-environment ES_KEYSTORE_PASSPHRASE_FILE=/path/to/my_pwd_file.tmp sudo systemctl start elasticsearch.service
默认情况下,Elasticsearch 服务不在 systemd
日志中记录信息。
要启用journalctl
日志记录,必须从 elasticsearch.service
文件的 ExecStart
命令行中删除 --quiet
选项。
启用 systemd
日志记录时,可以使用 journalctl
命令获得日志记录信息:
要跟踪日志,执行:
sudo journalctl -f
要列出 elasticsearch 服务的日志记录:
sudo journalctl --unit elasticsearch
要列出从给定时间开始的 elasticsearch 服务的日志记录:
sudo journalctl --unit elasticsearch --since "2016-10-30 18:17:16"
更多命令行选项,请查看 man journalctl
或者 https://www.freedesktop.org/software/systemd/man/journalctl.html。
- Elasticsearch权威指南: 其他版本:
- Elasticsearch是什么?
- 7.7版本的新特性
- 开始使用Elasticsearch
- 安装和设置
- 升级Elasticsearch
- 搜索你的数据
- 查询领域特定语言(Query DSL)
- SQL access(暂时不翻译)
- Overview
- Getting Started with SQL
- Conventions and Terminology
- Security
- SQL REST API
- SQL Translate API
- SQL CLI
- SQL JDBC
- SQL ODBC
- SQL Client Applications
- SQL Language
- Functions and Operators
- Comparison Operators
- Logical Operators
- Math Operators
- Cast Operators
- LIKE and RLIKE Operators
- Aggregate Functions
- Grouping Functions
- Date/Time and Interval Functions and Operators
- Full-Text Search Functions
- Mathematical Functions
- String Functions
- Type Conversion Functions
- Geo Functions
- Conditional Functions And Expressions
- System Functions
- Reserved keywords
- SQL Limitations
- 聚合
- 度量(metric)聚合
- 桶(bucket)聚合
- adjacency_matrix 聚合
- auto_date_histogram 聚合
- children 聚合
- composite 聚合
- date_histogram 聚合
- date_range 聚合
- diversified_sampler 聚合
- filter 聚合
- filters 聚合
- geo_distance 聚合
- geohash_grid 聚合
- geotile_grid 聚合
- global 聚合
- histogram 聚合
- ip_range 聚合
- missing 聚合
- nested 聚合
- parent 聚合
- range 聚合
- rare_terms 聚合
- reverse_nested 聚合
- sampler 聚合
- significant_terms 聚合
- significant_text 聚合
- terms 聚合
- 给范围字段分桶的微妙之处
- 管道(pipeline)聚合
- 矩阵(matrix)聚合
- 重度缓存的聚合
- 只返回聚合的结果
- 聚合元数据
- Returning the type of the aggregation
- 使用转换对聚合结果进行索引
- 脚本
- 映射
- 删除的映射类型
- 字段数据类型
- alias(别名)
- array(数组)
- binary(二进制)
- boolean(布尔)
- date(日期)
- date_nanos(日期纳秒)
- dense_vector(密集矢量)
- histogram(直方图)
- flattened(扁平)
- geo_point(地理坐标点)
- geo_shape(地理形状)
- IP
- join(联结)
- keyword(关键词)
- nested(嵌套)
- numeric(数值)
- object(对象)
- percolator(渗透器)
- range(范围)
- rank_feature(特征排名)
- rank_features(特征排名)
- search_as_you_type(输入即搜索)
- Sparse vector
- Text
- Token count
- Shape
- Constant keyword
- Meta-Fields
- Mapping parameters
- Dynamic Mapping
- Text analysis
- Overview
- Concepts
- Configure text analysis
- Built-in analyzer reference
- Tokenizer reference
- Char Group Tokenizer
- Classic Tokenizer
- Edge n-gram tokenizer
- Keyword Tokenizer
- Letter Tokenizer
- Lowercase Tokenizer
- N-gram tokenizer
- Path Hierarchy Tokenizer
- Path Hierarchy Tokenizer Examples
- Pattern Tokenizer
- Simple Pattern Tokenizer
- Simple Pattern Split Tokenizer
- Standard Tokenizer
- Thai Tokenizer
- UAX URL Email Tokenizer
- Whitespace Tokenizer
- Token filter reference
- Apostrophe
- ASCII folding
- CJK bigram
- CJK width
- Classic
- Common grams
- Conditional
- Decimal digit
- Delimited payload
- Dictionary decompounder
- Edge n-gram
- Elision
- Fingerprint
- Flatten graph
- Hunspell
- Hyphenation decompounder
- Keep types
- Keep words
- Keyword marker
- Keyword repeat
- KStem
- Length
- Limit token count
- Lowercase
- MinHash
- Multiplexer
- N-gram
- Normalization
- Pattern capture
- Pattern replace
- Phonetic
- Porter stem
- Predicate script
- Remove duplicates
- Reverse
- Shingle
- Snowball
- Stemmer
- Stemmer override
- Stop
- Synonym
- Synonym graph
- Trim
- Truncate
- Unique
- Uppercase
- Word delimiter
- Word delimiter graph
- Character filters reference
- Normalizers
- Index modules
- Ingest node
- Pipeline Definition
- Accessing Data in Pipelines
- Conditional Execution in Pipelines
- Handling Failures in Pipelines
- Enrich your data
- Processors
- Append Processor
- Bytes Processor
- Circle Processor
- Convert Processor
- CSV Processor
- Date Processor
- Date Index Name Processor
- Dissect Processor
- Dot Expander Processor
- Drop Processor
- Enrich Processor
- Fail Processor
- Foreach Processor
- GeoIP Processor
- Grok Processor
- Gsub Processor
- HTML Strip Processor
- Inference Processor
- Join Processor
- JSON Processor
- KV Processor
- Lowercase Processor
- Pipeline Processor
- Remove Processor
- Rename Processor
- Script Processor
- Set Processor
- Set Security User Processor
- Split Processor
- Sort Processor
- Trim Processor
- Uppercase Processor
- URL Decode Processor
- User Agent processor
- ILM: Manage the index lifecycle
- Monitor a cluster
- Frozen indices
- Roll up or transform your data
- Set up a cluster for high availability
- Snapshot and restore
- Secure a cluster
- Overview
- Configuring security
- User authentication
- Built-in users
- Internal users
- Token-based authentication services
- Realms
- Realm chains
- Active Directory user authentication
- File-based user authentication
- LDAP user authentication
- Native user authentication
- OpenID Connect authentication
- PKI user authentication
- SAML authentication
- Kerberos authentication
- Integrating with other authentication systems
- Enabling anonymous access
- Controlling the user cache
- Configuring SAML single-sign-on on the Elastic Stack
- Configuring single sign-on to the Elastic Stack using OpenID Connect
- User authorization
- Built-in roles
- Defining roles
- Security privileges
- Document level security
- Field level security
- Granting privileges for indices and aliases
- Mapping users and groups to roles
- Setting up field and document level security
- Submitting requests on behalf of other users
- Configuring authorization delegation
- Customizing roles and authorization
- Enabling audit logging
- Encrypting communications
- Restricting connections with IP filtering
- Cross cluster search, clients, and integrations
- Tutorial: Getting started with security
- Tutorial: Encrypting communications
- Troubleshooting
- Some settings are not returned via the nodes settings API
- Authorization exceptions
- Users command fails due to extra arguments
- Users are frequently locked out of Active Directory
- Certificate verification fails for curl on Mac
- SSLHandshakeException causes connections to fail
- Common SSL/TLS exceptions
- Common Kerberos exceptions
- Common SAML issues
- Internal Server Error in Kibana
- Setup-passwords command fails due to connection failure
- Failures due to relocation of the configuration files
- Limitations
- Alerting on cluster and index events
- Command line tools
- How To
- Glossary of terms
- REST APIs
- API conventions
- cat APIs
- cat aliases
- cat allocation
- cat anomaly detectors
- cat count
- cat data frame analytics
- cat datafeeds
- cat fielddata
- cat health
- cat indices
- cat master
- cat nodeattrs
- cat nodes
- cat pending tasks
- cat plugins
- cat recovery
- cat repositories
- cat shards
- cat segments
- cat snapshots
- cat task management
- cat templates
- cat thread pool
- cat trained model
- cat transforms
- Cluster APIs
- Cluster allocation explain
- Cluster get settings
- Cluster health
- Cluster reroute
- Cluster state
- Cluster stats
- Cluster update settings
- Nodes feature usage
- Nodes hot threads
- Nodes info
- Nodes reload secure settings
- Nodes stats
- Pending cluster tasks
- Remote cluster info
- Task management
- Voting configuration exclusions
- Cross-cluster replication APIs
- Document APIs
- Enrich APIs
- Explore API
- Index APIs
- Add index alias
- Analyze
- Clear cache
- Clone index
- Close index
- Create index
- Delete index
- Delete index alias
- Delete index template
- Flush
- Force merge
- Freeze index
- Get field mapping
- Get index
- Get index alias
- Get index settings
- Get index template
- Get mapping
- Index alias exists
- Index exists
- Index recovery
- Index segments
- Index shard stores
- Index stats
- Index template exists
- Open index
- Put index template
- Put mapping
- Refresh
- Rollover index
- Shrink index
- Split index
- Synced flush
- Type exists
- Unfreeze index
- Update index alias
- Update index settings
- Index lifecycle management API
- Ingest APIs
- Info API
- Licensing APIs
- Machine learning anomaly detection APIs
- Add events to calendar
- Add jobs to calendar
- Close jobs
- Create jobs
- Create calendar
- Create datafeeds
- Create filter
- Delete calendar
- Delete datafeeds
- Delete events from calendar
- Delete filter
- Delete forecast
- Delete jobs
- Delete jobs from calendar
- Delete model snapshots
- Delete expired data
- Estimate model memory
- Find file structure
- Flush jobs
- Forecast jobs
- Get buckets
- Get calendars
- Get categories
- Get datafeeds
- Get datafeed statistics
- Get influencers
- Get jobs
- Get job statistics
- Get machine learning info
- Get model snapshots
- Get overall buckets
- Get scheduled events
- Get filters
- Get records
- Open jobs
- Post data to jobs
- Preview datafeeds
- Revert model snapshots
- Set upgrade mode
- Start datafeeds
- Stop datafeeds
- Update datafeeds
- Update filter
- Update jobs
- Update model snapshots
- Machine learning data frame analytics APIs
- Create data frame analytics jobs
- Create inference trained model
- Delete data frame analytics jobs
- Delete inference trained model
- Evaluate data frame analytics
- Explain data frame analytics API
- Get data frame analytics jobs
- Get data frame analytics jobs stats
- Get inference trained model
- Get inference trained model stats
- Start data frame analytics jobs
- Stop data frame analytics jobs
- Migration APIs
- Reload search analyzers
- Rollup APIs
- Search APIs
- Security APIs
- Authenticate
- Change passwords
- Clear cache
- Clear roles cache
- Create API keys
- Create or update application privileges
- Create or update role mappings
- Create or update roles
- Create or update users
- Delegate PKI authentication
- Delete application privileges
- Delete role mappings
- Delete roles
- Delete users
- Disable users
- Enable users
- Get API key information
- Get application privileges
- Get builtin privileges
- Get role mappings
- Get roles
- Get token
- Get users
- Has privileges
- Invalidate API key
- Invalidate token
- OpenID Connect Prepare Authentication API
- OpenID Connect authenticate API
- OpenID Connect logout API
- SAML prepare authentication API
- SAML authenticate API
- SAML logout API
- SAML invalidate API
- SSL certificate
- Snapshot and restore APIs
- Snapshot lifecycle management API
- Transform APIs
- Usage API
- Watcher APIs
- Definitions
- Breaking changes
- Release notes
- Elasticsearch version 7.7.1
- Elasticsearch version 7.7.0
- Elasticsearch version 7.6.2
- Elasticsearch version 7.6.1
- Elasticsearch version 7.6.0
- Elasticsearch version 7.5.2
- Elasticsearch version 7.5.1
- Elasticsearch version 7.5.0
- Elasticsearch version 7.4.2
- Elasticsearch version 7.4.1
- Elasticsearch version 7.4.0
- Elasticsearch version 7.3.2
- Elasticsearch version 7.3.1
- Elasticsearch version 7.3.0
- Elasticsearch version 7.2.1
- Elasticsearch version 7.2.0
- Elasticsearch version 7.1.1
- Elasticsearch version 7.1.0
- Elasticsearch version 7.0.0
- Elasticsearch version 7.0.0-rc2
- Elasticsearch version 7.0.0-rc1
- Elasticsearch version 7.0.0-beta1
- Elasticsearch version 7.0.0-alpha2
- Elasticsearch version 7.0.0-alpha1