Loading...
Loading...
An issue exists on Zurich where a large memory footprint can be created when using QueryBuilder queries. This can cause instances to perform slowly, or become outright unresponsive. This issue only affects instances on Zurich (Patch 6 or lower), which are using the "v2" query execution mode. The issue is fixed in Zurich Patch 4 Hot Fix 3b+, Zurich Patch 6 Hotfix 1+, and Zurich Patch 7+.
Pre-conditon: Instance is on Zurich version and the system property 'glide.cmdb.query.execution_mode' has value of v2 or the property is not present at all (default is v2) 1. Open CMDB Query Builder 2. Create one or more queries with multiple connected nodes. More usage with more nodes will cause a bigger memory footprint 3. Run those queries multiple times (these is no specific deterministic times to run it that would cause the problem) Note: The issue is intermittent and not consistently reproducible. Factors include: overall QueryBuilder usage, # of connected nodes on queries, etc
It is recommended to upgrade to a fixed version to resolve this issue. The fix for this issue is included in Zurich Patch 4 Hot Fix 3b+, Zurich Patch 6 Hotfix 1+, and Zurich Patch 7+. If upgrading is not an option, the instance can be configured to run in the pre-Zurich mode, which will resolve the performance issue. To do this: 1) Navigate to System Properties 2) Open the property named "glide.cmdb.query.execution_mode". Out of box, this will have a value of "v2". 3) Update the value to "v1", which will change execution behavior to pre-Zurich. 4) Save the property Please be aware: by applying this workaround, QueryBuilder queries will have a significant reduction in performance. It is strongly advised to revert the workaround (set the value back to "v2") after upgrading to a fixed version. Note: After updating the property, a node restart is required for the workaround to take effect. Node restarts will occur naturally after some time (typically ~1/week), but if a sooner restart is required, please open a Customer Support case. FAQ Q: Where is this issue fixed? A: The fix for this issue is included in Zurich Patch 4 Hot Fix 3b+, Zurich Patch 6 Hotfix 1+, and Zurich Patch 7+. Please upgrade to a fixed version when it becomes available. Q: Can customers the workaround themselves? A: Yes. It is strongly advised to re-enable “v2” mode after upgrading to a fixed version. Q: Is there any downside to applying the workaround? A: Yes, QueryBuilder queries will perform significantly slower. It is strongly recommended to upgrade to a fixed version once it becomes available. Once on a fixed version, ensure that the System Property has a value of "V2". Q: How can I confirm if I am impacted? A: The issue is intermittent and does not have definitive impact criteria. The issue can occur if: 1. Instance is on impacted Zurich version 2. Instance has high QueryBuilder usage 3. System Property "glide.cmdb.query.execution_mode" = "V2" Q: Does this issue affect both production and sub-production instances? A: Yes. Q: Are On-Premise customers impacted? A: If self-hosted customers meet the impact criteria defined above, they can be impacted by this issue.
PRB1977703
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.