Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-70691

Jira Data Center deployment with Hazelcast ECACHE

XMLWordPrintable

    • 0
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Currently, Jira Data Center ECACHE replication does not work with HAZELCAST similar to Confluence and Bitbucket in Docker.

      Install Bitbucket Data Center  

      Install Bitbucket Data Center 

       

      https://hub.docker.com/r/atlassian/jira-software

      EHCACHE_LISTENER_PORT (default: 40001)
The port the node is going to be listening to. Depending on your container deployment method this port may need to be exposed and published.

EHCACHE_OBJECT_PORT (default: dynamic)
The port number on which the remote objects bound in the registry receive calls. This defaults to a free port if not specified. This port may need to be exposed and published.

EHCACHE_MULTICAST_PORT (default: NONE)
The dedicated port for the multicast heartbeat traffic. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' instead of 'default'. Depending on your container deployment method this port may need to be exposed and published.

      Suggested Solution

      Provide ability or configuration methods to achieve for Jira Data Center to work with HAZELCAST for ECACHE replication without any network connectivity between 2 different docker host.

      Workaround 

      n/a

            [JRASERVER-70691] Jira Data Center deployment with Hazelcast ECACHE

            There are no comments yet on this issue.

              Unassigned Unassigned
              7b16d25fc289 Venkatesan Vaidhya
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: