4paradigm / 4paradigm/OpenMLDB
`stop job` won't kill the job process in local mode
- Langage dominant
- C++
- Étoiles
- 1.7k
- Forks
- 331
- Merge moyen
- 12 j 12 h
- PR mergées (30 j)
- 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?
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java, scala
- Domaine
- backend, databases
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Clairement spécifiée
- Accessibilité débutants
- 55/100