<REPO_NAME> is already indexing, ignoring second indexing request
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
Symptoms
The following appears in the atlassian-bitbucket.log:
1
2
"90.55 "POST /scm/<PROJECT>/<REPO_NAME>/git-receive-pack HTTP/1.1" c.a.s.i.i.i.Changes etIndexingServiceImpl Request for indexing of test-repo received
2012-10-10 16:10:01,868 DEBUG [pool-4-thread-1] <USER> 843x784x1 v7lj91 10.0.90.55 "POST /scm/<PROJECT>/<REPO_NAME>/git-receive-pack HTTP/1.1" c.a.s.i.i.i.Changes etIndexingServiceImpl [<PROJECT>/<REPO_NAME>] is already indexing, ignoring second indexing request" Diagnosis
The new commit does appear in Bitbucket Server but there is no related to the JIRA issue that was mentioned in the Commit Comment. Also on JIRA the Source Tab on the issue does not display any information relating to the git commit.
Cause
Bitbucket Server thinks it's already indexing that repository (when in fact it probably isn't). Because it thinks it's already in the process of indexing, it doesn't start indexing for the new pushes, so the commit information doesn't appear.
Solution
Resolution
Restart the Bitbucket Server instance - ℹ️ the list of what is being indexed, which it tests against to ensure it doesn't concurrently index - is maintained in memory, and will be cleared by the restart.
Then do exactly
one pushto the repository and the logs should show something like this in theLogs:c.a.s.i.i.i.Changes etIndexingServiceImpl Request for indexing of test-repo receivedThe message that says
it's already indexingshould be gone and the integration should be working perfectly.
Was this helpful?