http://blog.sina.com.cn/s/blog_8ea8e9d50102wwik.html

Docker部署Elasticsearch集群
参考文档:
 
 
 
环境:
CentOS 7.2
docker-engine-1.11.2
elasticsearch-2.3.3
 
 
前言:
虚拟机节点部署请参看Elasticsearch 负载均衡集群，这里简单介绍下docker部署
 

本实验采用不同类型的节点集群(client x1, master x3, data x2)

ela-client.example.com:192.168.8.10(client node)
ela-master1.example.com:192.168.8.101(master node)
ela-master2.example.com:192.168.8.102(master node)
ela-master3.example.com:192.168.8.103(master node)
ela-data1.example.com:192.168.8.201(data node)
ela-data2.example.com:192.168.8.202(data node)
 
 
一.安装docker-engine(所有节点)
docker镜像加速请参看Docker Hub加速及私有镜像搭建
 
 
二.获取elasticsearch docker镜像
docker pull elasticsearch:2.3.3
 
测试运行elasticsearch
docker run -d -p 9200:9200 -p 9300:9300 --name=elasticsearch-test elasticsearch:2.3.3
查看容器配置
docker inspect elasticsearch-test
删除测试容器
docker rm -f $(docker ps -aq)
提示:对于持续增长的目录或文件可以通过映射到docker主机来提高可定制性，如data,logs
 
 
三.配置并启动节点
创建集群名为elasticsearch_cluster的集群(默认的集群名为elasticsearch)
A.client node
ela-client.example.com:192.168.8.10(client node)

docker run -d --restart=always -p 9200:9200 -p 9300:9300 --name=elasticsearch-client --oom-kill-disable=true --memory-swappiness=1 -v /opt/elasticsearch/data:/usr/share/elasticsearch/data -v /opt/elasticsearch/logs:/usr/share/elasticsearch/logs elasticsearch:2.3.3

cat >elasticsearch.yml <<HERE

cluster.name: elasticsearch_cluster

node.name: ${HOSTNAME}

node.master: false

node.data: false

path.data: /usr/share/elasticsearch/data

path.logs: /usr/share/elasticsearch/logs

bootstrap.mlockall: true

network.host: 0.0.0.0

network.publish_host: 192.168.8.10

transport.tcp.port: 9300

http.port: 9200

index.refresh_interval: 5s

script.inline: true

script.indexed: true

HERE
docker cp elasticsearch.yml elasticsearch-client:/usr/share/elasticsearch/config/elasticsearch.yml

docker restart elasticsearch-client

直接将修改好的配置文件cp到容器对应位置后重启容器

man docker-run

       --net="bridge"

          Set the Network mode for the container

                                      'bridge': create a network stack on the default Docker bridge

                                      'none': no networking

                                      'container:': reuse another container's network stack

                                      'host': use the Docker host network stack. Note: the host mode gives the container full access to local system services such as D-bus and is  therefore  consid‐

       ered insecure.

说明:docker默认的网络模式为bridge,会自动为容器分配一个私有地址，如果是多台宿主机之间集群通信需要借助Consul,Etcd,Doozer等服务发现，自动注册组件来协同。请参看Docker集群之Swarm+Consul+Shipyard

必须通过network.publish_host: 192.168.8.10参数指定elasticsearch节点对外的监听地址,非常重要,不指定的话,集群节点间无法正常通信,报错如下

