[GH-ISSUE #355] storage初始化阶段,没有IBDevice相关日志. IBManager::start调用时,log初始化的操作(initLogging)还没调用 #217

Open
opened 2026-10-26 09:47:16 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @kaede11 on GitHub (Oct 23, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/355

RT
日志的初始化模块,和IBDevice的初始化的顺序是不是反了,即IBDevice初始化时,日志的句柄是不是还没有初始化完成?

`
void initCommonComponents(const ApplicationBase::Config &cfg, const String &serverName, flat::NodeId nodeId) {

initLogging(cfg.log(), serverName);

XLOGF(INFO, "{}", VersionInfo::full());

XLOGF(INFO, "Init waiter singleton {}", fmt::ptr(&net::Waiter::instance()));

auto monitorResult =
monitor::Monitor::start(cfg.monitor(), nodeId == 0 ? "" : fmt::format("Node_{}", nodeId.toUnderType()));

XLOGF_IF(FATAL, !monitorResult, "Start monitor failed: {}", monitorResult.error());

}
`
此外,这个函数中,头两条日志,也时有时无。是否跟folly log是lazy初始化有关?

Originally created by @kaede11 on GitHub (Oct 23, 2025). Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/355 RT 日志的初始化模块,和IBDevice的初始化的顺序是不是反了,即IBDevice初始化时,日志的句柄是不是还没有初始化完成? ` void initCommonComponents(const ApplicationBase::Config &cfg, const String &serverName, flat::NodeId nodeId) { initLogging(cfg.log(), serverName); XLOGF(INFO, "{}", VersionInfo::full()); XLOGF(INFO, "Init waiter singleton {}", fmt::ptr(&net::Waiter::instance())); auto monitorResult = monitor::Monitor::start(cfg.monitor(), nodeId == 0 ? "" : fmt::format("Node_{}", nodeId.toUnderType())); XLOGF_IF(FATAL, !monitorResult, "Start monitor failed: {}", monitorResult.error()); } ` 此外,这个函数中,头两条日志,也时有时无。是否跟folly log是lazy初始化有关?
Author
Owner

@kaede11 commented on GitHub (Oct 24, 2025):

感觉这里有些不清晰,像是个妥协后的方案,即最终IBDevice的相关日志都进入标准输出。

IBDevice依赖log 初始化,才能记录日志。而log 初始化,依赖RDMA获取配置

<!-- gh-comment-id:3440756321 --> @kaede11 commented on GitHub (Oct 24, 2025): 感觉这里有些不清晰,像是个妥协后的方案,即最终IBDevice的相关日志都进入标准输出。 IBDevice依赖log 初始化,才能记录日志。而log 初始化,依赖RDMA获取配置
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/3FS#217
No description provided.