Stale node ids should automatically be removed in Jira Data Center


Finally finally ... Atlassian takes action on this one since reported 5 years ago. As stated in the 8.10.x release notes, Jira 8.10.0 and later now is able to remove stale node automatically. We've introduced automation to your cluster maintenance. Now, you do not have to remove the offline nodes from your cluster manually, or … Continue reading Stale node ids should automatically be removed in Jira Data Center →

Run Jira Data Center in AWS – Part One


Jira is a stateful application, it requires persistent storage for both database and the shared home folder. And actually it is more complicated than it looks, e.g local index file, index files for some addons, nodes records etc. But it does not mean that you cannot run Jira in a dynamic environment, like AWS Auto … Continue reading Run Jira Data Center in AWS – Part One →

Confluence BootstrapException: Unable to bootstrap application: Failed to parse config file


One of our newly built Confluence stacks failed to start, and the error message is as below: BootstrapException: Unable to bootstrap application: Failed to parse config file: Error on line 19 of document : The reference to entity "k" must end with the ';' delimiter. Nested exception: The reference to entity "k" must end with … Continue reading Confluence BootstrapException: Unable to bootstrap application: Failed to parse config file →

CICD Design for Atlassian Suites in AWS


I have been working on a project of migrating Atlassian suites (Confluence/Jira/...) to AWS. This is not a simple lift and shift migration. We actually redesigned everything from ground up. Here is the CICD that I designed. The source codes are stored in on-premise BitBucket, the build tools is AWS Dev Tools (mainly CodeBuild). Development … Continue reading CICD Design for Atlassian Suites in AWS →

Use New Relic Java Agent with Jira


While setup New Relic Java agent in Jira, I found out that there is an extra option '-Datlassian.org.osgi.framework.bootdelegation.extra=com.newrelic.*' that you need to add into JVM parameters to make New Relic Java Agent to work with Jira. This is due to Jira uses OSGI framework, and the default boot class loader does not load the extra … Continue reading Use New Relic Java Agent with Jira →