[2016-06-21 05:50:19,123][INFO ][discovery.zen ] [consul-s2.example.com] failed to send join request to master[{consul-s1.example.com}{DeKixlVMS2yoynzX8Y-gdA}{172.17.0.1}{172.17.0.1:9300}{data=false, master=true}], reason [RemoteTransportException[[consul-s2.example.com][172.17.0.1:9300]

最简单的，还可以网络直接设为host模式--net=host，直接借用宿主机的网络接口,换言之,不做网络层的layer

同时可禁用OOM，还可根据宿主机内存来设置-m参数(默认为0，无限)限制容器内存大小

[root@ela-client ~]# docker ps

CONTAINER ID        IMAGE                 COMMAND                  CREATED             STATUS              PORTS               NAMES

762e4d21aaf8        elasticsearch:2.3.3   "/docker-entrypoint.s"   2 minutes ago       Up 2 minutes                            elasticsearch-client

[root@ela-client ~]# netstat -tunlp|grep java

tcp        0      0 0.0.0.0:9200            0.0.0.0:*               LISTEN      18952/java

tcp        0      0 0.0.0.0:9300            0.0.0.0:*               LISTEN      18952/java

[root@ela-client ~]# ls /opt/elasticsearch/

data  logs

[root@ela-client ~]# docker logs $(docker ps -q)

[2016-06-13 16:09:51,308][INFO ][node                     ] [Sunfire] version[2.3.3], pid[1], build[218bdf1/2016-05-17T15:40:04Z]

[2016-06-13 16:09:51,311][INFO ][node                     ] [Sunfire] initializing ...

... ...

[2016-06-13 16:09:56,408][INFO ][node                     ] [Sunfire] started

[2016-06-13 16:09:56,417][INFO ][gateway                  ] [Sunfire] recovered [0] indices into cluster_state

 
或者
卷映射,个人认为卷映射更便于管理与备份
mkdir -p /opt/elasticsearch/config

cat >/opt/elasticsearch/config/elasticsearch.yml <<HERE

cluster.name: elasticsearch_cluster

node.name: ${HOSTNAME}

node.master: false

node.data: false

path.data: /usr/share/elasticsearch/data

path.logs: /usr/share/elasticsearch/logs

bootstrap.mlockall: true

network.host: 0.0.0.0

network.publish_host: 192.168.8.10

transport.tcp.port: 9300

http.port: 9200

index.refresh_interval: 5s

script.inline: true

script.indexed: true

HERE
docker run -tid --restart=always \
    -p 9200:9200 \
    -p 9300:9300 \
    --oom-kill-disable=true \
    --memory-swappiness=1 \
    -v /opt/elasticsearch/data:/usr/share/elasticsearch/data \
    -v /opt/elasticsearch/logs:/usr/share/elasticsearch/logs \
    -v /opt/elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
    --name=elasticsearch-client \
    elasticsearch:2.3.3
 
B.master node
ela-master1.example.com:192.168.8.101(master node)
mkdir -p /opt/elasticsearch/config

cat >/opt/elasticsearch/config/elasticsearch.yml <<HERE

cluster.name: elasticsearch_cluster

node.name: ${HOSTNAME}

node.master: true

node.data: false

path.data: /usr/share/elasticsearch/data

path.logs: /usr/share/elasticsearch/logs

bootstrap.mlockall: true

network.host: 0.0.0.0

network.publish_host: 192.168.8.101

transport.tcp.port: 9300

http.port: 9200

index.refresh_interval: 5s

script.inline: true

script.indexed: true

HERE
docker run -tid --restart=always \
    -p 9200:9200 \
    -p 9300:9300 \
    --oom-kill-disable=true \
    --memory-swappiness=1 \
    -v /opt/elasticsearch/data:/usr/share/elasticsearch/data \
    -v /opt/elasticsearch/logs:/usr/share/elasticsearch/logs \
    -v /opt/elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
    --name=elasticsearch-master1 \
    elasticsearch:2.3.3
ela-master2.example.com:192.168.8.102(master node)
mkdir -p /opt/elasticsearch/config

cat >/opt/elasticsearch/config/elasticsearch.yml <<HERE

cluster.name: elasticsearch_cluster

node.name: ${HOSTNAME}

node.master: true

node.data: false

path.data: /usr/share/elasticsearch/data

path.logs: /usr/share/elasticsearch/logs

bootstrap.mlockall: true

network.host: 0.0.0.0

network.publish_host: 192.168.8.102

transport.tcp.port: 9300

http.port: 9200

index.refresh_interval: 5s

script.inline: true

script.indexed: true

HERE
docker run -tid --restart=always \
    -p 9200:9200 \
    -p 9300:9300 \
    --oom-kill-disable=true \
    --memory-swappiness=1 \
    -v /opt/elasticsearch/data:/usr/share/elasticsearch/data \
    -v /opt/elasticsearch/logs:/usr/share/elasticsearch/logs \
    -v /opt/elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
    --name=elasticsearch-master2 \
    elasticsearch:2.3.3
ela-master3.example.com:192.168.8.103(master node)
mkdir -p /opt/elasticsearch/config

cat >/opt/elasticsearch/config/elasticsearch.yml <<HERE

cluster.name: elasticsearch_cluster

node.name: ${HOSTNAME}

node.master: true

node.data: false

path.data: /usr/share/elasticsearch/data

path.logs: /usr/share/elasticsearch/logs

bootstrap.mlockall: true

network.publish_host: 192.168.8.103

transport.tcp.port: 9300

network.host: 0.0.0.0

http.port: 9200

index.refresh_interval: 5s

script.inline: true

script.indexed: true

HERE
docker run -tid --restart=always \
    -p 9200:9200 \
    -p 9300:9300 \
    --oom-kill-disable=true \
    --memory-swappiness=1 \
    -v /opt/elasticsearch/data:/usr/share/elasticsearch/data \
    -v /opt/elasticsearch/logs:/usr/share/elasticsearch/logs \
    -v /opt/elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
    --name=elasticsearch-master3 \
    elasticsearch:2.3.3
 
C.data node
ela-data1.example.com:192.168.8.201(data node)
mkdir -p /opt/elasticsearch/config

cat >/opt/elasticsearch/config/elasticsearch.yml <<HERE

cluster.name: elasticsearch_cluster

node.name: ${HOSTNAME}

node.master: false

node.data: true

path.data: /usr/share/elasticsearch/data

path.logs: /usr/share/elasticsearch/logs

bootstrap.mlockall: true

network.publish_host: 192.168.8.201

transport.tcp.port: 9300

network.host: 0.0.0.0

http.port: 9200

index.refresh_interval: 5s

script.inline: true

script.indexed: true

HERE
docker run -tid --restart=always \
    -p 9200:9200 \
    -p 9300:9300 \
    --oom-kill-disable=true \
    --memory-swappiness=1 \
    -v /opt/elasticsearch/data:/usr/share/elasticsearch/data \
    -v /opt/elasticsearch/logs:/usr/share/elasticsearch/logs \
    -v /opt/elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
    --name=elasticsearch-data1 \
    elasticsearch:2.3.3
ela-data2.example.com:192.168.8.202(data node)
mkdir -p /opt/elasticsearch/config

cat >/opt/elasticsearch/config/elasticsearch.yml <<HERE

cluster.name: elasticsearch_cluster

node.name: ${HOSTNAME}

node.master: false

node.data: true

path.data: /usr/share/elasticsearch/data

path.logs: /usr/share/elasticsearch/logs

bootstrap.mlockall: true

network.host: 0.0.0.0

network.publish_host: 192.168.8.202

transport.tcp.port: 9300

http.port: 9200

index.refresh_interval: 5s

script.inline: true

script.indexed: true

HERE
docker run -tid --restart=always \
    -p 9200:9200 \
    -p 9300:9300 \
    --oom-kill-disable=true \
    --memory-swappiness=1 \
    -v /opt/elasticsearch/data:/usr/share/elasticsearch/data \
    -v /opt/elasticsearch/logs:/usr/share/elasticsearch/logs \
    -v /opt/elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
    --name=elasticsearch-data2 \
    elasticsearch:2.3.3
 
 
四.配置集群(所有节点)

通过discovery模块来将节点加入集群

在以上节点的配置文件/opt/elasticsearch/config/elasticsearch.yml中加入如下行后重启

cat >>/opt/elasticsearch/config/elasticsearch.yml <<HERE

discovery.zen.ping.timeout: 100s

discovery.zen.fd.ping_timeout: 100s

discovery.zen.ping.multicast.enabled: false

discovery.zen.ping.unicast.hosts: ["192.168.8.101:9300", "192.168.8.102:9300", "192.168.8.103:9300", "192.168.8.201:9300", "192.168.8.202:9300","192.168.8.10:9300"]

HERE

docker restart $(docker ps -a|grep elasticsearch|awk '{print $1}')

 

 

五.确认集群

等待30s左右，集群节点会自动join,在集群的含意节点上都会看到如下类似输出，说明集群运行正常

REST API调用请参看Elasticsearch REST API小记

https://www.elastic.co/guide/en/elasticsearch/reference/current/_cluster_health.html

[root@ela-client ~]#curl 'http://localhost:9200/_cat/health?v'

epoch      timestamp cluster               status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent

1465843145 18:39:05  elasticsearch_cluster green           6         2      0   0    0    0        0             0                  -                100.0%

[root@ela-client ~]#curl 'localhost:9200/_cat/nodes?v'

host            ip              heap.percent ram.percent load node.role master name

192.168.8.102 192.168.8.102           14          99 0.00 -         *      ela-master2.example.com

192.168.8.103 192.168.8.103            4          99 0.14 -         m      ela-master3.example.com

192.168.8.202 192.168.8.202           11          99 0.00 d         -      ela-data2.example.com

192.168.8.10  192.168.8.10            10          98 0.17 -         -      ela-client.example.com

192.168.8.201 192.168.8.201           11          99 0.00 d         -      ela-data1.example.com

192.168.8.101 192.168.8.101           12          99 0.01 -         m      ela-master1.example.com

[root@ela-master2 ~]#curl 'http://localhost:9200/_nodes/process?pretty'

{

"cluster_name" : "elasticsearch_cluster",

"nodes" : {

"naMz_y4uRRO-FzyxRfTNjw" : {

"name" : "ela-data2.example.com",

"transport_address" : "192.168.8.202:9300",

"host" : "192.168.8.202",

"ip" : "192.168.8.202",

"version" : "2.3.3",

"build" : "218bdf1",

"http_address" : "192.168.8.202:9200",

"attributes" : {

"master" : "false"

},

"process" : {

"refresh_interval_in_millis" : 1000,

"id" : 1,

"mlockall" : false

}

},

"7FwFY20ESZaRtIWhYMfDAg" : {

"name" : "ela-data1.example.com",

"transport_address" : "192.168.8.201:9300",

"host" : "192.168.8.201",

"ip" : "192.168.8.201",

"version" : "2.3.3",

"build" : "218bdf1",

"http_address" : "192.168.8.201:9200",

"attributes" : {

"master" : "false"

},

"process" : {

"refresh_interval_in_millis" : 1000,

"id" : 1,

"mlockall" : false

}

},

"X0psLpQyR42A4ThiP8ilhA" : {

"name" : "ela-master3.example.com",

"transport_address" : "192.168.8.103:9300",

"host" : "192.168.8.103",

"ip" : "192.168.8.103",

"version" : "2.3.3",

"build" : "218bdf1",

"http_address" : "192.168.8.103:9200",

"attributes" : {

"data" : "false",

"master" : "true"

},

"process" : {

"refresh_interval_in_millis" : 1000,

"id" : 1,

"mlockall" : false

}

},

"MG_GlSAZRkqLq8gMqaZITw" : {

"name" : "ela-master1.example.com",

"transport_address" : "192.168.8.101:9300",

"host" : "192.168.8.101",

"ip" : "192.168.8.101",

"version" : "2.3.3",

"build" : "218bdf1",

"http_address" : "192.168.8.101:9200",

"attributes" : {

"data" : "false",

"master" : "true"

},

"process" : {

"refresh_interval_in_millis" : 1000,

"id" : 1,

"mlockall" : false

}

},

"YxNHUPqVRNK3Liilw_hU9A" : {

"name" : "ela-master2.example.com",

"transport_address" : "192.168.8.102:9300",

"host" : "192.168.8.102",

"ip" : "192.168.8.102",

"version" : "2.3.3",

"build" : "218bdf1",

"http_address" : "192.168.8.102:9200",

"attributes" : {

"data" : "false",

"master" : "true"

},

"process" : {

"refresh_interval_in_millis" : 1000,

"id" : 1,

"mlockall" : false

}

},

"zTKJJ4ipQg6xAcwy1aE-9g" : {

"name" : "ela-client.example.com",

"transport_address" : "192.168.8.10:9300",

"host" : "192.168.8.10",

"ip" : "192.168.8.10",

"version" : "2.3.3",

"build" : "218bdf1",

"http_address" : "192.168.8.10:9200",

"attributes" : {

"data" : "false",

"master" : "true"

},

"process" : {

"refresh_interval_in_millis" : 1000,

"id" : 1,

"mlockall" : false

}

}

}

}

问题:

修改jvm内存,初始值-Xms256m -Xmx1g

https://hub.docker.com/r/itzg/elasticsearch/

https://hub.docker.com/_/elasticsearch/

实测:修改JAVA_OPTS,ES_JAVA_OPTS都只能追加，而不能覆盖，只能通过

-e ES_HEAP_SIZE="32g" 来覆盖



补充:

head,Marvel等监控可视化插件有兴趣的朋友可以试下

Docker部署Elasticsearch集群的更多相关文章

  1. Centos8 Docker部署ElasticSearch集群

    ELK部署 部署ElasticSearch集群 1.拉取镜像及批量生成配置文件 # 拉取镜像 [root@VM-24-9-centos ~]# docker pull elasticsearch:7. ...

  2. 利用 docker 部署 elasticsearch 集群（单节点多实例）

    文章目录 1.环境介绍 2.拉取 `elasticserach` 镜像 3.创建 `elasticsearch` 数据目录 4.创建 `elasticsearch` 配置文件 5.配置JVM线程数量限 ...

  3. Centos8 部署 ElasticSearch 集群并搭建 ELK，基于Logstash同步MySQL数据到ElasticSearch

    Centos8安装Docker 1.更新一下yum [root@VM-24-9-centos ~]# yum -y update 2.安装containerd.io # centos8默认使用podm ...

  4. 日志分析系统 - k8s部署ElasticSearch集群

    K8s部署ElasticSearch集群 1.前提准备工作 1.1 创建elastic的命名空间 namespace编排文件如下: elastic.namespace.yaml --- apiVers ...

  5. Docker部署Hadoop集群

    Docker部署Hadoop集群 2016-09-27 杜亦舒 前几天写了文章"Hadoop 集群搭建"之后,一个朋友留言说希望介绍下如何使用Docker部署,这个建议很好,Doc ...

  6. Azure vm 扩展脚本自动部署Elasticsearch集群

    一.完整过程比较长,我仅给出Azure vm extension script 一键部署Elasticsearch集群的安装脚本,有需要的同学,可以邮件我,我给你完整的ARM Template 如果你 ...

  7. 基于Docker部署ETCD集群

    基于Docker部署ETCD集群 关于ETCD要不要使用TLS? 首先TLS的目的是为了鉴权为了防止别人任意的连接上你的etcd集群.其实意思就是说如果你要放到公网上的ETCD集群,并开放端口,我建议 ...

  8. Docker部署zookeeper集群和kafka集群，实现互联

    本文介绍在单机上通过docker部署zookeeper集群和kafka集群的可操作方案. 0.准备工作 创建zk目录,在该目录下创建生成zookeeper集群和kafka集群的yml文件,以及用于在该 ...

  9. Elasticsearch使用系列-Docker搭建Elasticsearch集群

    Elasticsearch使用系列-ES简介和环境搭建 Elasticsearch使用系列-ES增删查改基本操作+ik分词 Elasticsearch使用系列-基本查询和聚合查询+sql插件 Elas ...

随机推荐

  1. Java的按位操作符

    本文参考:Java的位操作符 Java的位操作符用来操作整数基本数据类型中的单个"比特"(bit),即代进制位.而我们知道比特就是0和1,那么,位操作就是对这些数据进行基本的操作. ...

  2. Tsung脚本中使用动态参数（一）---直接在脚本里编写Erlang代码

    杀死一个程序猿,只要改三次需求.同理,杀死一个接口自动化测试人员,只要改三次接口数据处理方式.我目前的状态,改了一次接口数据处理方式,有一种胸闷的感觉. 因为改需求,所以,要改脚本.T_T.所以,才有 ...

  3. Lua和C的语法差别

    没有main函数 Lua是脚本语言,没有固定入口的main函数.当lua解析器解析某个lua代码文件时,lua解析器一样一行的解析lua脚本. print("Hello lua") ...

  4. 实体处理模块IEntityModule

    在2015年7月16日,XCode新增了实体处理模块IEntityModule,用于拦截实体对象添删改操作. 该接口参考IHttpModule设计理念,横切在实体对象的关键生命周期之中,以达到多实体类 ...

  5. Windows下使用pip安装mysql-python

    安装的过程很煎熬,留个爪,希望对其他人有帮助. 先声明我安装前的电脑配置: Win10: Python2和Python3共存(备注一个好用的方法,感谢知乎大神:https://www.zhihu.co ...

  6. Elixir的Phoenix框架：请求处理之道

    本文基于Phoenix1.3,但请求的处理流程跟1.2基本一致,只是模块的命名和目录结构有所差异. 简单介绍,phoenix是一个网站框架,本质就是http请求处理.这篇文章主要就是讲一个请求,在结果 ...

  7. windows c++程序移植到linux的要点

    这段时间得到一份源码,是Windows下的,调试了一把,可以正常运行,可是没有Linux版本,而实际的应用场景是要在Linux服务器上面运行 所以涉及到Windows下c++程序的移植,有同事竭力推荐 ...

  8. Flask中的单例模式

    1,基于文件的单例模式: import pymysql import threading from DBUtils.PooledDB import PooledDB class SingletonDB ...

  9. CTF---密码学入门第六题 古典密码

    古典密码分值:10 来源: 北邮天枢战队 难度:易 参与人数:5115人 Get Flag:1549人 答题人数:1783人 解题通过率:87% 密文内容如下{79 67 85 123 67 70 8 ...

  10. Codeforces Round #345(Div. 2)-651A.水题 651B.。。。 651C.去重操作 真是让人头大

    A. Joysticks time limit per test 1 second memory limit per test 256 megabytes input standard input o ...