Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,279
Community Members
 
Community Events
176
Community Groups

Clustering in AWS with bitbucket docker image

Edited

Hi All,

I have some challenges while clustering as i couldnt see all the nodes. Listed my setup details.

1. Ec2-1 (bitbucket image is running) - in private subnet

2. Ec2-2 (bitbucket image is running) - in private subnet

PS: Downloaded the image from https://hub.docker.com/r/atlassian/bitbucket-server/ - v7.3.2

3. Created NFS in aws and mounted the shared directory while starting the container and both the container starts without any issues.

4. Configured load balancer, target group(with sticky session), Bitbucket setup with free license

5. Now i am able to access the bitbucket and if i see clustering, its listing only 1 node (could be ec2-1 or ec2-2) which started first. Not all the nodes.

6. Even in that, i dont see ec2 ip. its listed the docker IP

7. Configuration in bitbucket.properties (commented first 3 lines) and restarted the bitbucket container.

#hazelcast.network.multicast=true

#hazelcast.network.tcpip=true
#hazelcast.network.tcpip.members=172.17.0.2:5701,172.17.0.2:5701

hazelcast.network.aws=true
hazelcast.network.aws.region=us-east-1
hazelcast.network.aws.host.header=
hazelcast.network.aws.security.group.name=SG-EC2-BITBUCKET-PROD
hazelcast.network.aws.iam.role=role-ec2-bitbucket-prod

8. Still i could see only one node and dont see any entry "hazel" in the log "atlassian-bitbucket.log"

9. Added the configuration "ec2:DescribeInstances" as described in https://github.com/hazelcast/hazelcast-aws for ec2. But still same issue.

10. Cloned from https://github.com/hazelcast/hazelcast-aws and generated package "hazelcast-aws.jar" using maven. I tried to upload this into docker image to the location $BITBUCKET_HOME/lib, but it didnt work as expected.

Am i missing something?

Thanks & Regards,
Divakar

1 answer

Any updates on this? I am actually encountering problems setting Bitbucket (Mirror Farm to be specific) via Docker which will be provisioned in AWS. I tried the Hazelcast AWS properties but I still keep on getting 403 errors. Not sure what policy to define for the role.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events