4paradigm / 4paradigm/OpenMLDB

`stop job` won't kill the job process in local mode

Open
#2,799 0 comments 0 reactions 2 assignees Claimed by @vagetablechicken View on GitHub
Dominant language
C++
Stars
1.7k
Forks
331
Avg merge
12d 12h
Merged PRs (30d)
1

Description

`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?

Contributor guide

Open the contributing guide

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, scala
Domain
backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.