-
Bug
-
Resolution: Low Engagement
-
Medium (View bug fix roadmap)
-
None
-
3.13.2
-
Tomcat 6, MS SQL host. Both systems running on separate Xen VM's
-
3.13
-
Severity 2 - Major
-
Backups that never complete (e.g., sql server hangs and never replies) will leave behind partial backup files that are not identified as corrupted.
I would propose that backup files are created in the "corrupted" folder, and moved out to the proper backup directory only after they have been verified as complete. A corrupted until proven valid mindset if you will...
For some more background on how we've discovered this issue, we've uncovered an issue with the VM's we are running in that there is an abnormally high percentage of packets being dropped. This is causing random queries to hang when using JIRA. The backup system in this case causes a very high number of queries, making it almost guaranteed that the query system will hang during the backup process. I have used remote debugging in Eclipse to confirm that the particular backup thread ends up hung waiting for data from the SQL server (readSocket0).
- is incorporated by
-
JRASERVER-18019 Scheduled backups that fail to complete within a certain time period should provide indications
- Closed
- relates to
-
-
- Closed
-
- was cloned as
-
JDEV-29467 Loading...
[JRASERVER-18018] Failed backups are not identified as corrupted
Philip Peitsch
added a comment - The reason this was initially raised as a Bug was because the presence of the "corrupt" folder in the jira backup directory conveys the ides that JIRA detects and marks corrupted backups as such. This implementation has some flaws, hence the existing functionality has flaws.
To summarise, a new feature or improvement I would class as something that could be done to improve the behaviour... A bug is something that should be done to correct existing behaviour!
Philip Peitsch
added a comment - The reason this was initially raised as a Bug was because the presence of the "corrupt" folder in the jira backup directory conveys the ides that JIRA detects and marks corrupted backups as such. This implementation has some flaws, hence the existing functionality has flaws.
To summarise, a new feature or improvement I would class as something that could be done to improve the behaviour... A bug is something that should be done to correct existing behaviour! 
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center