testing upgrade from 7.13.20 to 8.5.1

[Ravi Shankar]

Hi All,

I am testing confluence upgrade from 7.13.20 to 8.5.1 on test server before doing in production. My upgrade seems stuck for lot of time.

My two questions

1) Is it okay to upgrade from 7.13.20 to 8.5.1 directly?

2) I have 8gb memory and two trials with 2gb and 3gb max heap and it failed ,so increased max heap now to 4gb. Is that okay? Mysql db is around 23GB.

snippet of logs.upgrade going on more than 1hr.

2023-09-22 14:35:32,076 WARN [AtlassianEvent::CustomizableThreadFactory-2] [core.persistence.hibernate.HibernateVersionHistoryDao] getLatestBuildNumber Unable to determine build number from database. If you are upgrading from a Confluence version prior to 7.14.0, this is expected: Unknown column 'FINALIZED' in 'where clause'
2023-09-22 14:35:32,554 INFO [Catalina-utility-1] [confluence.upgrade.impl.DefaultUpgradeManager] beforeUpgrade Generating pre-upgrade recovery file...
2023-09-22 14:35:32,631 INFO [Catalina-utility-1] [confluence.upgrade.recovery.ConfluenceProgressMonitor] begin Starting
2023-09-22 14:35:32,647 INFO [Catalina-utility-1] [confluence.upgrade.recovery.ConfluenceProgressMonitor] logTask Starting DATABASE_INFORMATION
2023-09-22 14:35:32,653 INFO [Catalina-utility-1] [confluence.upgrade.recovery.ConfluenceProgressMonitor] logTask Finishing DATABASE_INFORMATION
2023-09-22 14:35:32,654 INFO [Catalina-utility-1] [confluence.upgrade.recovery.ConfluenceProgressMonitor] logTask Starting TABLE_DEFINITION
2023-09-22 14:35:33,842 INFO [Catalina-utility-1] [confluence.upgrade.recovery.ConfluenceProgressMonitor] logTask Finishing TABLE_DEFINITION
2023-09-22 14:35:33,842 INFO [Catalina-utility-1] [confluence.upgrade.recovery.ConfluenceProgressMonitor] totalNumberOfTables Total number of tables: 207
2023-09-22 14:35:33,843 INFO [Catalina-utility-1] [confluence.upgrade.recovery.ConfluenceProgressMonitor] logTask Starting TABLES_DATA
2023-09-22 14:46:47,306 WARN [Catalina-utility-1] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:\n ->[null]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #1094319232)

[Rilwan Ahmed · Accepted solution]

Hi @Ravi Shankar ,

You need to disable recovery file generation. i.e set system property Dconfluence.upgrade.recovery.file.enabled=false.

More details in https://confluence.atlassian.com/confkb/upgrading-hangs-when-generating-pre-upgrade-recovery-file-590938663.html

[Kian Stack Mumo Systems · Accepted solution]

@Ravi Shankar, Yes. The upgrade path of 7.130->8.5.1 should be fine.

I would just double check to make sure that your database and java versions are compatible with the version you are upgrading to.

If your upgrade failed with 2GB and 3GB heap I would kick it up a couple of GB. Confluence upgrades can take a while if the content of the DB is quite large. I've seen the bodycontent table in particular take a while to complete.