-
Suggestion
-
Resolution: Low Engagement
-
None
-
2
-
Summary (Customer's use case)
When a node in a Data Center experiences some errors such as disconnecting to the database, Hazlecast should be able to automatically remove it from the cluster, thus stopping the load balancer from forwarding traffic to the node.
Current outcome
A node remains in the cluster when it looses connection to the database. This results in the load balancer forwarding traffic to the node which results in errors for clients accessing resources from that node
Expected result
Whenever a node within a Data Center cluster encounters errors such as not connecting to the database, it should be disconnected from the cluster.
- mentioned in
-
Page Failed to load
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