Introduce/implement a new ckpt creation flag CL_CKPT_PEER_TO_PEER_REPLICA with hot standby checkpoints. During a sectionoverwrite, the writes are directly sent to the peers by iterating through the checkpoints client list. For peer to peer replica enabled checkpoints, the hot-standby update is skipped by the ckpt server since the client writer directly sends/writes to the peers
Also enable/implement ckpt peer to peer replica for clCkptCheckpointWrite api like clCkptSectionOverwrite if the CL_CKPT_PEER_TO_PEER_REPLICA flag is set for the checkpoint to directly update the hot-standby peer from the client side and skip updation of hot-standby's for such ckpts from ckpt server side
Introduce a small peer to peer (2n specific) client cache for CL_CKPT_PEER_TO_PEER_REPLICA crhot-standby checkpoints. This caches the hot-standby client list for the ckpt fetched from the server. The cache is invalidated when the node or component in the cache leaves. To disable using the cache, users can either: export CL_CKPT_CLIENT_CACHE_DISABLE=1 in the etc/asp.conf file or create the checkpoint with CL_CKPT_PEER_TO_PEER_CACHE_DISABLE flag on top of CL_CKPT_PEER_TO_PEER_REPLICA flag