4paradigm / 4paradigm/OpenMLDB
Fail to stop yarn job when kerberos is enabled
- 主要言語
- C++
- スター
- 1.7k
- フォーク
- 331
- 平均マージ
- 12日 12時間
- マージ済み PR(30日)
- 1
説明
**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
}
```
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- hadoop, scala
- 領域
- backend, databases, machine-learning
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 45/100