-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
We use cold backup for Stash. We need to lock Stash via REST API available since 2.12. And actually use it. Only one annoying thing – Stash on locked mode became to full unaccessable. We need to lock only writes/pushes into Stash, and set instance as readonly.
[BSERV-4799] Allow readonly access on Stash lock mode
Alexey Efimov
added a comment - Since Stash 3.10+ it again cause problem, or maybe we grown up with Git repos. Bu Backup phase now takes ~3 minutes.
Alexey Efimov
added a comment - Since Stash 3.10+ it again cause problem, or maybe we grown up with Git repos. Bu Backup phase now takes ~3 minutes. Alexey Efimov
added a comment - We found workarround to make Stash backup do not show 503 error in git fetch, or HTTP access. As Backup phase take 1-2 seconds, we just use iptables on eth0 to DROP all TCP packets while backup is in progress. After that we clean iptables firewall rules.
On client side it look like temporary 'network problem' and TCP protocol rules allo to send SYN packets again and again, until Stash became accessable.
Alexey Efimov
added a comment - We found workarround to make Stash backup do not show 503 error in git fetch, or HTTP access. As Backup phase take 1-2 seconds, we just use iptables on eth0 to DROP all TCP packets while backup is in progress. After that we clean iptables firewall rules.
On client side it look like temporary 'network problem' and TCP protocol rules allo to send SYN packets again and again, until Stash became accessable. Alexey Efimov
added a comment - Ping! 
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion 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. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Bitbucket Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues.
Kind regards,
Bitbucket Data Center