4paradigm / 4paradigm/OpenMLDB
`stop job` won't kill the job process in local mode
- Vorherrschende Sprache
- C++
- Sterne
- 1.7k
- Forks
- 331
- Ø Merge
- 12 T. 12 Std.
- Gemergte PRs (30 T.)
- 1
Beschreibung
`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?
Beitragsleitfaden
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java, scala
- Bereich
- backend, databases
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 55/100