Unable to use code search on Bitbucket Data Center due to c.a.b.s.i.i.IndexingSynchronizationService Unable to establish a connection to Elasticsearch.

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Problem

The code search functionality does not work at all in Bitbucket Server, and the following appears in the atlassian-bitbucket.log file.

1 2 3 4 INFO [Caesium-1-1] c.a.b.s.i.i.jobs.StartupChecksJob Attempting provisioning in startup job INFO [Caesium-1-1] c.a.b.s.i.i.jobs.StartupChecksJob Running startup jobs for search ERROR [Caesium-1-1] c.a.b.s.i.i.IndexingSynchronizationService Unable to establish a connection to Elasticsearch. WARN [Caesium-1-1] c.a.b.s.i.cluster.ClusterJobRunner Job execution failed. Rescheduling. Job key: com.atlassian.bitbucket.search.internal.indexing.jobs.StartupChecksJob Job id: faf44142-3a7f-42c9-b840-4267101ea9b6

Diagnosis

Environment

  • Bitbucket Data Center is installed

  • The bundled Elasticsearch is connected

Cause

This is caused by using the bundled Elasticsearch on Bitbucket Data Center.

Solution

Resolution

It's necessary to install and configure a remote Elasticsearch instance. Please refer to Install and configure a remote Elasticsearch server documentation in order to configure a new remote Elasticsearch instance.

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.