Inter-node communication in ActivityTimeline for Jira Data Center

Owned by Instructor
Last updated: Jul 18, 2024 by Svitlana Samotis

This article is applicable to Jira Data Center only.

ActivityTimeline app requires direct communication between Jira DC nodes through Jira node port.

If there is a Firewall on each Jira node/VPC that blocks Jira port from accessing by other Jira nodes then ActivityTimeline app will not work correctly on all Jira cluster nodes.

The IT infrastructure team should open Jira node’s port for internal direct communication between Jira nodes. There is no need to open it for public/external/Internet access.

 

Configuration Steps

  1. Open the Maintenance Page page at the following link:
    https://<JIRA_HOME_URL>/plugins/servlet/activitytimelineconfig/configuration

  2. If you see an error like on the screenshot below then it most likely means the Firewall is blocking connection from Jira nodeA to nodeB and vise versa on port 8081 (your configuration may have a different Jira node port number in the URL):

  1. Open your Firewall configuration and allow 8081 port (or 8080) depending on what you see on your Maintenance Page for communication between cluster nodes.

That should be it.

Simply refresh the Maintenance Page to check if the connection is successful now.

ActivityTimeline connects to the nodes using URLs, not IP addresses. Therefore, it is essential to map node URLs to their corresponding IP addresses.

Configuration Steps

  1. Open the Maintenance Page page at the following link:
    https://<JIRA_HOME_URL>/plugins/servlet/activitytimelineconfig/configuration

  2. If you see an error like on the screenshot below ensure the URL specified under ‘Node URL’ in the master node section on the maintenance page is accessible from each node:

image-20240710-124505.png

  1. Updating Hosts File (Linux Example):

  • Open the /etc/hosts file and update the configuration to include the IP addresses and server names of each node. Example:

10.0.0.1  node1servername
10.0.0.2  node2servername
10.0.0.3  node3servername 

  1. Alternatively, to configure that you can assign each node URL in the at.properties configuration file. You may refer to the example below:

    at.jira.node1.url=node1_id@https://https_url_to_node

    at.jira.node2.url=node2_id@https://https_url_to_node

    at.jira.node3.url=node3_id@https://https_url_to_node

    at.jira.node4.url=node4_id@https://https_url_to_node

    at.jira.node5.url=node5_id@https://https_url_to_node

    at.jira.node6.url=node6_id@https://https_url_to_node

     

  1. Restart ActivityTimeline:

  • After updating the configurations, perform a force restart of ActivityTimeline from the maintenance page.

 

In case you are not sure about the reasons, please make sure to contact our Support Team