remote-cluster-network.asciidoc 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101
  1. [[remote-cluster-network-settings]]
  2. ==== Advanced remote cluster (API key based model) settings
  3. Use the following advanced settings to configure the remote cluster interface (API key based model)
  4. independently of the <<transport-settings,transport interface>>. You can also
  5. configure both interfaces together using the <<common-network-settings,network settings>>.
  6. `remote_cluster_server.enabled`::
  7. (<<static-cluster-setting,Static>>, boolean)
  8. Determines whether the remote cluster server should be enabled. This setting must
  9. be `true` for `remote_cluster.port` and all following remote cluster settings to
  10. take effect. Enabling it allows the cluster to serve cross-cluster requests using
  11. the API key based model. Defaults to `false`.
  12. `remote_cluster.host`::
  13. (<<static-cluster-setting,Static>>, string)
  14. Sets the address of this node for remote cluster server traffic. The node will bind to this
  15. address and will also use it as its remote cluster server publish address. Accepts an IP
  16. address, a hostname, or a <<network-interface-values,special value>>.
  17. Use this setting only if you require different configurations for the
  18. remote cluster server and transport interfaces.
  19. +
  20. Defaults to the address given by `transport.bind_host`.
  21. `remote_cluster.bind_host`::
  22. (<<static-cluster-setting,Static>>, string)
  23. The network address(es) to which the node should bind in order to listen for
  24. incoming remote cluster connections. Accepts a list of IP addresses, hostnames, and
  25. <<network-interface-values,special values>>. Defaults to the address given by
  26. `remote_cluster.host`. Use this setting only if you require
  27. to bind to multiple addresses or to use different addresses for publishing and
  28. binding, and you also require different binding configurations for the
  29. remote cluster server and transport interfaces.
  30. `remote_cluster.publish_host`::
  31. (<<static-cluster-setting,Static>>, string)
  32. The network address at which the node can be contacted by other nodes. Accepts
  33. an IP address, a hostname, or a <<network-interface-values,special value>>.
  34. Defaults to the address given by `remote_cluster.host`.
  35. Use this setting only if you require to bind to multiple addresses or to use
  36. different addresses for publishing and binding, and you also require different
  37. binding configurations for the remote cluster server and transport interfaces.
  38. `remote_cluster.publish_port`::
  39. (<<static-cluster-setting,Static>>, integer)
  40. The port of the <<modules-network-binding-publishing,remote cluster server publish
  41. address>>. Set this parameter only if you need the publish port to be
  42. different from `remote_cluster.port`. Defaults to the port assigned via
  43. `remote_cluster.port`.
  44. `remote_cluster.tcp.keep_alive`::
  45. (<<static-cluster-setting,Static>>, boolean)
  46. Configures the `SO_KEEPALIVE` option for remote cluster sockets, which determines
  47. whether they send TCP keepalive probes. Defaults to `transport.tcp.keep_alive`.
  48. `remote_cluster.tcp.keep_idle`::
  49. (<<static-cluster-setting,Static>>, integer)
  50. Configures the `TCP_KEEPIDLE` option for transport sockets, which determines
  51. the time in seconds that a connection must be idle before starting to send TCP
  52. keepalive probes. Defaults to `transport.tcp.keep_idle` if set, or the system
  53. default otherwise. This value cannot exceed `300` seconds. In cases where the
  54. system default is higher than `300`, the value is automatically lowered to
  55. `300`. Only applicable on Linux and macOS.
  56. `remote_cluster.tcp.keep_interval`::
  57. (<<static-cluster-setting,Static>>, integer)
  58. Configures the `TCP_KEEPINTVL` option for transport sockets, which determines
  59. the time in seconds between sending TCP keepalive probes. Defaults to
  60. `transport.tcp.keep_interval` if set, or the system default otherwise. This value
  61. cannot exceed `300` seconds. In cases where the system default is higher than
  62. `300`, the value is automatically lowered to `300`. Only applicable on Linux
  63. and macOS.
  64. `remote_cluster.tcp.keep_count`::
  65. (<<static-cluster-setting,Static>>, integer)
  66. Configures the `TCP_KEEPCNT` option for transport sockets, which determines the
  67. number of unacknowledged TCP keepalive probes that may be sent on a connection
  68. before it is dropped. Defaults to `transport.tcp.keep_count` if set, or the
  69. system default otherwise. Only applicable on Linux and macOS.
  70. `remote_cluster.tcp.no_delay`::
  71. (<<static-cluster-setting,Static>>, boolean)
  72. Configures the `TCP_NODELAY` option on transport sockets, which determines
  73. whether {wikipedia}/Nagle%27s_algorithm[TCP no delay] is enabled. Defaults to
  74. `transport.tcp.no_delay`.
  75. `remote_cluster.tcp.reuse_address`::
  76. (<<static-cluster-setting,Static>>, boolean)
  77. Configures the `SO_REUSEADDR` option for network sockets, which determines
  78. whether the address can be reused or not. Defaults to
  79. `transport.tcp.reuse_address`.
  80. `remote_cluster.tcp.send_buffer_size`::
  81. (<<static-cluster-setting,Static>>, <<byte-units,byte value>>)
  82. The size of the TCP send buffer for transport traffic. Defaults to
  83. `transport.tcp.send_buffer_size`.
  84. `remote_cluster.tcp.receive_buffer_size`::
  85. (<<static-cluster-setting,Static>>, <<byte-units,byte value>>)
  86. The size of the TCP receive buffer for transport traffic. Defaults to
  87. `transport.tcp.receive_buffer_size`.