[META] [2.16] Cluster State Publication using Remote State

[soosinha]

Please describe the end goal of this project

For remote store enabled clusters, the cluster state is being published to a remote repository. This can be used to publish the cluster state to all nodes in the cluster. Instead of sending the cluster state object over the transport layer, the cluster manager node can just send the term and version of the cluster state over the transport layer which can then be used to download the corresponding cluster state by all the nodes directly from the remote store.

Previous meta issue for 2.15 release : #13683
The current meta issue is targetted for the enhancements targetted for 2.16 release.

Supporting References

Previous meta issue for 2.15 release : #13683
RFC: #13257

Issues

• [Remote Cluster State] Send remote cluster state only when all nodes in the cluster are remote state enabled #14113
• [Remote State] Create a RemoteObjectManager interface which is used by all managers #14176
• [Remote State] Timing and tracing for RemoteWritableEntityStore #14470
• [Optimization] [Remote state] With every election full state shouldn't get uploaded to remote #10682

Related component

Cluster Manager

[getsaurabh02]

@soosinha Can we close this issue out for 2.16?

[soosinha]

This will be completed in 2.17. I have removed 2.16 tag.