So the client would be on each of nodea, nodeb, and nodec. The server would be on nodea, nodeb, nodec. Each client would be configured to talk to any one of the three servers nodea, nodeb, or nodec. It does not offer HA. For more complete behavior it is a good idea to have a client/service implementation that talks to a full caching service. In the next release you can script out a controller service as a cache client. I believe one of the folks in the community has an example floating around on how to do this to talk to Hazelcast.
Thanks Joe On Thu, May 25, 2017 at 8:45 PM, 尹文才 <batman...@gmail.com> wrote: > Thanks Joe, so I need to setup the DistributedMapCacheServer on all nodes, > do you mean all DistributedMapCacheClientService should reference only one > of the servers(the same one on the same node)? > What if the DistributedMapCacheServer goes down on that node(or the node > itself goes down), does it support HA? > > > 2017-05-25 20:46 GMT+08:00 Joe Witt <joe.w...@gmail.com>: >> >> Hello >> >> You put the DistributedMapCacheServer controller service on as well >> and then point at it from the client services. So in your three nodes >> all three will have the server service but on all the clients they'll >> only point to the server service on one of the nodes. >> >> Thanks >> Joe >> >> On Thu, May 25, 2017 at 5:29 AM, 尹文才 <batman...@gmail.com> wrote: >> > Hi guys, I'm currently using NIFI with 3 nodes as a cluster, when using >> > DistributedMapCacheClientService there's a configuration property >> > called 'Server Hostname'. I've tried with localhost on my local NIFI >> > standlone node >> > and it did work. My question is what should I set inside the NIFI >> > cluster? >> > Thanks. > >
