From dd3a2c5295db2ea716b0baea4960eec5fe43cbb7 Mon Sep 17 00:00:00 2001 From: Sooraj Sinha Date: Wed, 12 Jun 2024 10:00:01 +0530 Subject: [PATCH] Simplify the remote publication description Signed-off-by: Sooraj Sinha --- .../remote-store/remote-cluster-state.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/_tuning-your-cluster/availability-and-recovery/remote-store/remote-cluster-state.md b/_tuning-your-cluster/availability-and-recovery/remote-store/remote-cluster-state.md index 66879fdf091..d042024d7e9 100644 --- a/_tuning-your-cluster/availability-and-recovery/remote-store/remote-cluster-state.md +++ b/_tuning-your-cluster/availability-and-recovery/remote-store/remote-cluster-state.md @@ -66,13 +66,11 @@ The remote cluster state functionality has the following limitations: - Unsafe bootstrap scripts cannot be run when the remote cluster state is enabled. When a majority of cluster-manager nodes are lost and the cluster goes down, the user needs to replace any remaining cluster manager nodes and reseed the nodes in order to bootstrap a new cluster. ## Remote cluster state publication -Cluster state publication using remote - When it is enabled, the updated cluster state during any updates like creation of an index and -put mappings will be published through remote store, that is, the cluster manager will provide the remote location -and nodes will download the cluster state directly from remote location. -As the cluster state grows over time and there are large number of nodes in the cluster, publishing the state over local transport -tends to add lot of overhead in terms of CPU, memory and transport thread-pool. This will reduce the overhead on cluster manager node -to publish the updated cluster state through remote store to every other node in the cluster instead of local transport. -Remote cluster state publication can be enabled by configuring the experimental remote publication feature. +The cluster manager node processes the updates to cluster state. It then, publishes the updated cluster state +over the local transport layer to all the follower nodes. With remote cluster state enabled, +cluster state is backed to remote store with every state update. The follower nodes can fetch the state +from remote store directly and reducing the overhead on the cluster manager node for publication. +This can be done by enabling the experimental remote publication feature. Enable the feature flag for `remote_store.publication` feature by following the [experiment feature flag documentation]({{site.url}}{{site.baseurl}}/install-and-configure/configuring-opensearch/experimental/). The routing table is an object within the cluster state which contains the shard allocation details for each index.