feature: Shard Lifecycle In The Caching Server

[stevekuznetsov]

Feature Description

We need to handle the creation of new shards, the removal of existing shards, etc. for their data in the caching server.

Proposed Solution

To be designed. Open questions:

• how do we know a shard has been removed, and how do we remove all the data for it in the caching server (etcd range request is most efficient here)
• how do we know a new shard exists & should be present in the internal representation of which shards should be pushing?

Alternative Solutions

No response

Want to contribute?

• [ ] I would like to work on this issue.

Additional Context

No response