Update 1.1 for Azure DevOps Server 2019 is a roll up of bug fixes and security patches. This includes any patches put out prior to this update. Three major pain points that have been fixed in this release are Elasticsearch failures, high memory usage and collection sorting.
Collection Sorting
Prior to Update 1, project collections were sorted alphabetically. However, the sorting appeared to be random after the update. This made it difficult for teams with multiple collections to find what they were looking for. Update 1.1 put out a fix for this, bringing back the alphabetical sorting.
High Memory Usage
After installing Update 1, many noticed that Azure DevOps Server appeared to slow down significantly. This affected processes such as the web portal and even simple folder navigation. Those experiencing this problem noticed the slowdown was due to very high memory usage. One user noted that their memory usage was over 90%. For some, this also presented a financial problem: adding memory to cope with this higher usage would come at a cost. Fortunately, Update 1.1 has remedied this issue.
Elasticsearch Failures
Elasticsearch is an open-source, distributed search and analytics engine. It has many use cases, including for application search, enterprise search, and log analytics. Prior to this update, some received an error when setting up Elasticsearch: “User not authorized.” Still others experienced indexing and query failures when upgrading from TFS 2018 Update 2 or newer. Update 1.1 resolved both of these issues.
For more information on Azure DevOps Server Update 1.1, or to speak to an expert about troubleshooting or installation, contact us here at PRAKTIK today.