Guest User

1.7.1

a guest
Nov 2nd, 2016
76
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.81 KB | None | 0 0
  1. ##################### Elasticsearch Configuration Example #####################
  2.  
  3. # This file contains an overview of various configuration settings,
  4. # targeted at operations staff. Application developers should
  5. # consult the guide at <http://elasticsearch.org/guide>.
  6. #
  7. # The installation procedure is covered at
  8. # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
  9. #
  10. # Elasticsearch comes with reasonable defaults for most settings,
  11. # so you can try it out without bothering with configuration.
  12. #
  13. # Most of the time, these defaults are just fine for running a production
  14. # cluster. If you're fine-tuning your cluster, or wondering about the
  15. # effect of certain configuration option, please _do ask_ on the
  16. # mailing list or IRC channel [http://elasticsearch.org/community].
  17.  
  18. # Any element in the configuration can be replaced with environment variables
  19. # by placing them in ${...} notation. For example:
  20. #
  21. #node.rack: ${RACK_ENV_VAR}
  22.  
  23. # For information on supported formats and syntax for the config file, see
  24. # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html>
  25.  
  26.  
  27. ################################### Cluster ###################################
  28.  
  29. # Cluster name identifies your cluster for auto-discovery. If you're running
  30. # multiple clusters on the same network, make sure you're using unique names.
  31. #
  32. #cluster.name: elasticsearch
  33. cluster.name: "graylog2b"
  34.  
  35. #################################### Node #####################################
  36.  
  37. # Node names are generated dynamically on startup, so you're relieved
  38. # from configuring them manually. You can tie this node to a specific name:
  39. #
  40. #node.name: "Franz Kafka"
  41. node.name: "graylog2b-server"
  42.  
  43. # Every node can be configured to allow or deny being eligible as the master,
  44. # and to allow or deny to store the data.
  45. #
  46. # Allow this node to be eligible as a master node (enabled by default):
  47. #
  48. node.master: true
  49. #
  50. # Allow this node to store data (enabled by default):
  51. #
  52. node.data: true
  53.  
  54. # You can exploit these settings to design advanced cluster topologies.
  55. #
  56. # 1. You want this node to never become a master node, only to hold data.
  57. # This will be the "workhorse" of your cluster.
  58. #
  59. #node.master: false
  60. #node.data: true
  61. #
  62. # 2. You want this node to only serve as a master: to not store any data and
  63. # to have free resources. This will be the "coordinator" of your cluster.
  64. #
  65. #node.master: true
  66. #node.data: false
  67. #
  68. # 3. You want this node to be neither master nor data node, but
  69. # to act as a "search load balancer" (fetching data from nodes,
  70. # aggregating results, etc.)
  71. #
  72. #node.master: false
  73. #node.data: false
  74.  
  75. # Use the Cluster Health API [http://localhost:9200/_cluster/health], the
  76. # Node Info API [http://localhost:9200/_nodes] or GUI tools
  77. # such as <http://www.elasticsearch.org/overview/marvel/>,
  78. # <http://github.com/karmi/elasticsearch-paramedic>,
  79. # <http://github.com/lukas-vlcek/bigdesk> and
  80. # <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.
  81.  
  82. # A node can have generic attributes associated with it, which can later be used
  83. # for customized shard allocation filtering, or allocation awareness. An attribute
  84. # is a simple key value pair, similar to node.key: value, here is an example:
  85. #
  86. #node.rack: rack314
  87.  
  88. # By default, multiple nodes are allowed to start from the same installation location
  89. # to disable it, set the following:
  90. #node.max_local_storage_nodes: 1
  91.  
  92.  
  93. #################################### Index ####################################
  94.  
  95. # You can set a number of options (such as shard/replica options, mapping
  96. # or analyzer definitions, translog settings, ...) for indices globally,
  97. # in this file.
  98. #
  99. # Note, that it makes more sense to configure index settings specifically for
  100. # a certain index, either when creating it or by using the index templates API.
  101. #
  102. # See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and
  103. # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html>
  104. # for more information.
  105.  
  106. # Set the number of shards (splits) of an index (5 by default):
  107. #
  108. #index.number_of_shards: 5
  109.  
  110. # Set the number of replicas (additional copies) of an index (1 by default):
  111. #
  112. #index.number_of_replicas: 1
  113.  
  114. # Note, that for development on a local machine, with small indices, it usually
  115. # makes sense to "disable" the distributed features:
  116. #
  117. index.number_of_shards: 1
  118. index.number_of_replicas: 0
  119.  
  120. # These settings directly affect the performance of index and search operations
  121. # in your cluster. Assuming you have enough machines to hold shards and
  122. # replicas, the rule of thumb is:
  123. #
  124. # 1. Having more *shards* enhances the _indexing_ performance and allows to
  125. # _distribute_ a big index across machines.
  126. # 2. Having more *replicas* enhances the _search_ performance and improves the
  127. # cluster _availability_.
  128. #
  129. # The "number_of_shards" is a one-time setting for an index.
  130. #
  131. # The "number_of_replicas" can be increased or decreased anytime,
  132. # by using the Index Update Settings API.
  133. #
  134. # Elasticsearch takes care about load balancing, relocating, gathering the
  135. # results from nodes, etc. Experiment with different settings to fine-tune
  136. # your setup.
  137.  
  138. # Use the Index Status API (<http://localhost:9200/A/_status>) to inspect
  139. # the index status.
  140.  
  141.  
  142. #################################### Paths ####################################
  143.  
  144. # Path to directory containing configuration (this file and logging.yml):
  145. #
  146. #path.conf: /path/to/conf
  147.  
  148. # Path to directory where to store index data allocated for this node.
  149. #
  150. #path.data: /path/to/data
  151. #
  152. # Can optionally include more than one location, causing data to be striped across
  153. # the locations (a la RAID 0) on a file level, favouring locations with most free
  154. # space on creation. For example:
  155. #
  156. path.data: /logs/index
  157.  
  158. # Path to temporary files:
  159. #
  160. path.work: /logs/work
  161.  
  162. # Path to log files:
  163. #
  164. path.logs: /logs/logfiles
  165.  
  166. # Path to where plugins are installed:
  167. #
  168. path.plugins: /opt/elasticsearch-1.7.1/plugins
  169.  
  170.  
  171. #################################### Plugin ###################################
  172.  
  173. # If a plugin listed here is not installed for current node, the node will not start.
  174. #
  175. #plugin.mandatory: mapper-attachments,lang-groovy
  176.  
  177.  
  178. ################################### Memory ####################################
  179.  
  180. # Elasticsearch performs poorly when JVM starts swapping: you should ensure that
  181. # it _never_ swaps.
  182. #
  183. # Set this property to true to lock the memory:
  184. #
  185. bootstrap.mlockall: true
  186.  
  187. # Make sure that the ES_MIN_MEM and ES_MAX_MEM environment variables are set
  188. # to the same value, and that the machine has enough memory to allocate
  189. # for Elasticsearch, leaving enough memory for the operating system itself.
  190. #
  191. # You should also make sure that the Elasticsearch process is allowed to lock
  192. # the memory, eg. by using `ulimit -l unlimited`.
  193.  
  194.  
  195. ############################## Network And HTTP ###############################
  196.  
  197. # Elasticsearch, by default, binds itself to the 0.0.0.0 address, and listens
  198. # on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node
  199. # communication. (the range means that if the port is busy, it will automatically
  200. # try the next port).
  201.  
  202. # Set the bind address specifically (IPv4 or IPv6):
  203. #
  204. network.bind_host: 10.0.0.29
  205.  
  206. # Set the address other nodes will use to communicate with this node. If not
  207. # set, it is automatically derived. It must point to an actual IP address.
  208. #
  209. network.publish_host: 10.0.0.29
  210.  
  211. # Set both 'bind_host' and 'publish_host':
  212. #
  213. network.host: 10.0.0.29
  214.  
  215. # Set a custom port for the node to node communication (9300 by default):
  216. #
  217. transport.tcp.port: 9300
  218.  
  219. # Enable compression for all communication between nodes (disabled by default):
  220. #
  221. #transport.tcp.compress: true
  222.  
  223. # Set a custom port to listen for HTTP traffic:
  224. #
  225. http.port: 9200
  226.  
  227. # Set a custom allowed content length:
  228. #
  229. #http.max_content_length: 100mb
  230.  
  231. # Disable HTTP completely:
  232. #
  233. #http.enabled: false
  234.  
  235.  
  236. ################################### Gateway ###################################
  237.  
  238. # The gateway allows for persisting the cluster state between full cluster
  239. # restarts. Every change to the state (such as adding an index) will be stored
  240. # in the gateway, and when the cluster starts up for the first time,
  241. # it will read its state from the gateway.
  242.  
  243. # There are several types of gateway implementations. For more information, see
  244. # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>.
  245.  
  246. # The default gateway type is the "local" gateway (recommended):
  247. #
  248. #gateway.type: local
  249.  
  250. # Settings below control how and when to start the initial recovery process on
  251. # a full cluster restart (to reuse as much local data as possible when using shared
  252. # gateway).
  253.  
  254. # Allow recovery process after N nodes in a cluster are up:
  255. #
  256. #gateway.recover_after_nodes: 1
  257.  
  258. # Set the timeout to initiate the recovery process, once the N nodes
  259. # from previous setting are up (accepts time value):
  260. #
  261. #gateway.recover_after_time: 5m
  262.  
  263. # Set how many nodes are expected in this cluster. Once these N nodes
  264. # are up (and recover_after_nodes is met), begin recovery process immediately
  265. # (without waiting for recover_after_time to expire):
  266. #
  267. #gateway.expected_nodes: 2
  268.  
  269.  
  270. ############################# Recovery Throttling #############################
  271.  
  272. # These settings allow to control the process of shards allocation between
  273. # nodes during initial recovery, replica allocation, rebalancing,
  274. # or when adding and removing nodes.
  275.  
  276. # Set the number of concurrent recoveries happening on a node:
  277. #
  278. # 1. During the initial recovery
  279. #
  280. #cluster.routing.allocation.node_initial_primaries_recoveries: 4
  281. #
  282. # 2. During adding/removing nodes, rebalancing, etc
  283. #
  284. #cluster.routing.allocation.node_concurrent_recoveries: 2
  285.  
  286. # Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
  287. #
  288. #indices.recovery.max_bytes_per_sec: 20mb
  289.  
  290. # Set to limit the number of open concurrent streams when
  291. # recovering a shard from a peer:
  292. #
  293. #indices.recovery.concurrent_streams: 5
  294.  
  295.  
  296. ################################## Discovery ##################################
  297.  
  298. # Discovery infrastructure ensures nodes can be found within a cluster
  299. # and master node is elected. Multicast discovery is the default.
  300.  
  301. # Set to ensure a node sees N other master eligible nodes to be considered
  302. # operational within the cluster. This should be set to a quorum/majority of
  303. # the master-eligible nodes in the cluster.
  304. #
  305. #discovery.zen.minimum_master_nodes: 1
  306.  
  307. # Set the time to wait for ping responses from other nodes when discovering.
  308. # Set this option to a higher value on a slow or congested network
  309. # to minimize discovery failures:
  310. #
  311. #discovery.zen.ping.timeout: 3s
  312.  
  313. # For more information, see
  314. # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html>
  315.  
  316. # Unicast discovery allows to explicitly control which nodes will be used
  317. # to discover the cluster. It can be used when multicast is not present,
  318. # or to restrict the cluster communication-wise.
  319. #
  320. # 1. Disable multicast discovery (enabled by default):
  321. #
  322. discovery.zen.ping.multicast.enabled: false
  323. #
  324. # 2. Configure an initial list of master nodes in the cluster
  325. # to perform discovery when new nodes (master or data) are started:
  326. #
  327. discovery.zen.ping.unicast.hosts: 10.0.0.29:9300
  328.  
  329. # EC2 discovery allows to use AWS EC2 API in order to perform discovery.
  330. #
  331. # You have to install the cloud-aws plugin for enabling the EC2 discovery.
  332. #
  333. # For more information, see
  334. # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html>
  335. #
  336. # See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/>
  337. # for a step-by-step tutorial.
  338.  
  339. # GCE discovery allows to use Google Compute Engine API in order to perform discovery.
  340. #
  341. # You have to install the cloud-gce plugin for enabling the GCE discovery.
  342. #
  343. # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-gce>.
  344.  
  345. # Azure discovery allows to use Azure API in order to perform discovery.
  346. #
  347. # You have to install the cloud-azure plugin for enabling the Azure discovery.
  348. #
  349. # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-azure>.
  350.  
  351. ################################## Slow Log ##################################
  352.  
  353. # Shard level query and fetch threshold logging.
  354.  
  355. #index.search.slowlog.threshold.query.warn: 10s
  356. #index.search.slowlog.threshold.query.info: 5s
  357. #index.search.slowlog.threshold.query.debug: 2s
  358. #index.search.slowlog.threshold.query.trace: 500ms
  359.  
  360. #index.search.slowlog.threshold.fetch.warn: 1s
  361. #index.search.slowlog.threshold.fetch.info: 800ms
  362. #index.search.slowlog.threshold.fetch.debug: 500ms
  363. #index.search.slowlog.threshold.fetch.trace: 200ms
  364.  
  365. #index.indexing.slowlog.threshold.index.warn: 10s
  366. #index.indexing.slowlog.threshold.index.info: 5s
  367. #index.indexing.slowlog.threshold.index.debug: 2s
  368. #index.indexing.slowlog.threshold.index.trace: 500ms
  369.  
  370. ################################## GC Logging ################################
  371.  
  372. #monitor.jvm.gc.young.warn: 1000ms
  373. #monitor.jvm.gc.young.info: 700ms
  374. #monitor.jvm.gc.young.debug: 400ms
  375.  
  376. #monitor.jvm.gc.old.warn: 10s
  377. #monitor.jvm.gc.old.info: 5s
  378. #monitor.jvm.gc.old.debug: 2s
  379.  
  380. ################################## Security ################################
  381.  
  382. # Uncomment if you want to enable JSONP as a valid return transport on the
  383. # http server. With this enabled, it may pose a security risk, so disabling
  384. # it unless you need it is recommended (it is disabled by default).
  385. #
  386. #http.jsonp.enable: true
  387. script.disable_dynamic: true
  388.  
  389. ####Memory Best Practices 1.7######
  390.  
  391. indices.fielddata.cache.size: 50%
  392. indices.breaker.fielddata.limit: 60%
  393. indices.breaker.request.limit: 40%
  394. indices.breaker.total.limit: 70%
  395. #indices.store.throttle.max_bytes_per_sec: 150mb
Advertisement
Add Comment
Please, Sign In to add comment