mirror of
https://github.com/Graylog2/graylog2-server.git
synced 2026-03-13 09:32:21 +08:00
66 lines
2.4 KiB
YAML
66 lines
2.4 KiB
YAML
# this must be the same as for your elasticsearch cluster
|
|
cluster.name: graylog
|
|
|
|
# you could also leave this out, but makes it easier to identify the Graylog embedded Elasticsearch node
|
|
node.name: "graylog-server"
|
|
|
|
# we don't want the graylog2 client to store any data, or be master node
|
|
node.master: false
|
|
node.data: false
|
|
|
|
# you might need to bind to a certain IP address, do that here
|
|
#network.host: 172.24.0.14
|
|
# use a different port if you run multiple elasticsearch nodes on one machine
|
|
transport.tcp.port: 9350
|
|
|
|
# we don't need to run the embedded HTTP server here
|
|
http.enabled: false
|
|
|
|
# adapt these for discovery to work in your network! multicast can be tricky
|
|
#discovery.zen.ping.multicast.address: 172.24.0.14
|
|
#discovery.zen.ping.multicast.group: 224.0.0.1
|
|
|
|
|
|
################################## Discovery ##################################
|
|
|
|
# Discovery infrastructure ensures nodes can be found within a cluster
|
|
# and master node is elected. Multicast discovery is the default.
|
|
|
|
# Set to ensure a node sees N other master eligible nodes to be considered
|
|
# operational within the cluster. Set this option to a higher value (2-4)
|
|
# for large clusters (>3 nodes):
|
|
#
|
|
# discovery.zen.minimum_master_nodes: 1
|
|
|
|
# Set the time to wait for ping responses from other nodes when discovering.
|
|
# Set this option to a higher value on a slow or congested network
|
|
# to minimize discovery failures:
|
|
#
|
|
# discovery.zen.ping.timeout: 3s
|
|
|
|
# See <http://elasticsearch.org/guide/reference/modules/discovery/zen.html>
|
|
# for more information.
|
|
|
|
# Unicast discovery allows to explicitly control which nodes will be used
|
|
# to discover the cluster. It can be used when multicast is not present,
|
|
# or to restrict the cluster communication-wise.
|
|
#
|
|
# 1. Disable multicast discovery (enabled by default):
|
|
#
|
|
# discovery.zen.ping.multicast.enabled: false
|
|
#
|
|
# 2. Configure an initial list of master nodes in the cluster
|
|
# to perform discovery when new nodes (master or data) are started:
|
|
#
|
|
# discovery.zen.ping.unicast.hosts: ["host1", "host2:port", "host3[portX-portY]"]
|
|
|
|
# EC2 discovery allows to use AWS EC2 API in order to perform discovery.
|
|
#
|
|
# You have to install the cloud-aws plugin for enabling the EC2 discovery.
|
|
#
|
|
# See <http://elasticsearch.org/guide/reference/modules/discovery/ec2.html>
|
|
# for more information.
|
|
#
|
|
# See <http://elasticsearch.org/tutorials/2011/08/22/elasticsearch-on-ec2.html>
|
|
# for a step-by-step tutorial.
|