linux docker 安装elasticsearch7.17.4

docker安装mysql

依赖安装

yum install -y yum-utils device-mapper-persistent-data lvm2

配置docker-ce源

yum-config-manager \
--add-repo \
http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo

安装

yum install -y docker-ce

数据文件以及配置,可根据自己的磁盘定义

mkdir -p /data/docker &&  mkdir -p /etc/docker/

创建配置文件

下面json中data-root的值是docker的数据目录,请根据自己需要填写相应位置

cat >> /etc/docker/daemon.json << EOF
{
  "storage-driver": "overlay2",
  "insecure-registries": ["registry.access.redhat.com","quay.io"],
  "registry-mirrors": ["https://60699eq2.mirror.aliyuncs.com","https://registry.docker-cn.com"],
  "exec-opts": ["native.cgroupdriver=systemd"],
  "live-restore": true,
  "log-opts": {
  "max-size": "100m"
   },
  "data-root":"/data/docker"
}
EOF

启动docker以及开机自启动

systemctl daemon-reload && systemctl start docker && systemctl enable docker

确认docker版本

docker info

创建目录

useradd elasticsearch
mkdir -p /data/es/{data,logs,conf,plugins}
chown  -R  elasticsearch.elasticsearch  /data/es

修改配置信息elasticsearch.yml,jvm.options

elasticsearch配置文件

注意:192.168.32.1要改成自己机器的局域网ip

cat >> /data/es/conf/elasticsearch.yml <<EOF
cluster.name: es
node.name: es-node
bootstrap.memory_lock: false
network.host: 0.0.0.0
http.port: 9200
transport.tcp.port: 9300
http.cors.enabled: true
http.cors.allow-origin: "*"
discovery.seed_hosts: ["192.168.32.1:9300"]
cluster.initial_master_nodes: ["192.168.32.1"]
EOF

elasticsearch的JVM配置信息

cat >> /data/es/conf/jvm.options <<EOF
## JVM configuration

################################################################
## IMPORTANT: JVM heap size
################################################################
##
## You should always set the min and max JVM heap
## size to the same value. For example, to set
## the heap to 4 GB, set:
##
## -Xms4g
## -Xmx4g
##
## See https://www.elastic.co/guide/en/elasticsearch/reference/current/heap-size.html
## for more information
##
################################################################

# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space

-Xms2g
-Xmx2g

################################################################
## Expert settings
################################################################
##
## All settings below this section are considered
## expert settings. Don't tamper with them unless
## you understand what you are doing
##
################################################################

## GC configuration
8-13:-XX:+UseConcMarkSweepGC
8-13:-XX:CMSInitiatingOccupancyFraction=75
8-13:-XX:+UseCMSInitiatingOccupancyOnly

## G1GC Configuration
# NOTE: G1 GC is only supported on JDK version 10 or later
# to use G1GC, uncomment the next two lines and update the version on the
# following three lines to your version of the JDK
# 10-13:-XX:-UseConcMarkSweepGC
# 10-13:-XX:-UseCMSInitiatingOccupancyOnly
14-:-XX:+UseG1GC
14-:-XX:G1ReservePercent=25
14-:-XX:InitiatingHeapOccupancyPercent=30

## DNS cache policy
# cache ttl in seconds for positive DNS lookups noting that this overrides the
# JDK security property networkaddress.cache.ttl; set to -1 to cache forever
-Des.networkaddress.cache.ttl=60
# cache ttl in seconds for negative DNS lookups noting that this overrides the
# JDK security property networkaddress.cache.negative ttl; set to -1 to cache
# forever
-Des.networkaddress.cache.negative.ttl=10

## optimizations

# pre-touch memory pages used by the JVM during initialization
-XX:+AlwaysPreTouch

## basic

# explicitly set the stack size
-Xss1m

# set to headless, just in case
-Djava.awt.headless=true

# ensure UTF-8 encoding by default (e.g. filenames)
-Dfile.encoding=UTF-8

# use our provided JNA always versus the system one
-Djna.nosys=true

# turn off a JDK optimization that throws away stack traces for common
# exceptions because stack traces are important for debugging
-XX:-OmitStackTraceInFastThrow

# enable helpful NullPointerExceptions (https://openjdk.java.net/jeps/358), if
# they are supported
14-:-XX:+ShowCodeDetailsInExceptionMessages

# flags to configure Netty
-Dio.netty.noUnsafe=true
-Dio.netty.noKeySetOptimization=true
-Dio.netty.recycler.maxCapacityPerThread=0

# log4j 2
-Dlog4j.shutdownHookEnabled=false
-Dlog4j2.disable.jmx=true
-Dlog4j2.formatMsgNoLookups=true

-Djava.io.tmpdir=${ES_TMPDIR}

## heap dumps

# generate a heap dump when an allocation from the Java heap fails
# heap dumps are created in the working directory of the JVM
-XX:+HeapDumpOnOutOfMemoryError

# specify an alternative path for heap dumps; ensure the directory exists and
# has sufficient space
-XX:HeapDumpPath=data

# specify an alternative path for JVM fatal error logs
-XX:ErrorFile=logs/hs_err_pid%p.log

## JDK 8 GC logging

8:-XX:+PrintGCDetails
8:-XX:+PrintGCDateStamps
8:-XX:+PrintTenuringDistribution
8:-XX:+PrintGCApplicationStoppedTime
8:-Xloggc:logs/gc.log
8:-XX:+UseGCLogFileRotation
8:-XX:NumberOfGCLogFiles=32
8:-XX:GCLogFileSize=64m

# JDK 9+ GC logging
#9-:-Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m
# due to internationalization enhancements in JDK 9 Elasticsearch need to set the provider to COMPAT otherwise
# time/date parsing will break in an incompatible way for some date patterns and locals
#9-:-Djava.locale.providers=COMPAT

# temporary workaround for C2 bug with JDK 10 on hardware with AVX-512
10-:-XX:UseAVX=2
EOF

修改权限

chown -R  1000.1000  /data/es 

服务启动

docker run -d  --name elasticsearch  --restart always --net=host \
-v /usr/share/zoneinfo/Asia/Shanghai:/etc/localtime \
-v /data/es/conf/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
-v /data/es/conf/jvm.options:/usr/share/elasticsearch/config/jvm.options \
-v /data/es/plugins/:/usr/share/elasticsearch/plugins \
-v /data/es/data/:/usr/share/elasticsearch/data \
-v /data/es/logs/:/usr/share/elasticsearch/logs \
elasticsearch:7.17.4

验证是否安装成功

