-
Bug
-
Resolution: Fixed
-
Medium
-
4.20.5, 4.20.6, 4.20.7
-
None
-
2
-
Severity 3 - Minor
-
32
-
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
- Set up JSM Data Center with 2 nodes or more.
- Include at least one underscore (_) symbol in the nodes' id. For example,
jira.node.id = jiradc_node1
- Assign one of the nodes as the dedicated scheduling node for Insight.
- 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.
- 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.
- mentioned in
-
Page Failed to load
[JSDSERVER-11222] Scheduled import does not run consistently according to cron schedule if nodes' id contains an underscore symbol(s)
| Fix Version/s | Original: Insight 10.0.1 [ 100293 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 5.0.0 [ 99898 ] |
| UIS | Original: 40 | New: 32 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 649401 ] |
| UIS | Original: 32 | New: 40 |
| Description |
Original:
h3. 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 h3. Steps to Reproduce # Set up JSM Data Center with 2 nodes or more. # Include at least one underscore (_) symbol in the nodes' id. For example, {code} jira.node.id = jiradc_node1 {code} # Assign one of the nodes as the [dedicated scheduling node for Insight|https://confluence.atlassian.com/servicemanagementserver/configuring-global-jira-settings-1044784415.html]. # 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. # Monitor if the import starts every 2 minutes. h3. Expected Results The scheduled import starts according to the cron schedule consistently h3. 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: {code} 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 {code} h3. Workaround Rename the node id by avoiding any underscore (_) symbol. A hyphen ( - ) can be used as an alternative symbol. |
New:
h3. 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 h3. Steps to Reproduce # Set up JSM Data Center with 2 nodes or more. # Include at least one underscore (_) symbol in the nodes' id. For example, {code} jira.node.id = jiradc_node1 {code} # Assign one of the nodes as the [dedicated scheduling node for Insight|https://confluence.atlassian.com/servicemanagementserver/configuring-global-jira-settings-1044784415.html]. # 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. # Monitor if the import starts every 2 minutes. h3. Expected Results The scheduled import starts according to the cron schedule consistently h3. 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: {code} 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 {code} h3. Workaround Rename the node id by avoiding any underscore (_) symbol. A hyphen ( - ) can be used as an alternative symbol. (i) 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. |
| Support reference count | New: 2 |
| Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
| UIS | New: 32 |