Applies to:

Issue Description

Recently, it has come to our attention, there were performance issues related to BigPicture in JIRA Data Center caused by improper cluster node deactivation within BigPicture. 
The issue manifests itself only when you update BigPicture multiple times without restarting JIRA. It results in multiple orphaned BigPicture server runnings on a single JIRA cluster node, causing the performance issues.


The issue had been resolved and the fix was implemented on 2017-07-31. It requires a user to restart their JIRA environment after the upgrade in order to terminate all mentioned ghost servers. 



Restart the JIRA environment after the plugin upgrade. Please make sure BigPicture has properly initialized its cluster (check for log entries as shown below)

Other recommendation

Check the following log entries in your Atlassian log files. You may need to enable INFO logging level to: "com.softwareplant" package. 

2017-08-25 14:46:19,987 ThreadPoolAsyncTaskExecutor::Thread 30 INFO      [c.s.u.cacheint.hazelcast.HazelcastCacheFactory] HAZELCAST SERVER ENABLED
2017-08-25 14:46:19,988 ThreadPoolAsyncTaskExecutor::Thread 30 INFO      [c.s.u.cacheint.hazelcast.HazelcastCacheFactory] HAZELCAST SERVER INFO
    Name        : bigpictureenterprise
    UUID        : 53d46a88-2b85-4134-a749-bfc2a36cee51
    Port        : 40102
    ClusterTime : 1503665179968
    Members     : 2
     Member UUID    : 6c90c55f-a2bb-4f45-b56d-f9a70376621a
     Member UUID    : 53d46a88-2b85-4134-a749-bfc2a36cee51

If you have any additional questions, please feel free to contact us via the Service Desk

Other Articles: