SGITLOGIN commented on issue #6777:
URL: https://github.com/apache/kyuubi/issues/6777#issuecomment-2434063495
@pan3793
Hello, there is no such problem when using beeline to access hive. Hive will
first access the first namenode internally. If the first namenode is standby,
it will also report the error Operation category READ is not supported in state
standby, and then access the second namenode.
However, the current phenomenon when using kyuubi to query is that when
accessing a cluster with Kerberos authentication through dbever, the first
namenode will be accessed first. If it is found to be in standby state, this
error will be thrown directly without looking for the second namenode. Is this
design method caused by dbever or kyuubi?
HDFS Configurations
<property>
<name>dfs.client.failover.proxy.provider.ha-nn</name>
<value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value>
</property>
I tried using RequestHedgingProxyProvider for the
dfs.client.failover.proxy.provider parameter to no avail.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@kyuubi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@kyuubi.apache.org
For additional commands, e-mail: notifications-h...@kyuubi.apache.org
