Slow Content indexing with Azure SQL after migration to Azure Cloud

Still need help?

The Atlassian Community is here for you.

Ask the community

   

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

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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

Content Indexing in Confluence takes larger amount after migrating the on premises deployment to Azure Cloud.

Environment

Diagnosis

  • atlassian-confluence-index.log: Gaps of seconds in two consecutive output line from the same Indexer thread.

    YYYY-MM-DD HH:MM:12,618 INFO [Indexer: 1] [confluence.internal.index.ConcurrentBatchIndexer] logProgress Re-index progress: 1388222 of 5599305. 24% complete. Memory usage: 6 GB free, 20 GB total
    YYYY-MM-DD HH:MM:15,674 INFO [Indexer: 1] [confluence.internal.index.ConcurrentBatchIndexer] logProgress Re-index progress: 1388382 of 5599305. 24% complete. Memory usage: 5 GB free, 20 GB total

    Upon enabling SQL logging, there is evidence that these gaps are linked to the response time to the SQL queries performed by the Confluence application.

    YYYY-MM-DD HH:MM:13,381 DEBUG [Indexer: 1] [org.hibernate.SQL] logStatement select label0_.LABELID as LABELID1_54_0_, label0_.NAME as NAME2_54_0_, label0_.OWNER as OWNER3_54_0_, label0_.NAMESPACE as NAMESPAC4_54_0_, label0_.CREATIONDATE as CREATION5_54_0_, label0_.LASTMODDATE as LASTMODD6_54_0_ from LABEL label0_ where label0_.LABELID=?
    YYYY-MM-DD HH:MM:13,381 TRACE [Indexer: 1] [type.descriptor.sql.BasicBinder] bind binding parameter [1] as [BIGINT] - [289374327]
    YYYY-MM-DD HH:MM:14,996 TRACE [Indexer: 1] [type.descriptor.sql.BasicExtractor] extract extracted value ([NAME2_54_0_] : [VARCHAR]) - [favourite]

Manual execution of the query from SQL Client, located on the same VM where Confluence is running, help to rule out the Database as suspect of the slow response.

  • TCP Packet capture on Azure SQL Connections, performed when the Content Indexing starts to slow down, shows a large number of TCP retransmissions.
  • VM kernel logs report TCP packets dropped during Content indexing.

Cause

Solution

The following actions can help to improve the Content Indexing slowness:


Last modified on Sep 27, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.