JBoss ON 3.2 to 3.3 storage schema upgrade (rhqctl upgrade --storage-schema) takes many hours to complete

Solution Verified - Updated -

Issue

  • Storage node upgrade took several hours to complete
  • Metric data migration will take a week

  • rhq-installer.log shows only 18 metric schedules are being migrated per minute:

    14:37:04,763 INFO  [org.rhq.cassandra.schema.MigrateAggregateMetrics] There are 108560 remaining schedules for the one_hour data migration
14:37:34,774 INFO  [org.rhq.cassandra.schema.MigrateAggregateMetrics] There are 108551 remaining schedules for the one_hour data migration
14:38:04,795 INFO  [org.rhq.cassandra.schema.MigrateAggregateMetrics] There are 108542 remaining schedules for the one_hour data migration
14:38:34,806 INFO  [org.rhq.cassandra.schema.MigrateAggregateMetrics] There are 108533 remaining schedules for the one_hour data migration

  • Storage schema upgrade and metric data migration when upgrading from JBoss ON 3.2 to 3.3 takes too long to process

Environment

  • Red Hat JBoss Operations Network (ON) 3.3
  • Upgrading from JBoss ON 3.2 to 3.3
  • Performing JBoss ON storage node schema upgrade step using command rhqctl upgrade --storage-schema

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.