Karaf
  1. Karaf
  2. KARAF-1322

The Hazelcast group name is randomly set

    Details

      Description

      I want to create 2 hazelcast groups

      But when you change the default group name value ( cellar by default) in the both files :

      • hazelcast.xml,
      • org.apache.karaf.cellar.instance.cfg

      Once 10, the value set is the default value :

      • system | - - | /192.168.1.21:5706 [cellar] Hazelcast 1.9.4.6 (20120105) starting at Address[192.168.1.21:5706]

      and 9 out of 10, you have your value :

      • system | - - | /192.168.1.21:5706 [myGroup] Hazelcast 1.9.4.6 (20120105) starting at Address[192.168.1.21:5706]

        Activity

        Hide
        Anthony Masse added a comment -

        To continue my test ( creation of 2 hazelcasts groups), I searched another temporary solution :

        1. modify the "multicast-port" (ie: 54327)

        => but it is not possible

        2. modify the "multicast-group" (ie : 224.2.2.3)

        => it is OK 9 out of 10 (then I use this solution today)

        Show
        Anthony Masse added a comment - To continue my test ( creation of 2 hazelcasts groups), I searched another temporary solution : 1. modify the "multicast-port" (ie: 54327) => but it is not possible 2. modify the "multicast-group" (ie : 224.2.2.3) => it is OK 9 out of 10 (then I use this solution today)
        Hide
        Jean-Baptiste Onofré added a comment -

        With the latest change on trunk and cellar-2.2.x (2.2.4-SNAPSHOT), now, only etc/hazelcast.xml is used.

        I tested to change the group name (in the hazelcast.xml):

        node1:
        /192.168.1.241:5701 [my] Hazelcast Management Center started at port 5801.

        node2:
        /192.168.1.241:5702 [my] Hazelcast Management Center started at port 5802.

        So it works fine.

        It also tested to create two different groups:

        node1:
        /192.168.1.241:5701 [my] Hazelcast Management Center started at port 5801.

        node2:
        /192.168.1.241:5702 [other] Hazelcast Management Center started at port 5802.

        and node-list display only the member of the configured Hazelcast group:
        karaf@node2> cluster:node-list
        No. Host Name Port ID

        • 1 192.168.1.241 5702 192.168.1.241:5702
        Show
        Jean-Baptiste Onofré added a comment - With the latest change on trunk and cellar-2.2.x (2.2.4-SNAPSHOT), now, only etc/hazelcast.xml is used. I tested to change the group name (in the hazelcast.xml): node1: /192.168.1.241:5701 [my] Hazelcast Management Center started at port 5801. node2: /192.168.1.241:5702 [my] Hazelcast Management Center started at port 5802. So it works fine. It also tested to create two different groups: node1: /192.168.1.241:5701 [my] Hazelcast Management Center started at port 5801. node2: /192.168.1.241:5702 [other] Hazelcast Management Center started at port 5802. and node-list display only the member of the configured Hazelcast group: karaf@node2> cluster:node-list No. Host Name Port ID 1 192.168.1.241 5702 192.168.1.241:5702

          People

          • Assignee:
            Jean-Baptiste Onofré
            Reporter:
            Anthony Masse
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development