Hi community, Router uses Zookeeper to its MountTable, which is the key dataset to make the component function. Over time more and more entries are added into the Mount table. The current Router in memory cache from ZK often takes a lot of time to sync. (10-15 mins to download 1Million entries in our scenario).
On another hand, Router mounts are intended to be modified by admin only, which naturally limits the number of writes to it and the write is often done either via cmd/scripting. We also see more use cases where customers might want to create their own dirs and truly uses Router as one endpoint to access the whole Storage service. This goes against Zookeeper usage pattern and we also saw some perf and consistency issues. Both of the above behaviors fall into Key-Value Store use cases. Has someone considered or implemented certain features/components using Key-Value Store? Would love to hear more from the community. Thanks, Fengnan
