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.