linkedin / linkedin/dr-elephant
SparkFetcher with Namenode HA
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 839
- PR merge metrics
- No merged PRs in 30d
Description
Am I right, that the configuration option for Namenode HA added with #55 to the `SparkFSFetcher` class (with has been removed in 28f4025bbade1be0fc93111ee439859c530a8747) is not available for the new `SparkFetcher` class introduced with #162?
In my case, the SparkLogClient is unable to [resolve the hostname for webhdfs](https://github.com/linkedin/dr-elephant/blob/master/app/com/linkedin/drelephant/spark/fetchers/SparkLogClient.scala#L60) (is `null`) when `spark.eventLog.dir=hdfs:///spark-history`, which is the [default setting for HDP](https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.4/bk_installing_manually_book/content/config-shs-hdfs.html).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the Namenode HA configuration added to SparkFSFetcher in #55 and removed in commit 28f4025bbade1be0fc93111ee439859c530a8747 with the SparkFetcher introduced in #162. Trace SparkLogClient.scala line 60 for the null WebHDFS hostname when spark.eventLog.dir is hdfs:///spark-history; done when the new fetcher handles the needed HA configuration for this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala, spark
- Domain
- data-engineering, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100