Bug 1135623
Summary: | Update instructions fail to mention how old metric data can be purged after migration/upgrade | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Larry O'Leary <loleary> |
Component: | Documentation | Assignee: | Jared MORGAN <jmorgan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | high | Docs Contact: | Jared MORGAN <jmorgan> |
Priority: | unspecified | ||
Version: | JON 3.2 | CC: | dlackey, mmurray, snegrea |
Target Milestone: | GA | Keywords: | Documentation |
Target Release: | JON 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
The installation and upgrade instructions for upgrading from JBoss ON <3.2 to JBoss ON >=3.2 did not provide information on how to remove the legacy metric data from the relational database. If users did not perform this step, legacy data persisted in the system, and continued to use many GB of database space. In some instances, database performance was impacted. Multiple changes were made to the Installation Guide to fix this issue. The "About the Upgrade Script" section now has two extra database management parameters described in the "Options for Upgrading" subsection. The "Upgrading the JON Server and Components" procedure has a specific call-out in Step 8 that prompts users to check the "Options for Upgrading" section so they are aware of the new parameters. This content is available for review at access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html-single/Installation_Guide/index.html#upgrade-script
|
Story Points: | --- |
Clone Of: | Environment: |
[Install Guide]
|
|
Last Closed: | 2014-12-11 14:02:44 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: |
Description
Larry O'Leary
2014-08-29 19:51:15 UTC
==Legacy Metric Data== Applicable for upgrading from releases prior to 3.2 (I read this as 3.1.x) to releases later than 3.2 (I read this as 3.2.x and greater). Need to specify that when data migration is run as part of an upgrade, that the user must specify the --delete-data command with the upgrade command. A user can manually run the migration tool and specify the --delete-only argument to remove the metric data. |