We are moving our Jira from server to DC and this is requiring us to validate our internal plugin.
We have one of the plugins that runs a job every few minutes, fetches the data from another bug-tracking tool and then creates event for each bug which ultimately is consumed by other exposed services of the plugin. This works as expected in Server version.
In the data center cluster, we are seeing some of the bugs from the other tracking tool being repeated multiple times (same bug is created more than once, whereas it should be created exactly once). I tried putting cluster-lock for the part of polling the data and also consuming but we are still seeing the duplicates. I was also under the assumption that at any point, only one node should run the cron and consume a particular event but my theory is not standing the test.
What should we do to avoid this? This is a major impediment in our quest to move to DC.
https://developer.atlassian.com/server/jira/platform/developing-for-high-availability-and-clustering/#developing-for-high-availability-and-clustering is the official source of info about things like scheduling tasks in a plugin for a Data Center instance
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events