remote-cluster-network.asciidoc 5.1 KB

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