callback hook for launchers
- 主要语言
- Jupyter Notebook
- 星标
- 2.6k
- 派生
- 1k
- PR 合并指标
- 30 天内没有已合并 PR
描述
It would be great, when possible, to use a callback hook in launchers to signal when a launcher is ready. This could be used to return connection info from the controller to a Cluster object without needing access to the filesystem.
Unfortunately, we can't in general assume the controller or engines *can* call back to the host requesting the launch. So we need to keep the 'watch for files and copy them when they show up' behavior available, and perhaps as the default. However, for the simple Local launcher case, network callbacks should work nicer.
贡献指南
调研方向
Start by tracing how launchers communicate with the controller and Cluster object, especially the Local launcher and the existing filesystem-watch behavior. Define how a readiness callback would return connection information while preserving the filesystem fallback, then verify both paths for launcher startup.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- distributed-systems
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100