yugabyte/yugabyte-db
View on GitHubNoisy logging from docdb transaction cache lookup loops
Open
#28,908 opened on Oct 10, 2025
good first issuejira-originatedkind/new-featurepriority/low
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