Currently, Jira's health check features do not include a mechanism to verify cache connections between nodes. When issues arise, Jira only indicates that it cannot reach the node, leading to confusion and additional troubleshooting steps for our customers.

This often results in customers needing to manually check if ports 40001 and 40011 are open between nodes, as these ports are crucial for caching operations. Blocked ports can cause caching failures, impacting Jira's performance and reliability.

We propose integrating this functionality directly into Jira's health check feature in future releases. By doing so, Jira will automatically verify the cache connection between nodes during health checks and provide clear, actionable feedback if any issues are detected. This enhancement will:

• Reduce the volume of support cases related to cache connection issues.
• Empower customers to resolve connectivity issues quickly and independently.
• Improve overall customer satisfaction by providing clear diagnostics and solutions.

As a workaround, I created this script that you can download and use to check these ports on your own. Alternatively, you can Telnet or use another network tool to help check the connectivity

#!/bin/bash
# Check if a hostname or IP is provided
if [ -z "$1" ]; then
  echo "Usage: $0 <hostname_or_ip>"
  exit 1
fi
HOST=$1
# Define the specific ports to check
PORTS=(40001 40011)
# Loop over the specified ports
for PORT in "${PORTS[@]}"; do
  # Use /dev/tcp to test connectivity
  (echo > /dev/tcp/$HOST/$PORT) >/dev/null 2>&1
  # Check the exit status of the command
  if [ $? -eq 0 ]; then
    echo "Port $PORT on $HOST is open."
  else
    echo "Port $PORT on $HOST is closed."
  fi
done

How to Use:

1. Save this script to a file, for example, check_ports.sh.
2. Make the script executable with the command: chmod +x check_ports.sh.
3. Run the script with the hostname or IP address you want to check: ./check_ports.sh example.com