4paradigm / 4paradigm/OpenMLDB
`stop job` won't kill the job process in local mode
- 主要语言
- C++
- 星标
- 1.7k
- 派生
- 331
- 平均合并
- 12 天 12 小时
- 30 天内合并 PR
- 1
描述
`stop job` in yarn mode will call `killYarnJob` to stop job. But in local mode or yarn-client mode, it'll only modify the job info table. So the job process will still be running.
https://github.com/4paradigm/OpenMLDB/blob/14a734c2a6f06acd137947eca875074dec3ec61f/java/openmldb-taskmanager/src/main/scala/com/_4paradigm/openmldb/taskmanager/JobInfoManager.scala#L106-L115
- [x] doc
- [ ] a better way, support stop job in local or yarn-client mode?
贡献指南
调研方向
The issue points to JobInfoManager.scala lines 106-115. Examine the stopJob method to see how it handles local and yarn-client modes versus yarn mode. Look for where job processes are spawned and managed in these modes to understand how to send a kill signal. Testing will involve running a job in local mode and attempting to stop it.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java, scala
- 领域
- backend, databases
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 描述清楚
- 新手友好度
- 55/100