Remove the double logging for open trace file failure from the TraceEvent cache based implementation

描述

貢獻者指南

技術棧

cpp

領域

database

議題類型

refactor

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

2

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

1-3 hours

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

stale

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

clear

前置要求

C++ knowledgeFamiliarity with FoundationDB trace system

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

60

研究方向

The issue requires removing double logging for trace file open failure. The new issue reporting mechanism was introduced in PR #2605, so the old TraceEvent cache based implementation can be removed. Look for the code that handles trace file open failure in the TraceEvent cache and remove the redundant logging. The relevant file is likely in the trace related source files of FoundationDB. The maintainers have provided a clear direction; no further investigation needed.