简体   繁体   English

使用 kubernetes 在生产环境中使用 Elasticsearch

[英]Elasticsearch in production with kubernetes

I am working on product in which we are using elasticsearch for search.我正在开发我们使用 elasticsearch 进行搜索的产品。 Our production setup is in K8S (1.7.7) and we are able to scale it pretty well.我们的生产设置是在 K8S (1.7.7) 中,我们能够很好地扩展它。 Only thing I am not sure about is whether we should be hosting elasticsearch in k8s (it can go on dedicated host as well using label selector nodes) or it is advisable to host elasticsearch on VM than docker.我唯一不确定的是我们是否应该在 k8s 中托管 elasticsearch(它也可以使用标签选择器节点在专用主机上运行),或者建议在 VM 上托管 elasticsearch 而不是 docker。 Our data set size is 2-3 GB and would go further.我们的数据集大小为 2-3 GB,并且会更进一步。 But this is the benchmark we can consider.但这是我们可以考虑的基准。 And elasticsearch cluster I am planning to have ti is - 3 master (with 2 as eligible master), one client node, and one data node.我计划拥有 ti is - 3 个 master(其中 2 个作为合格的 master)、一个客户端节点和一个数据节点的 elasticsearch 集群。 We can scale datanode and client node as data increases.随着数据的增加,我们可以扩展数据节点和客户端节点。 Is anyone did this before?以前有人这样做过吗? thanks in advance.提前致谢。

IMO the best resource for Elasticsearch on Kubernetes is https://github.com/pires/kubernetes-elasticsearch-cluster IMO Kubernetes 上 Elasticsearch 的最佳资源是https://github.com/pires/kubernetes-elasticsearch-cluster

Note that while there are official Docker containers, no official solution for orchestration is being provided at the moment.请注意,虽然有官方的 Docker 容器,但目前没有提供官方的编排解决方案。 This is currently covered by the community only.这目前仅由社区涵盖。

3 master (with 2 as eligible master) 3 位大师(其中 2 位为合格的大师)

This doesn't make much sense.这没有多大意义。 You'll want 3 master eligible nodes with the setting discovery.zen.minimum_master_nodes: 2 and one of the 3 nodes will be the actual master.您需要 3 个符合主节点的节点,设置为discovery.zen.minimum_master_nodes: 2并且 3 个节点之一将是实际的主节点。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM