Starting an async task on Jira Data Center runs forever
Description
It seems that async tasks on Jira Data Center in some cases run forever. The dialog shows "Starting task on other cluster node", but does not update itself afterwards. Also, users are seeing these or similar exceptions in their Jira logs:
The exceptions are related to the communication between the cluster nodes which fails for some reason.
Note
As soon as one synchronization is running in the background and you are restarting a cluster node, you will probably still see these exceptions even after you have updated to the Backbone version in which the fix for this problem has been introduced (see version information of this issue). However, the exceptions in this case should only be temporary for the time you are restarting a cluster node. If this happens permanently and even when the node has been restarted >30mins ago, then please reach out to our support and we'll investigate it.
It seems that async tasks on Jira Data Center in some cases run forever. The dialog shows "Starting task on other cluster node", but does not update itself afterwards. Also, users are seeing these or similar exceptions in their Jira logs:
The exceptions are related to the communication between the cluster nodes which fails for some reason.
Note
As soon as one synchronization is running in the background and you are restarting a cluster node, you will probably still see these exceptions even after you have updated to the Backbone version in which the fix for this problem has been introduced (see version information of this issue). However, the exceptions in this case should only be temporary for the time you are restarting a cluster node. If this happens permanently and even when the node has been restarted >30mins ago, then please reach out to our support and we'll investigate it.