Issue Summary

Scheduled import does not run consistently according to cron schedule if nodes' id contains an underscore symbol(s)

This is reproducible on Data Center: yes

Steps to Reproduce

1. Set up JSM Data Center with 2 nodes or more.
2. Include at least one underscore (_) symbol in the nodes' id. For example,

   jira.node.id = jiradc_node1
   

3. Assign one of the nodes as the dedicated scheduling node for Insight.
4. Create a schema and configure an import to automatically synchronize every 2 minutes. For test purpose, create an import that could be completed within 2 minutes.
5. Monitor if the import starts every 2 minutes.

Expected Results

The scheduled import starts according to the cron schedule consistently

Actual Results

• The scheduled import doesn't start according to the cron schedule consistently.
• The below exception is thrown in the atlassian-jira.log file:

  2022-03-23 10:48:02,127+0100 ClusterMessageHandlerServiceThread:thread-1 WARN anonymous     [c.r.j.p.i.services.impl.InsightDCMessagingServiceImpl] Unable to parse received message dc_node2_SCHEDULED_IMPORT_1
  

Workaround

Rename the node id by avoiding any underscore (_) symbol. A hyphen ( - ) can be used as an alternative symbol.
It's required to configure the dedicated scheduling node for Insight again on the Administration > Manage apps > Insight configuration after renaming and restarting the node.