Loading...
Loading...
We have identified an issue affecting ServiceNow Instances with Haraka/Kagami enabled during the upgrade to the Yokohama release. This issue may cause outages, leading to delays in the upgrade process and extended downtime. The root cause is the orphan transactions left behind by Glide on the database. These orphaned database transactions prevent the upgrade job triggers from acquiring a lock, causing all queries to enter the "waiting for metadata lock" state. Consequently, this results in backlog, contention, connection exhaustion, and ultimately, outages on the instance.
The issue can be reproduced by upgrading a Haraka/Kagami enabled instance to a Yokohama release. When the issue is encountered, the upgrade process will hang.
Admins can proactively apply the following workaround before the Yokohama upgrade: Set the system property 'glide.db.kagami_query_registrar.active' to false. If it does not exist, create the system property as follows: Name : glide.db.kagami_query_registrar.active Value : false Type : Boolean (true|false) If you are experiencing the issue after initiating the Yokohama upgrade, please contact ServiceNow Customer Support for assistance with recovery. FAQs: Q: Can admins set up this system property without assistance from the ServiceNow customer support team? A: Yes, admins can configure this system property as outlined in the article. Q: What is the role of this system property, and what is the impact of setting it to false? A: This property allows Glide to monitor query response times and direct queries to either MariaDB Read Replica or Haraka. If set to false, queries will be routed to MariaDB or Haraka read replicas based on the pool ordering assigned to the specific assigned category. Q: I do not see this system property set up on my instance. Do I still need to perform this action? A: Yes, you should still create the system property and set it to false. Q: Will this property be re-enabled in the future? A: We are still working on this. Please subscribe to this article for future updates on this matter.
PRB1928008
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.