Add progress logging to LSMTreeIndex build phase#2772
Merged
Conversation
Co-authored-by: robfrank <413587+robfrank@users.noreply.github.com>
Co-authored-by: robfrank <413587+robfrank@users.noreply.github.com>
Contributor
🧪 CI InsightsHere's what we observed from your CI run for 67cc106. 🟢 All jobs passed!But CI Insights is watching 👀 |
Copilot
AI
changed the title
[WIP] Add logging during FULL_TEXT index build phase
Add progress logging to LSMTreeIndex build phase
Nov 10, 2025
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences |
robfrank
approved these changes
Nov 10, 2025
robfrank
added a commit
that referenced
this pull request
Feb 11, 2026
Co-authored-by: Roberto Franchini <ro.franchini@gmail.com> (cherry picked from commit fa1405e)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Index builds on large datasets (millions of records) were completely silent for hours, providing no visibility into progress, performance, or whether the process was stuck.
Changes
LSMTreeIndex.java: Added periodic logging in
build()methodLSMTreeIndexTest.java: Added
testBuildWithLogging()to verify logging behaviorExample output
This brings build phase logging in line with the existing compaction phase logging and enables monitoring of long-running index operations.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
repository.apache.org/usr/lib/jvm/temurin-17-jdk-amd64/bin/java -classpath /home/REDACTED/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1/boot/plexus-classworlds-2.8.0.jar -Dclassworlds.conf=/home/REDACTED/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1/bin/m2.conf -Dmaven.home=/home/REDACTED/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1 -Dlibrary.jansi.path=/home/REDACTED/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/arcadedb/arcadedb org.codehaus.plexus.classworlds.launcher.Launcher -f pom.xml -B -V -e -Dfindbugs.skip -Dcheckstyle.skip -Dpmd.skip=true -Dspotbugs.skip -Denforcer.skip -Dmaven.javadoc.skip -DskipTests -Dmaven.test.skip.exec -Dlicense.skip=true -Drat.skip=true -Dspotless.check.skip=true -s /home/REDACTED/work/arcadedb/.codeql-scratch/dbs/java/working/settings.xml com.github.ferstl:depgraph-maven-plugin:4.0.3-CodeQL:graph -B -DclasspathScopes=compile -DoutputDirectory=/home/REDACTED/work/arcadedb/.codeql-scratch/dbs/java/working/java-standalone-dependency-graph16842588051782640130/${project.groupId}/${project.artifactId} -DgraphFormat=json -Dmaven.ext.class.path=/opt/hostedtoolcache/CodeQL/2.23.3/x64/codeql/java/tools/java-buildless-maven-plugin.jar(dns block)scarf.shnode ./report.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
This section details on the original issue you should resolve
<issue_title>No logging during FULL_TEXT index build phase</issue_title>
<issue_description>## Problem Description
When creating FULL_TEXT indexes on large datasets, the index build process is completely silent for extended periods (hours), making it impossible to determine if:
This is particularly problematic for datasets with millions of records where the build phase can take 5-10+ hours with zero feedback.
Current Behavior
LSM_TREE indexes provide good logging during compaction:
FULL_TEXT indexes are silent during the build phase:
Reproduction
Create a FULL_TEXT index on a large text field with millions of records:
Observe complete silence during the initial build phase (scanning records, tokenizing text, inserting into LSM tree)
Only when compaction starts do logs appear
Root Cause
In
LSMTreeIndex.java(line 626-657), thebuild()method has no logging:For FULL_TEXT indexes, this means:
Impact on Large Datasets
Based on testing with Stack Overflow dataset:
During the 5-7 hour build phase, there is zero indication that work is being done.
Proposed Solution
Add periodic progress logging in
LSMTreeIndex.build():