Hi guys, I have a few questions about DistributedMapCacheServer.
First question, I am confused by "Distributed" part. If I get it, the server actually runs on a single node and if it fails, it is game over. Is that right? Why NiFi is not using ZK for that since ZK is already used by NiFi cluster? I see most of the use cases / examples are about using DistributedMapCacheServer as a lookup or state store and this is exactly what ZK was designed for and provides redundancy, scalability and 5-10k ops per sec on 3 node ZK cluster. Second question, I did not find any tools to interact with it other than Matt's groovy tool. Third question, how DistributedMapCacheServer that persists to file system, handles concurrency and locking? Is it reliable and can be trusted? And lastly, is there additional overhead to support DistributedMapCacheServer as another system or it is pretty much hands off once a controller is set up? Thanks! Boris
