Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence Upgrade to 5.7 - Attachment Migration Question

Andre Lehmann
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 5, 2015

Hi there,

I'm just testing an Upgrade from our Confluence 5.4 to 5.7.

The 2nd upgradeTask is: resolveAttachmentIdClashes No ID collisions were found between the ATTACHMENTS and CONTENT tables.
For our instance: doMigration Beginning migration of 126497 attachment entries...

It starts with:

13:28:32,437 doMigration Migrated 126 (126 of 126497) attachment entries to the content table in 16s.
13:40:58,633 doMigration Migrated 1582 (1708 of 126497) attachment entries to the content table in 746s.
13:55:04,902 doMigration Migrated 1880 (3588 of 126497) attachment entries to the content table in 846s.
14:13:34,127 doMigration Migrated 2429 (6017 of 126497) attachment entries to the content table in 1109s.
14:35:30,387 doMigration Migrated 2852 (8869 of 126497) attachment entries to the content table in 1316s.

 

If I make a forecast with that values, that means that the attachment migration will take more than 17h!!!

Is that normal? What are your experiences?

There is no cpu/memory load on that server. Attachments are mounted with nfs

 

Kind regards
André

1 answer

1 accepted

1 vote
Answer accepted
Rodrigo Girardi Adami
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 5, 2015

HI Andre,

That's odd. I can see that you have a lot of attachments. Using NFS can be the cause as well. As far as I know, using NFS is not officially supported.

My advise would be to test a Confluence with a local file system storage and check if the issue persists when migrating a fewer number of attachments such as 20 or 30 thousand which should give us an sample rate good enough to measure the total time to accomplish the migration.

Cheers,

Rodrigo

 

Andre Lehmann
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 5, 2015

Hi Rodrigo, thanks for your answer. The whole update finaly finished after 5.5hours. The complete attachment migration took 4.5hours. On our main live-server we don't have nfs anymore so that should be go faster than :-) Now I have to wait until all plugins are marked as compatible or even the most used ones.. Kind regards André

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events