4paradigm / 4paradigm/OpenMLDB
Fail to stop yarn job when kerberos is enabled
- Lingua principale
- C++
- Stelle
- 1.7k
- Fork
- 331
- Merge medio
- 12g 12h
- PR unite (30g)
- 1
Descrizione
**Bug Description**
We create the yarn client without initializing with keytab which may be work.
```
def createYarnClient(): YarnClient = {
val config = new Configuration()
config.addResource(new Path(TaskManagerConfig.getHadoopConfDir, "core-site.xml"))
config.addResource(new Path(TaskManagerConfig.getHadoopConfDir, "hdfs-site.xml"))
config.addResource(new Path(TaskManagerConfig.getHadoopConfDir, "yarn-site.xml"))
config.addResource(new Path(TaskManagerConfig.getHadoopConfDir, "mapred-site.xml"))
// Create yarn client
val yarnClient = YarnClient.createYarnClient()
yarnClient.init(config)
yarnClient.start()
yarnClient
}
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Look at the Yarn client creation code in the issue, likely in a Scala file related to task management. Understand how Kerberos authentication works with Yarn. Check the project's configuration loading for keytab files. The fix involves initializing the Yarn client with proper Kerberos credentials. Test by running a Yarn job with Kerberos enabled to verify the stop functionality works.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- hadoop, scala
- Ambito
- backend, databases, machine-learning
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100