Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

BitBucket Data Center on AWS - Why the nodes are placed only in one AZ ? Edited

In this architecture diagram - 

I see that the BitBucket nodes are placed only on one AZ.

Ideally in a HA setup, the nodes should be installed in both Availability Zones ... Am I right?

Can someone help to clarify this?

1 answer

0 votes

Hi Karthikeyan,

The Hazelcast component of Bitbucket Server, which handles node-to-node communication, depends on low latency, and since only having all nodes in the same AZ guarantees low latencies, that's why all nodes are in the same AZ.



Premier Support Engineer


Thanks Chris. Appreciate your help.

Please help me understand ... what role Hazelcast component play in BitBucket server, and why there is a need for an inter-node communication, within a cluster?  


Hi Karthikeyan,


As I said, Hazelcast is used for inter-node communication. That communication is needed for various things, such as caches, synchronization of settings, identifying which node is the master, etc.



Premier Support Engineer


I got it. It now makes sense.  

We are actually interested to host all 3 products - BitBucket, Jira and Cloud Data centers on AWS ... and roll it out enterprise wide.

Wondering whether we can place all the 3 clusters in the same AZ and build it out together. Does it make sense?


I just got a response from our AWS architect. 

Since HA is our prime goal, with zero-down-time, he suggest this:

"Multi AZ have a little impact on the performance as compared to single AZ but it will be very minor (sub-millisecond). However, only extreme-low-latency use cases fit the single-AZ model. Thus, you can consider spanning the nodes across AZs to build a HA solution"

So I would like to double-check with Atlassian, if there is any "risk" involved in splitting the BitBucket nodes across multi-AZ in AWS, to accomplish HA?

Would this cause any Git transaction failure / mis-behavior?



Hi Karthik,

Bitbucket Server will only work in environments where you can guarantee very low latency, which is why we only support environments where all nodes are in the same physical location - and different availability zones typically aren't in the same location.

You can of course try it - chances are it will work, but be prepared to move everything to same AZ after all in case you are experiencing problems.



Premier Support Engineer


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

472 views 10 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you