Eureka enabled Spring-boot service with hazelcast client and EurekaOne discovery not able to reuse existing discovery client

[mgoldver]

The setup:

• Spring-boot service S1 registers with discovery service via discovery client DC1.
• This service S1 needs to connect to Hazelcast cluster (which is also registered with the same discovery service).
• Hazelcast client config also needs discovery client DC2 configured to discover Hazelcast cluster nodes.

The ask: allow DC1 to be used for Hazelcast client discovery by proving the ability to supply Hazelcast cluster name (using metadata property for example).

More explicitly, EurekaOneDiscoveryStrategy.discoverNodes() method determines "applicationName" by calling applicationInfoManager.getEurekaInstanceConfig().getAppname(). This creates an issue since "applicationName" returned is the name under which the service S1 is registered with Eureka instead of the name of the application under which the Hazelcast cluster is registered.

[leszko]

Hi @mgoldver , would using use-metadata-for-host-and-port solve your issue?

[mgoldver]

Hi @leszko, unfortunately not, we already use use-metadata-for-host-and-port option. The problem is that there is no way to reuse the same discovery client if the app is already using it to register itself with Eureka.