@@ -38,7 +38,7 @@ remote clusters that should be connected to, for instance:
38
38
39
39
[source,yaml]
40
40
--------------------------------
41
- search :
41
+ cluster :
42
42
remote:
43
43
cluster_one: <1>
44
44
seeds: 127.0.0.1:9300
@@ -58,7 +58,7 @@ following:
58
58
PUT _cluster/settings
59
59
{
60
60
"persistent": {
61
- "search ": {
61
+ "cluster ": {
62
62
"remote": {
63
63
"cluster_one": {
64
64
"seeds": [
@@ -94,7 +94,7 @@ because we'll use them later.
94
94
{
95
95
"acknowledged" : true,
96
96
"persistent": {
97
- "search ": {
97
+ "cluster ": {
98
98
"remote": {
99
99
"cluster_one": {
100
100
"seeds": [
@@ -129,7 +129,7 @@ A remote cluster can be deleted from the cluster settings by setting its seeds t
129
129
PUT _cluster/settings
130
130
{
131
131
"persistent": {
132
- "search ": {
132
+ "cluster ": {
133
133
"remote": {
134
134
"cluster_three": {
135
135
"seeds": null <1>
@@ -310,7 +310,7 @@ boolean `skip_unavailable` setting, set to `false` by default.
310
310
PUT _cluster/settings
311
311
{
312
312
"persistent": {
313
- "search .remote.cluster_two.skip_unavailable": true <1>
313
+ "cluster .remote.cluster_two.skip_unavailable": true <1>
314
314
}
315
315
}
316
316
--------------------------------
@@ -392,30 +392,30 @@ GET /cluster_one:twitter,cluster_two:twitter,twitter/_search <1>
392
392
[[cross-cluster-search-settings]]
393
393
=== Cross cluster search settings
394
394
395
- `search .remote.connections_per_cluster`::
395
+ `cluster .remote.connections_per_cluster`::
396
396
397
397
The number of nodes to connect to per remote cluster. The default is `3`.
398
398
399
- `search .remote.initial_connect_timeout`::
399
+ `cluster .remote.initial_connect_timeout`::
400
400
401
401
The time to wait for remote connections to be established when the node starts. The default is `30s`.
402
402
403
- `search .remote.node.attr`::
403
+ `cluster .remote.node.attr`::
404
404
405
405
A node attribute to filter out nodes that are eligible as a gateway node in
406
406
the remote cluster. For instance a node can have a node attribute
407
407
`node.attr.gateway: true` such that only nodes with this attribute will be
408
- connected to if `search .remote.node.attr` is set to `gateway`.
408
+ connected to if `cluster .remote.node.attr` is set to `gateway`.
409
409
410
- `search .remote.connect`::
410
+ `cluster .remote.connect`::
411
411
412
412
By default, any node in the cluster can act as a cross-cluster client and
413
- connect to remote clusters. The `search .remote.connect` setting can be set
413
+ connect to remote clusters. The `cluster .remote.connect` setting can be set
414
414
to `false` (defaults to `true`) to prevent certain nodes from connecting to
415
415
remote clusters. Cross-cluster search requests must be sent to a node that
416
416
is allowed to act as a cross-cluster client.
417
417
418
- `search .remote.${cluster_alias}.skip_unavailable`::
418
+ `cluster .remote.${cluster_alias}.skip_unavailable`::
419
419
420
420
Per cluster boolean setting that allows to skip specific clusters when no
421
421
nodes belonging to them are available and they are searched as part of a
0 commit comments