Bug 1418034
Summary: | Orphaned configuration still left in database | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Filip Brychta <fbrychta> | ||||||
Component: | Database | Assignee: | Ruben Vargas Palma <rvargasp> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Filip Brychta <fbrychta> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | JON 3.3.8 | CC: | jmartine, jshaughn, loleary, mshirley, rvargasp, spinder | ||||||
Target Milestone: | ER01 | Keywords: | Triaged | ||||||
Target Release: | JON 3.3.11 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2018-10-16 17:06:49 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Filip Brychta
2017-01-31 16:34:05 UTC
One thing to note given the description: Clean installation: orphans 499, 488 empty (non-empty 11) EAP6 was imported : orphans 896, 885 empty (non-empty 11) drift definitions : orphans 1832, 1821 empty (non-empty 11) so the non-empty confis is constant after install and 11 doesn't seem like a big deal. The complaint is for empty configs, which are a lot lighter than populated configs, but maybe still a problem. Either way, it's a clue, the issue(s) seems to be around cleaning up empty config. Right. Even though those configs are empty and do not consume a significant amount of space, they are still indexed and result in the database table containing more rows then it should. Although the number of rows per table is unlimited for Oracle and PostgreSQL, the way this data is stored in blocks can result in fragmentation that will add unneeded overhead. I have seen Oracle Database query execution times more then triple when the number of rows in a single table passes 1,000,000. The end result is severe system degradation. In most cases, adding additional resources provides relief and purging unneeded data helps. But if the configuration is empty it adds unnecessary load and if its orphaned, it can't be purged. Moving to ON_QA. JON 3.3.10 CR01 artifacts are available for test from here: http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/166/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip *Note: jon-server-patch-3.3.0.GA.zip maps to CR01 build of jon-server-3.3.0.GA-update-10.zip. Number of orphaned configurations is not growing when following repro steps but there are 2 issues. 1) lots of 'ORA-00060: deadlock detected while waiting for resource' on oracle: Oracle version: oracle-xe-11.2.0-1.0.x86_64 Repro steps: a) install JON 3.3.10.CR01 on oracle db It's not visible on JON 3.3.9. Attaching full server.log and trace logs from oracle. 2) Number of orphaned configurations is still growing when changing configuration of some resource for first time. Second update of configuration for the same resource does not increase number of orphaned configs. This issue might be tracked in new bz since the repro steps are different. This issues is visible on 3.3.9 too. Created attachment 1390214 [details]
complete server log
Created attachment 1390215 [details]
oracle trace logs
commit 7d7005ecdcec4715396637247642140cc4a3300f Author: ruben.vargas <ruben.vp8510> Date: Mon Sep 3 16:51:59 2018 -0500 Try to update configurations instead of replace/delete it Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2930 |