November 20, 2016 5:27:54 PM
> *To:* users@zeppelin.apache.org
> *Subject:* Re: Zepelin problem in HA HDFS
>
> When I failed over HDFS HA nameservice to another namenode, Zeppelin now
> has the same
> error stack *but* for the other namenode, which now became standby.
>
> Not sure if h
problem in HA HDFS
When I failed over HDFS HA nameservice to another namenode, Zeppelin now has
the same
error stack *but* for the other namenode, which now became standby.
Not sure if has something to do with Spark 2.0..
--
Ruslan Dautkhanov
On Sun, Nov 20, 2016 at 4:59 PM, Ruslan Dautkhanov
When I failed over HDFS HA nameservice to another namenode, Zeppelin now
has the same
error stack *but* for the other namenode, which now became standby.
Not sure if has something to do with Spark 2.0..
--
Ruslan Dautkhanov
On Sun, Nov 20, 2016 at 4:59 PM, Ruslan Dautkhanov
wrote:
> Running
Running into issues with Zeppelin in a cluster that runs HA HDFS.
See complete exception stack [1].
"pc1udatahad01.x.y/10.20.32.54:8020...
category READ is not supported in state standby"
Yes, pc1udatahad01 is a current standby, why Spark/HMS/doesn't switch over
to the active one?
hdfs-site.xml tha
