Event handling questions in Jira Data Center

, , ,
1

Hi Everyone,

I found some documentation for clustered Confluence and Bitbucket stating that events are only propagated on the instance on which they occur. My questions:

  1. Does the same hold for Jira Data Center? Are events propagated only inside the node on which they were fired?
  2. Does Jira Data Center has any performance penalty compared to Jira Server in terms of event broadcasting/listening?

To add some context: I am broadcasting custom events via PluginEventManager.broadcast() on a local Jira Server instance, and using these events to trigger Automation rules. It is very performant - I can easily fire thousands of events at once without slowing down Jira. I am curious about the performance impacts of doing the same in Data Center but did not find official documentation on that topic.

Any help/suggestion is highly appreciated. Thanks!

Gábor

1 Like
2

@aagrawal2 Do you think you can help us get an answer for this?

3

Let me look into it

5

From my conversations internally, there isn’t any known problem with the PluginEventManager.broadcast() being used in this (described above by Gabor) way in Jira Data Center.
You should be fine.
Heaviest impact come from, to my knowledge, from changes that need to be propagated to either cache or index.

1 Like