question Re: nifi detect duplicate MapCacheServer Error in Archives of Support Questions (Read Only)

nifi detect duplicate MapCacheServer Error

alexander_thoma — Mon, 01 Aug 2016 21:52:02 GMT

I have configured a DistributedMapCacheClientService and a DistributedMapCacheServer which are used by the DetectDuplicate processor. But when I try to process flowfiles using the DetectDuplicate Processor I receive an error: "Detect Duplicate failed to process session due to java.nio.channels.UnresolvedAdressException". So is there any additional configuration needed? Btw, I have installed Nifi additionally on my Hortonworks Sandbox, which is running locally.

Re: nifi detect duplicate MapCacheServer Error

pvillard — Mon, 01 Aug 2016 21:55:06 GMT

Hi @Alexander Flick,

Could you share the configuration of your controller services? Are the two controller services running?

Re: nifi detect duplicate MapCacheServer Error

alexander_thoma — Sun, 18 Aug 2019 12:00:16 GMT

MapCacheServer:

MapCacheClientService:

Both Controller Services are enabled but how can I check that they are running?

Re: nifi detect duplicate MapCacheServer Error

pvillard — Mon, 01 Aug 2016 22:10:10 GMT

Since you are running on a standalone NiFi instance, the MapCacheServer is running locally, then you should put 'localhost' for the property 'Server Hostname' in the client service. Let me know if it helps.

Re: nifi detect duplicate MapCacheServer Error

alexander_thoma — Mon, 01 Aug 2016 22:31:50 GMT

Yes, that helped - it works 🙂 Thank you so much!

Re: nifi detect duplicate MapCacheServer Error

alvinuw — Mon, 29 Aug 2016 22:33:19 GMT

@Pierre Villard

In the cluster mode, if we run MapCacheServer on only NCM, does that mean once NCM fails, the MapCacheServer becomes unavailable?

Is there anyway to avoid it?

Thanks.

Re: nifi detect duplicate MapCacheServer Error

pvillard — Mon, 29 Aug 2016 22:37:54 GMT

@Alvin Ji,

This is correct with NiFi 0.x. Unless you implement your own MapCacheServer service and separate it from NiFi, I am not sure there is a solution.

With NiFi 1.x (first version to be released in coming days, RC vote in progress), this is solved with a zero-master clustering paradigm.