32 lines
1.3 KiB
Plaintext
32 lines
1.3 KiB
Plaintext
|
[[modules-gateway-local]]
|
||
|
|
=== Local Gateway
|
||
|
|
|
||
|
|
The local gateway allows for recovery of the full cluster state and
|
||
|
|
indices from the local storage of each node, and does not require a
|
||
|
|
common node level shared storage.
|
||
|
|
|
||
|
|
Note, different from shared gateway types, the persistency to the local
|
||
|
|
gateway is *not* done in an async manner. Once an operation is
|
||
|
|
performed, the data is there for the local gateway to recover it in case
|
||
|
|
of full cluster failure.
|
||
|
|
|
||
|
|
It is important to configure the `gateway.recover_after_nodes` setting
|
||
|
|
to include most of the expected nodes to be started after a full cluster
|
||
|
|
restart. This will insure that the latest cluster state is recovered.
|
||
|
|
For example:
|
||
|
|
|
||
|
|
[source,js]
|
||
|
|
--------------------------------------------------
|
||
|
|
gateway:
|
||
|
|
recover_after_nodes: 1
|
||
|
|
recover_after_time: 5m
|
||
|
|
expected_nodes: 2
|
||
|
|
--------------------------------------------------
|
||
|
|
|
||
|
|
Note, to backup/snapshot the full cluster state it is recommended that
|
||
|
|
the local storage for all nodes be copied (in theory not all are
|
||
|
|
required, just enough to guarantee a copy of each shard has been copied,
|
||
|
|
i.e. depending on the replication settings) while disabling flush.
|
||
|
|
Shared storage such as S3 can be used to keep the different nodes'
|
||
|
|
copies in one place, though it does comes at a price of more IO.
|