Anyone know why bitbucket has 400 TCP connections on a local server? And how I can reduce this?

[Ian Forbes]

I am just starting to use BitBucket.

I have a single install with license individual.

I am using locally using the default DB. 

I should not have ANY outgoing TCP connections.  Yet I see about 10 of them to remote port 52.2.89.223.  I have 390 other TCP connections between the elasticsearch-service.exe and bserv64.exe.

Why the remote connections, and is there a way to control number of TCP threads. Lot of wasted resources.

Thanks in advance.

[Aaron]

Hello Ian,

The Elasticsearch service is what allows for code search for Bitbucket Server. If you don't need it you can run the start-bitbucket.bat with the /no-search so that the bundled Elasticsearch doesn't run. Either that or you can delete the AtlassianBitbucketElasticsearch service, although I wouldn't recommend that, it's a bit of a hassle to get it back. I'm not sure of any other way to tell Bitbucket to limit TCP connections.

Regards,
Aaron Levinson
Dev Tools Support Engineer

[Ian Forbes]

The /no-search did not work.  But I just 'disabled' the service with the service control manager (SCM) thus avoid deleting the service.

Thanks for the idea.

Being a developer, I wonder why the creators didn't just dynamically add / reduce the number of tcp connections dynamically or at least expose a way for small organizations to reduce cpu overhead.  Not really expecting a reply, just more of an observation.

Thanks again.