Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-26742

Slow Upgrade Due to UserIndexingUpgradeTask introduced in Confluence 4.3.1

      Upgrade takes a long time to complete (12 hours or more) for a Confluence instance with large user base, due to this upgrade task:

      2012-09-27 08:16:54,216 INFO [main] [confluence.upgrade.upgradetask.UserIndexingUpgradeTask] doUpgrade Created 51920 from 71136 missing Personal Information objects.
      2012-09-27 08:17:19,967 INFO [main] [confluence.upgrade.upgradetask.UserIndexingUpgradeTask] doUpgrade Created 51930 from 71136 missing Personal Information objects.
      2012-09-27 08:17:44,767 INFO [main] [confluence.upgrade.upgradetask.UserIndexingUpgradeTask] doUpgrade Created 51940 from 71136 missing Personal Information objects.
      2012-09-27 08:18:06,528 INFO [main] [confluence.upgrade.upgradetask.UserIndexingUpgradeTask] doUpgrade Created 51950 from 71136 missing Personal Information objects.
      2012-09-27 08:18:30,515 INFO [main] [confluence.upgrade.upgradetask.UserIndexingUpgradeTask] doUpgrade Created 51960 from 71136 missing Personal Information objects.
      2012-09-27 08:18:56,407 INFO [main] [confluence.upgrade.upgradetask.UserIndexingUpgradeTask] doUpgrade Created 51970 from 71136 missing Personal Information objects.
      2012-09-27 08:19:19,704 INFO [main] [confluence.upgrade.upgradetask.UserIndexingUpgradeTask] doUpgrade Created 51980 from 71136 missing Personal Information objects.
      

      The amount of time taken for each 10 Personal Information objects grows exponentially, as the upgrade continues.

      Workaround

      For upgrades that take too long to complete (causing production impact), make sure that you have pre-upgrade backups of the Confluence Home Directory and the Confluence Database. Restore those, and upgrade again, but this time, to Confluence 4.3 and not Confluence 4.3.1

          Form Name

            [CONFSERVER-26742] Slow Upgrade Due to UserIndexingUpgradeTask introduced in Confluence 4.3.1

            I encoutered this today during the upgrade from 5.8.14 to 5.10.6

            Deleted Account (Inactive) added a comment - I encoutered this today during the upgrade from 5.8.14 to 5.10.6

            Why am I seeing this error in Confluence 5.5.7?

            Bill Bailey added a comment - Why am I seeing this error in Confluence 5.5.7?

            Hi,

            I am upgrading from 4.2.3 to 5.4.4 and for me it is taking 48+ hrs to upgrade. It is really not acceptable. I understand, I have 1.6 laks users but still not good to wait for 2 days to upgrade with downtime of 2 days.

            It is more painfull, if fail in middle of upgrade which happen for me in production

            Do we have any solution for this.

            Thanks,
            Pawan

            Pawan Upadhyay added a comment - Hi, I am upgrading from 4.2.3 to 5.4.4 and for me it is taking 48+ hrs to upgrade. It is really not acceptable. I understand, I have 1.6 laks users but still not good to wait for 2 days to upgrade with downtime of 2 days. It is more painfull, if fail in middle of upgrade which happen for me in production Do we have any solution for this. Thanks, Pawan

            Dennis added a comment -

            N1 !

            Dennis added a comment - N1 !

            Just did this upgrade, and everything went smoothly. The UserIndexingUpgradeTask is running, but Confluence started up and is accessible first.

            Woot!

            Mark Moskovitz added a comment - Just did this upgrade, and everything went smoothly. The UserIndexingUpgradeTask is running, but Confluence started up and is accessible first. Woot!

            Has anyone attempted this yet on 4.3.2? I'm planning to do it this weekend, but wanted to see if there were any other issues?

            Mark Moskovitz added a comment - Has anyone attempted this yet on 4.3.2? I'm planning to do it this weekend, but wanted to see if there were any other issues?

            Hi Mark,

            I think the best thing to do would be to wait for Confluence 4.3.2 to be released (should be released within a week) and upgrade to that instead. It contains fixes that greatly speed up this particular upgrade task for cases where there are a lot of users to process.

            Niraj Bhawnani added a comment - Hi Mark, I think the best thing to do would be to wait for Confluence 4.3.2 to be released (should be released within a week) and upgrade to that instead. It contains fixes that greatly speed up this particular upgrade task for cases where there are a lot of users to process.

            Niraj - We have restricted LDAP as much as we can, but we still have 20000 users pulling in. How do you disable pulling in all the additional users?

            Thanks!

            Mark Moskovitz added a comment - Niraj - We have restricted LDAP as much as we can, but we still have 20000 users pulling in. How do you disable pulling in all the additional users? Thanks!

            Dennis added a comment -

            Hey,

            thanks for the advice

            Regards
            Dennis

            Dennis added a comment - Hey, thanks for the advice Regards Dennis

            Niraj Bhawnani added a comment - - edited

            Hi John,

            Yes, this was a part of the fix for CONF-6404.

            If those users are not using Confluence, it's probably a good idea to exclude them from the user synchronization by applying an appropriate LDAP filter. This will make the task as well as the periodic user synchronizations run faster. This guide is for Crowd, but applies just as well to Confluence:
            https://confluence.atlassian.com/display/CROWD/Restricting+LDAP+Scope+for+User+and+Group+Search

            That said, we are hard at work on a fix to improve the performance of this upgrade task.

            Hope this helps,
            Niraj.

            Niraj Bhawnani added a comment - - edited Hi John, Yes, this was a part of the fix for CONF-6404 . If those users are not using Confluence, it's probably a good idea to exclude them from the user synchronization by applying an appropriate LDAP filter. This will make the task as well as the periodic user synchronizations run faster. This guide is for Crowd, but applies just as well to Confluence: https://confluence.atlassian.com/display/CROWD/Restricting+LDAP+Scope+for+User+and+Group+Search That said, we are hard at work on a fix to improve the performance of this upgrade task. Hope this helps, Niraj.

              akdominguez Katrina Walser (Inactive)
              fsim Foo Sim (Inactive)
              Affected customers:
              9 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: