yugabyte/yugabyte-db

Noisy logging from docdb transaction cache lookup loops

Closed

#28,908 opened on Oct 10, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)C (1,003 forks)batch import
datapath-onboardinggood first issuejira-originatedkind/new-featurepriority/low

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-18631

The transaction cache lookup code has a tight retry loop on transaction status lookup, but logs during a cache lookup retry at WARNING level which is too high volume for a cache miss. This might actually be logging so aggressively that it impacts performance in extreme cases.

Specifically this should be a VLOG(5) (since below logging the results of the lookup is a VLOG(4) Conversely this should be a WARNING not an INFO

Contributor guide

Research direction
Locate the transaction status cache.cc file, find lines 146 and 156, and change the logging levels as specified: line 146 to VLOG(5) and line 156 to WARNING. Verify the changes with a local build and run relevant tests.
Tech stack
ccpp
Domain
backenddatabase
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60