Change is required. Atlassian engineer's blog

  During the tough times of the Covid-19 pandemic, I got a request from the Atlassian community to help with a Jira performance issue. Surprisingly, the solution was simple: removing an unused custom field in the default settings improved the performance for many projects. In this article, I’ll explain how this small change made a big difference. The Problem In 2020, as everyone adjusted to remote work and more online activities, users saw a big slowdown in many system, as on-prem Jira’s performance. The cause was hard to find, causing frustration. Error Analysis After adjusting logging level for all dedicated package (still unclear why package com. was only FATAL level), and x Upon delving into the logs, it became evident that there was an overwhelming number of errors linked to a particular custom field. This field, VIM: auto (customfield_16204), was part of the Jira Misc Custom Fields (JMCF) plugin. A typical log entry looked like this: 2020–07–30 13:45:19,458+0300 http-nio-8080...

  Hey DevOps folks, Gonchik here! Today, I want to share some insights and practical tips on managing your Kubernetes image registry more effectively. If you’re dealing with GitLab’s Container Registry, you know how quickly it can fill up with outdated and unused images. Storage costs can skyrocket, and managing all those images can become a nightmare. Let’s talk about how to avoid accidentally deleting the images your clusters still need. Why Cleaning Up is Crucial We’ve all been there — our CI/CD pipelines are constantly pushing new images with every commit, and over time, old deployments and misconfigured scripts leave behind a cluttered mess. This bloat doesn’t just affect costs; it can complicate day-to-day operations and make it harder to find the images you actually need. The Importance of Identifying Used Images Before you hit that “delete” button, it’s absolutely critical to know which images are still in use by your running pods. This is especially important in production...

  Maintaining a clean and efficient Jira installation, especially in an On-Prem setup, involves meticulous data management. A common issue faced by administrators is the duplication of history records for assets in Jira, which can lead to database bloat and performance issues. Duplications often stem from situations such as stuck imports, automated processes running recursively, or incorrect manual imports. This article will guide you through the process of detecting and cleaning up duplicated records, with an emphasis on solutions contributed by the Jira community. Understanding the Issue Duplicated history records can severely impact the performance of your Jira instance. As history records accumulate, database queries slow down, and system memory usage increases disproportionately. In one notable case, duplications reached a staggering 52 million records, prompting an urgent need for cleanup. Detecting Duplicated Records Artem Tumanov, a valuable contributor to the Jira communit...