Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-70

Confluence hazelcast port 5701 customisation

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • None
    • Environment - Kubernetes
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      The Confluence Helm Chart documents:

      confluence:
  # Port definitions
  #
  ports:

    # -- The port on which the Confluence container listens for Hazelcast traffic
    #
    hazelcast: 5701

      However, changing the above value to a custom value such as Port 5801 only works for a single node. Scaling to additional nodes will result in nodes encountering a Cluster Panic and shutting down.

      The above custom value updates Confluence to listen on Port 5801 but the discovery of other nodes still occurs on Port 5701 .

      The cause of this is that Hazelcast Kubernetes Discovery API appears to utilise the HAZELCAST_KUBERNETES_SERVICE_PORT environment value for the Port number to discover other nodes. When this environment variable is not set, it defaults to 5701.

      Suggestion:

      Update the Helm Chart deployment to automatically set the HAZELCAST_KUBERNETES_SERVICE_PORT environment variable to the value in confluence.ports.hazelcast from the Helm chart values.

      Workaround:

      To update Confluence to a custom Hazelcast port value, also set the HAZELCAST_KUBERNETES_SERVICE_PORT environment variable in the Helm Chart values file. e.g.

      confluence:
  ports:
    hazelcast: 5801

  additionalEnvironmentVariables:
    - name: HAZELCAST_KUBERNETES_SERVICE_PORT
      value: "5801"

            [SCALE-70] Confluence hazelcast port 5701 customisation

            Mateo made changes -
            Remote Link Original: This issue links to "DCD-1553 (Bulldog)" [ 647529 ] New: This issue links to "CLIP-1553 (JIRA Server (Bulldog))" [ 647529 ]
            Yevhen made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Yevhen made changes -
            Assignee New: Yevhen [ c64f33b2bce3 ]
            Yevhen made changes -
            Status Original: Gathering Interest [ 11772 ] New: In Progress [ 3 ]
            Yifei Zhang made changes -
            Remote Link New: This issue links to "DCD-1553 (Bulldog)" [ 647529 ]
            Eric Lam made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 647015 ]
            Eric Lam made changes -
            Description Original: The Confluence Helm Chart documents:

            {code}
            confluence:
              # Port definitions
              #
              ports:

                # -- The port on which the Confluence container listens for Hazelcast traffic
                #
                hazelcast: 5701
            {code}

            However, changing the above value to a custom value such as *Port 5801* only works for a single node. Scaling to additional nodes will result in nodes encountering a Cluster Panic and shutting down.

            The above custom value updates Confluence to listen on Port 5801 (/) but the discovery of other nodes still occurs on Port 5701 (x).

            The cause of this is that Hazelcast Discovery API appears to utilise the *{{HAZELCAST_KUBERNETES_SERVICE_PORT}}* environment value for the Port number to discover other nodes. When this environment variable is not set, it defaults to *5701*.

            h2. Suggestion:

            Update the Helm Chart deployment to automatically set the *{{HAZELCAST_KUBERNETES_SERVICE_PORT}}* environment variable to the value in *{{confluence.ports.hazelcast}}* from the Helm chart values.

            h2. Workaround:

            To update Confluence to a custom Hazelcast port value, also set the *{{HAZELCAST_KUBERNETES_SERVICE_PORT}}* environment variable in the Helm Chart values file. e.g.

            {code}
            confluence:
              ports:
                hazelcast: 5801

              additionalEnvironmentVariables:
                - name: HAZELCAST_KUBERNETES_SERVICE_PORT
                  value: "5801"
            {code}             		New: The Confluence Helm Chart documents:

            {code}
            confluence:
              # Port definitions
              #
              ports:

                # -- The port on which the Confluence container listens for Hazelcast traffic
                #
                hazelcast: 5701
            {code}

            However, changing the above value to a custom value such as *Port 5801* only works for a single node. Scaling to additional nodes will result in nodes encountering a Cluster Panic and shutting down.

            The above custom value updates Confluence to listen on Port 5801 (/) but the discovery of other nodes still occurs on Port 5701 (x).

            The cause of this is that Hazelcast Kubernetes Discovery API appears to utilise the *{{HAZELCAST_KUBERNETES_SERVICE_PORT}}* environment value for the Port number to discover other nodes. When this environment variable is not set, it defaults to *5701*.

            h2. Suggestion:

            Update the Helm Chart deployment to automatically set the *{{HAZELCAST_KUBERNETES_SERVICE_PORT}}* environment variable to the value in *{{confluence.ports.hazelcast}}* from the Helm chart values.

            h2. Workaround:

            To update Confluence to a custom Hazelcast port value, also set the *{{HAZELCAST_KUBERNETES_SERVICE_PORT}}* environment variable in the Helm Chart values file. e.g.

            {code}
            confluence:
              ports:
                hazelcast: 5801

              additionalEnvironmentVariables:
                - name: HAZELCAST_KUBERNETES_SERVICE_PORT
                  value: "5801"
            {code}
            Eric Lam created issue -

              c64f33b2bce3 Yevhen
              hlam@atlassian.com Eric Lam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: