4paradigm / 4paradigm/OpenMLDB
Fail to stop yarn job when kerberos is enabled
- Vorherrschende Sprache
- C++
- Sterne
- 1.7k
- Forks
- 331
- Ø Merge
- 12 T. 12 Std.
- Gemergte PRs (30 T.)
- 1
Beschreibung
**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
}
```
Beitragsleitfaden
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- hadoop, scala
- Bereich
- backend, databases, machine-learning
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100