研究目標
- Elastic 能否做到 Solr 的 Edismax
- 達到的情境:根據 List 的算法跟 String 算法是否一致
- 權重的分布情況
Docker 單節點運行指令
docker run -d --name elasticsearch -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" -e "xpack.security.enabled=false" -v es_data:/usr/share/elasticsearch/data elasticsearch:8.17.0
Docker 集群配置 (docker-compose)
version: '3'
services:
elasticsearch-node1:
image: docker.elastic.co/elasticsearch/elasticsearch:8.17.0
environment:
- discovery.type=zen-disco
- discovery.seed_hosts=elasticsearch-node1,elasticsearch-node2,elasticsearch-node3
- cluster.initial_master_nodes=elasticsearch-node1,elasticsearch-node2,elasticsearch-node3
- xpack.security.enabled=false
volumes:
- es_data1:/usr/share/elasticsearch/data
networks:
- elasticsearch-net
ports:
- "9200:9200"
- "9300:9300"
elasticsearch-node2:
image: docker.elastic.co/elasticsearch/elasticsearch:8.17.0
environment:
- discovery.type=zen-disco
- discovery.seed_hosts=elasticsearch-node1,elasticsearch-node2,elasticsearch-node3
- cluster.initial_master_nodes=elasticsearch-node1,elasticsearch-node2,elasticsearch-node3
- xpack.security.enabled=false
volumes:
- es_data2:/usr/share/elasticsearch/data
networks:
- elasticsearch-net
ports:
- "9201:9200"
- "9301:9300"
elasticsearch-node3:
image: docker.elastic.co/elasticsearch/elasticsearch:8.17.0
environment:
- discovery.type=zen-disco
- discovery.seed_hosts=elasticsearch-node1,elasticsearch-node2,elasticsearch-node3
- cluster.initial_master_nodes=elasticsearch-node1,elasticsearch-node2,elasticsearch-node3
- xpack.security.enabled=false
volumes:
- es_data3:/usr/share/elasticsearch/data
networks:
- elasticsearch-net
ports:
- "9202:9200"
- "9302:9300"
networks:
elasticsearch-net:
driver: bridge
volumes:
es_data1:
es_data2:
es_data3:
啟動集群: