Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.2.0
-
None
Description
In this issue we have a long running Spark application with secure HBase, which requires HBaseCredentialProvider to get tokens periodically, we specify HBase related jars with --packages, but these dependencies are not added into AM classpath, so when HBaseCredentialProvider tries to initialize HBase connections to get tokens, it will be failed.
Currently because jars specified with --jars or --packages are not added into AM classpath, the only way to extend AM classpath is to use "spark.driver.extraClassPath" which supposed to be used in yarn cluster mode.
So here we should figure out a solution either to put these dependencies to AM classpath or to extend AM classpath with correct configuration.