最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

Alternative to ManagementCenterConfig.setUrl() while upgrading Hazelcast from 3.12.x to 5.5.0 - Stack Overflow

programmeradmin8浏览0评论

In 3.12.x, one could do the following to provide cluster with the url of management-center:

com.hazelcast.config.Config config = new YamlConfigBuilder().build(); config.getManagementCenterConfig().setUrl("http://localhost:8090/hazelcast-mancenter");

Now, the documentation (upgradin-from-imdg-3) states the following: "As Management Center now uses Hazelcast Java client for communication with the cluster, all attributes and nested elements have been removed from programmatic, XML and YAML configurations for Management Center, i.e., from ManagementCenterConfig class and management-center configuration element, except for the scripting-enabled attribute."

But the documentation does not provide any alternative to set url through Java client. Need help in the finding the alternative.

Of-course, we can create a cluster in management-center and add member addresses manually, but then we loose automation. What I am looking for is that the service runs in kubernetes environment and uses kubernetes discovery to form cluster and discover each member. At the same time, these members are also discovered automatically by manahement-center. Is it achievable?

I have tried setting the following configuration in yaml file and providing to YamlConfigBuilder()

hazelcast:
   management-center:
      enabled: true
      url: "management-center-url"

But this gives error on enabled and url property that they are extraneous.

发布评论

评论列表(0)

  1. 暂无评论