-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 7.13.0, 7.14.0, 7.19.1
-
Component/s: Server - Installer / Setup
-
1
-
Severity 2 - Major
Issue Summary
When Confluence Data Center is installed and then setup as a clustered deployment, artefacts that are supposed to be created/placed at the instance's shared home directory get placed at the local home instead.
In Confluence 7.13.x
the analytics-logs directory is created at local home (instead of shared home)
the attachments directory is created at both local as well as shared home
actual attachments get placed in the attachments directory at shared home
In Confluence 7.14.x onwards
the analytics-logs directory is created at local home (instead of shared home)
the attachments directory is created only at local home (instead of shared home)
actual attachments get placed in the attachments directory at local home (instead of shared home)
Reproducible on Data Center: yes
Steps to Reproduce
- Download Confluence's installer zip file (7.13.0, 7.14.0, or 7.19.1)
- Unzip the file, create and specify the appropriate local home directory, database etc.
- Start Confluence, enter the setup phase, and choose Clustered installation. Specify values for:
- Cluster name
- Shared home directory (note this value)
- Network interface
- Join configuration
- Complete the installation, create a page, attach a file to the page.
Expected Results
Artefacts such as the attachments, analytics-logs should be created at the shared home directory
Actual Results
Artefacts such as the attachments, analytics-logs get created at the local home directory instead.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- causes
-
CONFSERVER-78928 Confluence Clustered DC Restore from Backup incorrectly reading from <Local Home>/restore folder
-
- Gathering Impact
-
- mentioned in
-
Page Loading...