yugabyte/yugabyte-db
Noisy logging from docdb transaction cache lookup loops
クローズ
#28,908 opened on 2025/10/10
datapath-onboardinggood first issuejira-originatedkind/new-featurepriority/low
Repository metrics
- Stars
- (8,229 個のスター)
- PR merge metrics
- (平均マージ 17d 21h) (30d で 92 merged PRs)
説明
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