curl 127.0.0.1:9200
h-7.17.14.jar:7.17.14] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112) [elasticsearch-cli-7.17.14.jar:7.17.14] at org.elasticsearch.cli.Command.main(Command.java:77) [elasticsearch-cli-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:125) [elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) [elasticsearch-7.17.14.jar:7.17.14] [2025-06-26T11:32:15,565][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [node-1] uncaught exception in thread [main] org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: failed to obtain node locks, tried [[/kms/component/es/data]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])? at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:173) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:160) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112) ~[elasticsearch-cli-7.17.14.jar:7.17.14] at org.elasticsearch.cli.Command.main(Command.java:77) ~[elasticsearch-cli-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:125) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) ~[elasticsearch-7.17.14.jar:7.17.14] Caused by: java.lang.IllegalStateException: failed to obtain node locks, tried [[/kms/component/es/data]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])? at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:328) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.node.Node.<init>(Node.java:429) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.node.Node.<init>(Node.java:309) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:234) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:234) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:434) ~[elasticsearch-7.17.14.jar:7.17.14] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:169) ~[elasticsearch-7.17.14.jar:7.17.14]如何解决
最新发布
06-27
<think>我们正在解决Elasticsearch启动时出现的`failedtoobtainnodelocks`错误。根据引用[2],这个错误通常是由于节点锁获取失败引起的,可能的原因包括:1.数据目录不可写2.多个节点使用了同一个数据目录,但没有增加`node.max_local_storage_nodes`配置(默认是1,即一个数据目录只能被一个节点使用)用户的问题是关于Elasticsearch7.17.14的,但引用中给出的例子是7.17.6和7.17.9,不过解决方法类似。解决步骤:1.**检查数据目录权限**:确保运行Elasticsearch的用户(非root用户)对数据目录有读写权限。2.**检查是否已有节点运行**:确保没有其他Elasticsearch实例正在使用同一个数据目录。3.**检查`node.max_local_storage_nodes`设置**:如果需要在同一机器上启动多个节点共享同一个数据目录,需要增加这个配置(但一般生产环境不推荐)。4.**清理锁文件**:如果之前节点异常退出,可能残留了锁文件,需要手动删除。具体操作:**步骤1:确保使用非root用户运行**引用[1]中提到了不能以root用户运行,因此我们需要创建一个专用用户(如果还没有的话)并授权。例如:```bash#创建elasticsearch用户组和用户groupaddelasticsearchuseradd-gelasticsearchelasticsearch```**步骤2:更改数据目录的拥有者**假设数据目录是`/home/elk/elastic/elasticsearch-7.17.6/data`(根据引用[1])或用户配置的目录,将其改为实际使用的数据目录。```bashchown-Relasticsearch:elasticsearch/path/to/elasticsearch/data```**步骤3:检查是否有其他节点正在运行**使用`ps`命令查看:```bashps-ef|grepelasticsearch```如果发现已有进程,使用`kill`命令停止它。**步骤4:检查锁文件**锁文件位于数据目录中,通常名为`node.lock`。如果确认没有其他节点在运行,可以删除这个文件。```bashrm/path/to/elasticsearch/data/*/node.lock```注意:数据目录下可能有多个集群名称的目录,进入相应的集群目录删除`node.lock`,或者直接删除整个数据目录下的所有`node.lock`。**步骤5:配置`node.max_local_storage_nodes`(如果需要)**在`elasticsearch.yml`中,如果你确实需要在一个数据目录上运行多个节点(例如测试环境),可以设置:```yamlnode.max_local_storage_nodes:2#根据需要的节点数设置```但请注意,生产环境不建议这样做,因为可能会造成数据损坏。**步骤6:检查数据目录是否在可写文件系统上**使用`df`命令查看挂载点,并使用`touch`测试写入。**步骤7:如果问题仍然存在,考虑重建数据目录**如果数据不重要,可以尝试备份配置后,删除整个数据目录,然后重新启动Elasticsearch,让它重新初始化数据目录。另外,引用[3]提供了下载和安装Elasticsearch的步骤,但用户已经安装,这里不需要重复。总结解决步骤:1.确保以非root用户运行。2.确保数据目录权限正确。3.停止占用同一数据目录的其他节点进程。4.删除残留的`node.lock`文件。5.如果需要多个节点共享同一数据目录,配置`node.max_local_storage_nodes`(一般不推荐)。6.如果以上步骤无效,考虑清理数据目录。最后,启动Elasticsearch:```bashsuelasticsearchcd/path/to/elasticsearch-7.17.14./bin/elasticsearch```如果启动成功,问题解决。相关问题:1.如何为Elasticsearch创建专用用户并设置权限?2.Elasticsearch的数据目录结构是怎样的?3.如何配置Elasticsearch的数据路径?4.为什么Elasticsearch不允许以root用户运行?</think>### 解决 Elasticsearch 7.17.14 "failed to obtain node locks" 错误 此错误表明 Elasticsearch 无法获取数据目录的独占访问权限,通常由以下原因引起: #### 核心解决步骤 1. **终止残留进程** ```bash # 查找并杀死所有 Elasticsearch 进程 ps aux | grep elasticsearch | awk '{print $2}' | xargs kill -9 ``` 2. **删除残留锁文件** ```bash # 删除所有 node.lock 文件(替换为你的实际数据目录) rm -f /home/elk/elastic/elasticsearch-7.17.14/data/*/node.lock ``` 3. **验证目录权限** ```bash # 确保数据目录可写(使用运行 ES 的用户) chown -R elasticsearch_user:elasticsearch_group /home/elk/elastic/elasticsearch-7.17.14/data chmod 755 /home/elk/elastic/elasticsearch-7.17.14/data ``` 4. **检查多节点冲突配置** 在 `elasticsearch.yml` 中确认: ```yaml # 确保单节点配置(默认值) node.max_local_storage_nodes: 1 ``` 5. **处理挂载点问题** ```bash # 检查目录挂载状态 df -h /home/elk/elastic/elasticsearch-7.17.14/data # 如果是挂载点,确保已正确挂载 mount | grep elasticsearch ``` #### 高级解决方案 **情况1:多节点冲突** ```yaml # 在 elasticsearch.yml 中明确设置节点名称 node.name: node-1 # 如果确实需要多节点共享目录 node.max_local_storage_nodes: 3 # 改为实际节点数 ``` **情况2:磁盘空间不足** ```bash # 检查磁盘空间 df -h /home/elk/elastic # 清理旧数据(谨慎操作) find /home/elk/elastic/data -name "*.log" -mtime +30 -exec rm {} \; ``` **情况3:SELinux 限制** ```bash # 临时禁用 SELinux(测试用) setenforce 0 # 永久解决方案 semanage fcontext -a -t elasticsearch_data_t '/home/elk/elastic/data(/.*)?' restorecon -Rv /home/elk/elastic/data ``` #### 验证修复 ```bash # 启动并跟踪日志 sudo -u elasticsearch_user ./bin/elasticsearch | grep "locked" ``` 成功启动后将显示: ``` [node-1] recovered [0] indices into cluster_state ``` #### 配置示例 `elasticsearch.yml` 关键配置: ```yaml # 数据目录配置 path: data: /home/elk/elastic/data logs: /home/elk/elastic/logs # 单节点模式(开发用) discovery.type: single-node # 明确设置节点名称 node.name: ${HOSTNAME} ``` #### 预防措施 1. 使用专用数据目录,避免多服务共享 2. 添加启动前清理脚本: ```bash # pre_start_clean.sh rm -f /home/elk/elastic/data/*/node.lock pkill -f 'java.*elasticsearch' ``` 3. 定期监控磁盘空间和inode使用率 ### 相关问题 1. 如何安全地迁移 Elasticsearch 数据目录到新位置? 2.Docker 中运行 Elasticsearch 时如何避免节点锁问题? 3. Elasticsearch 集群模式下如何管理节点锁冲突? 4. 如何诊断 Elasticsearch 启动时的权限问题? 5. 使用 systemd 管理 Elasticsearch 时如何配置自动恢复? > **提示**:生产环境建议使用独立数据磁盘,并配置监控告警规则检测 `disk_space` 和 `file_descriptors` 指标[^1][^2]。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值