Shared folder aquired by both Datacenter nodes | Bitbucket
Asked by jiqbal.c:

When i run nodes in single mode, bitbucket working fine. When i started both nodes its keep me logout. When i checked the logs, its showing that both nodes are acquiring the shared folder \& home folder. so Can anyone help me please.

here the bitbucket.properties file.

jdbc.driver=org.postgresql.Driver  
jdbc.url=jdbc:postgresql://pgm-l4vi0n  
jdbc.user=bitdb  
jdbc.password=9\*\*\*\*\*  

# Use multicast to discover cluster nodes (recommended).  
hazelcast.network.multicast=false

# If your network does not support multicast, you may uncomment the following lines and substitute  
# the IP addresses of some or all of your cluster nodes. (Not all of the cluster nodes have to be  
# listed here but at least one of them has to be active when a new node joins.)  
hazelcast.network.tcpip=true

hazelcast.network.tcpip.members=10.100.4.\*:5701,10.100.\*:5701

# The following should uniquely identify your cluster on the LAN.  
hazelcast.group.name=admin  
hazelcast.group.password=admin@123

server.proxy-name=bitbucket.\*  
server.proxy-port=443  
server.require-ssl=true  
server.secure=true  

\~


Answers:
author: Aman Shrivastava
body: Hi [@jiqbal.c](/t5/user/viewprofilepage/user-id/5410745)   

The error mentioned below is related to search indexing and is not related to the user logout issue.  

```
2024-02-21 20:08:23,470 WARN [Caesium-1-4] c.a.b.i.s.c.cluster.ClusterJobRunner Job execution failed. Rescheduling. Job key: com.atlassian.bitbucket.internal.search.indexing.jobs.StartupChecksJob Job id: 1eb17c4e-6225-43ec-a742-c5c8cded5bf3
```

<br />

If the LB/Proxy is not set up with sticky sessions, the user could log out abruptly. For a comprehensive guide on setting up Bitbucket clusters, please refer to the [Clustering with Bitbucket](https://confluence.atlassian.com/bitbucketserver/clustering-with-bitbucket-776640164.html) KB article.

The configuration of bitbucket.properties also needs to be corrected.

* Remove the wildcard and define each IP address in hazelcast.network.tcpip.members. Here's a valid example.

  ```
  hazelcast.network.tcpip.members=10.100.4.5:5701,10.100.4.6:5701
  ```

<!-- -->

* Additionally, the configuration of the server.proxy-name doesn't look valid. Please refer to [Securing a reverse proxy using HTTPS](https://confluence.atlassian.com/bitbucketserver/proxy-and-secure-bitbucket-776640099.html#ProxyandsecureBitbucket-SecuringareverseproxyusingHTTPS) to review the bitbucket.properties parameter that is needed when traffic is routed through LB/Proxy and the SSL certificate is set up at LB/Proxy.

<br />

Regards,  
Aman

comments: author: jiqbal.c
body: yes, that was the issue with my LB. I havent set up LoadBalancer with sticky sessions, thats why user could log out abruptly.

I have fixed it that time. Anyways thanks for the detailed answer.


author: jiqbal.c
body: 2024-02-21 20:08:23,470 WARN \[Caesium-1-4\] c.a.b.i.s.c.cluster.ClusterJobRunner Job execution failed. Rescheduling. Job key: com.atlassian.bitbucket.internal.search.indexing.jobs.StartupChecksJob Job id: 1eb17c4e-6225-43ec-a742-c5c8cded5bf3


Tags: bitbucket-data-center

data-center