Support Questions
Find answers, ask questions, and share your expertise

Could not connect to Distributed Map Cache server to get table information in CaptureChangesMysql Nifi processor

Solved Go to solution

Could not connect to Distributed Map Cache server to get table information in CaptureChangesMysql Nifi processor

Explorer

Hello .

 

I am trying to read the mysql bin log data from mysql database and i am getting the error as

"Could not connect to Distributed Map Cache server to get table information"

when i added the Distributed Map Cache Client value in CaptureChangeMysql Aapache nifi processor .

screenshots are attached for the reference 

 

OS :Ubuntu (AWS AC2)

NIFI : 1.8.0

Mysql : 5.7.*

iScreenshot 2019-08-29 at 6.29.04 PM.pngScreenshot 2019-08-29 at 6.33.56 PM.png

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Could not connect to Distributed Map Cache server to get table information in CaptureChangesMysql Nifi processor

@pacman You would do better to create your own new Question with the same errors and any additional information you can provide.  Its unlikely the original poster will respond.

 

Just incase he does, and just incase this helps:

 

I think the solution you are looking for is to add a DistributedMapCacheServer.  The screenshot above is just the client.  The client needs a server running/enabled in order to be operational.    

 

Another suggestion is to make sure that there is connectivity to the map cache port, between nifi,mysql, and the map cache port.

 

If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.

 

Thanks,

Steven

View solution in original post

4 REPLIES 4

Re: Could not connect to Distributed Map Cache server to get table information in CaptureChangesMysql Nifi processor

New Contributor

I getting the same error. Is there any solution to it?

Re: Could not connect to Distributed Map Cache server to get table information in CaptureChangesMysql Nifi processor

@pacman You would do better to create your own new Question with the same errors and any additional information you can provide.  Its unlikely the original poster will respond.

 

Just incase he does, and just incase this helps:

 

I think the solution you are looking for is to add a DistributedMapCacheServer.  The screenshot above is just the client.  The client needs a server running/enabled in order to be operational.    

 

Another suggestion is to make sure that there is connectivity to the map cache port, between nifi,mysql, and the map cache port.

 

If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.

 

Thanks,

Steven

View solution in original post

Re: Could not connect to Distributed Map Cache server to get table information in CaptureChangesMysql Nifi processor

New Contributor

@stevenmatison your answer did solve the problem. Thanks!

Re: Could not connect to Distributed Map Cache server to get table information in CaptureChangesMysql Nifi processor

Master Guru

@kiranps11 

 

Did you add and start a "DistributedMapCacheServer" controller service running on port 4557?

The "DistributedMapCacheClientService" controller service only creates a client that is used to connect to a server you must also create. 


Keep in mind that the DistributedMapCacheServer does not offer High Availability (HA). Enabling this controller services will start a DistributedMapCacheServer on each node in your NiFi cluster, but each of those servers do not talk to each other.  This is important to understand since you have configured your DMC Client to use localhost.  This means that each node in your cluster would be using its own DMC server rather than a single DMC server.

For a HA solution you should be using an external map cache via one of the other client offerings like "HBase_2_ClientMapCacheService " or "RedisDistributedMapCacheClientService", but this would require you to setup that external HBAs or Redis server with HA yourself.

Hope this helps,

Matt