Details
-
Suggestion
-
Resolution: Fixed
-
None
Description
When running the Linux Installer to upgrade an instance with a large amount of repository data under $BITBUCKET_HOME, it can spend a very long time doing a recursive chown of all the files in this directory, even if the home directory was already owned by the atlbitbucket user account.
2016-06-09 06:54:52 Downloading Bitbucket latest from https://s3.amazonaws.com/atlassian-software/releases/bitbucket/latest/atlassian-bitbucket-linux-x64.bin 2016-06-09 06:55:26 Installing Bitbucket to /opt/atlassian/bitbucket Starting Installer ... The target home directory is not empty. The installation directory has been set to /opt/atlassian/bitbucket. Extracting files ... 2016-06-09 07:51:57 Installed Bitbucket to /opt/atlassian/bitbucket 2016-06-09 07:51:57 Cleaning up
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 3422 0.0 0.0 11600 2608 ? S 06:55 0:00 bash /opt/atlassian/bitbucket/bin/chown.sh atlbitbucket /var/atlassian/application-data/bitbucket root 3423 1.2 0.0 8224 3520 ? D 06:55 0:09 chown -R -H -L atlbitbucket:atlbitbucket /var/atlassian/application-data/bitbucket
The Linux Installer should skip the chown -R step if the home directory is already owned by atlbitbucket.
Attachments
Issue Links
- causes
-
BSERV-9056 Installer does not copy Elasticsearch configuration into BITBUCKET_HOME/shared/search
- Closed
- is related to
-
BSERV-8921 If your $BITBUCKET_HOME/shared is an NFS mount that squashes root, the Installer cannot copy server.xml
- Closed