Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.1.0, 4.1.1, 4.1.3, 4.12.1
-
None
-
2
-
Severity 3 - Minor
-
1
-
Description
Summary
Deleting a repository with a large number of indexed commits (i.e. commits referencing a JIRA issue) results in the following message on Bitbucket Server UI:
Server Unreachable – The server didn't respond. You may retry your request when the server comes back up.
Environment
Bitbucket server installed with the default embedded H2 in-memory database
Steps to Reproduce
- Install Bitbucket server
- Use the default H2 in-memory database
- Create a repository with a large amount of JIRA issues indexed (e.g.: 40,000)
- Delete the repository
Expected Results
The repository gets deleted and a success message is shown on the UI.
Actual Results
The repository is deleted but the following message is displayed on the UI:
Server Unreachable – The server didn't respond. You may retry your request when the server comes back up.
Notes
The problem observed here occurs because the deletion of the repository is slow to happen on the database side.
Because the deletion involves a series of cascade deletes which H2 is taking too long to apply.
Workaround
No workaround is required as the action is performed successfully.
