Noisy logging from docdb transaction cache lookup loops · yugabyte/yugabyte-db#28908

2025-10-10T20:47:33.000Z

Jira Link: [DB-18631](https://yugabyte.atlassian.net/browse/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](https://github.com/yugabyte/yugabyte-db/blob/master/src/yb/docdb/transaction_status_cache.cc#L146) should be a VLOG(5) (since below logging the results of the lookup is a VLOG(4) Conversely [this](https://github.com/yugabyte/yugabyte-db/blob/master/src/yb/docdb/transaction_status_cache.cc#L156) should be a WARNING not an INFO [DB-18631]: https://yugabyte.atlassian.net/browse/DB-18631?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

(1 comment) (0 reactions) (1 assignee)C (8,229 stars) (1,003 forks)batch import

good first issuejira-originatedkind/new-featurepriority/low

説明

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

コントリビューターガイド

技術スタック: cpp
領域: backenddatabase
Issue 種別: performance
難度: 2
推定時間: under 1 hour
活動状況: blocked
明確さ: clear
前提条件: なし
初心者向け度: 30
調査方針: The issue is in `/src/yb/docdb/transaction status cache.cc`. Lines 146 and 156 need log level adjustments: line 146 should change from WARNING to VLOG(5), and line 156 should change from INFO to WARNING. The fix is straightforward and localized to this file.