The JIRA Data Center configuration can only be established when the system is able to identify the presence of JIRA Data Center environment.
In such an environment, all data is being replicated into cluster nodes with the use of Hazelcast technology.
How to set-up?
It is possible to set-up a port, which will be listened to by specific cluster nodes. With such a factor, we’d create a situation similar to the one described in Atlassian’s JIRA DataCenter Documenatation Article under the ehcache.listener.port paragraph (Cluster.properties file parameters).
In order to set-up a port mentioned above, it is required to add a parameter to JVM runtime parameters under which a specific node within a cluster is established (as per instruction provided by Atlassian in the following article: Setting properties and options on startup)
The parameter should be set according to the below principle:
Correspondingly, for each of our plugins it should look like this:
Please bear in mind that it is required for every cluster node to have the value of above parameter set identically for each specific plugin. With that in mind, we must also remember to define a different port for in every one of our products, otherwise it is very likely for us to encounter unwanted conflicts caused by the default port allocation with the value of 40101 for each plugin.
With the release of BigPicture 6.5.0, BigGantt 3.4.0 and BigTemplate 2.5.0 above configuration may be obsolete as for the clustering purposes our plugins will allocate all necessary port values to the ones seen below, during the installation in the JIRA Data Center:
- BigPicture - 40101
- BigPicture Enterprise - 40102
- BigTemplate - 40103
- BigGantt - 40104
Though, it is required for these ports to be open on each DC Node in order for our plugins to execute and function properly!
There is no content with the specified labels