You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Am I right, that the configuration option for Namenode HA added with #55 to the SparkFSFetcher class (with has been removed in 28f4025) is not available for the new SparkFetcher class introduced with #162?
@hoesler, yes you are right. Namenode HA support seems to have been lost will migrating to the new fetcher. We need to add HA support for the new Spark Fetcher.
Am I right, that the configuration option for Namenode HA added with #55 to the
SparkFSFetcher
class (with has been removed in 28f4025) is not available for the newSparkFetcher
class introduced with #162?In my case, the SparkLogClient is unable to resolve the hostname for webhdfs (is
null
) whenspark.eventLog.dir=hdfs:///spark-history
, which is the default setting for HDP.The text was updated successfully, but these errors were encountered: