@Prakash Ravi Question 1, No, you do not need a controller service for each processor, they can use the same DistributedCache service. Question 2, Yes, that is the correct understanding. If no directory is specified then the cache is in memory only. Question 3, The way the DistributedMapCacheServer works is, each node in the cluster will be running it's own server. But data is written via the DistributedMapCacheClient controller service, and in that configuration, you will specify which of the DistributedMapCacheServers to write the data. So, only one of servers will have the data. If that node is lost, then the server would not be available until the node was back in the cluster. When you say "primarily running the processor", I am assuming that you mean the processor is configured to run on the primary node only. If you lose the primary node, then another node would be elected a primary, and then the processor would start running again. There might be an issue if the lost node also happen to be the node that was configured to be used by the DistributedMapCacheClient controller service, then the state would be unavailable. FYI, there are only three processors currently that require a DistributedMapCache controller service. Any other processors that retain state use zookeeper. So, the state of the processor is maitained across the cluster automatically. ... View more