Open sivaponting opened 1 year ago
Getting the below error while connecting to remote metastore using kerberos
Need ur suggestion? Anyone please help to resolve. Thanks
Hi @patduin / @abhimanyugupta07 , Does the WD supports DBTokenStore? In my company all the existing Hive metastore is configured with DBTokenStore. For the initial connection it's connecting successfully using Kerberos. For the subsequent connection, it's trying with TOKENs and getting failed with DIGEST-MD5: IO error acquiring password.
I know very little about Kerberos as we don't use it ourselves. Kerberos has been a community contribution perhaps @zzzzming95 can help?
I know very little about Kerberos as we don't use it ourselves.
Kerberos has been a community contribution perhaps @zzzzming95 can help?
Thanks for the reply. @zzzzming95 kindly help on this issue.
@sivaponting
The below config has to be configured both in primary & remote metastores?
The answer is yes. In waggle-dance , we need to use one token to access all metastore (include primary & remote metastores) .
DBTokenStore
mean using mysql to store token , it only share the token who using the same mysql. So it need to change the token sotre to ZKtokenstore.
It should be noted that you need to pay attention to the token storage capacity. By default, the storage limit of a single znode in zk is about 50,000 tokens.
@sivaponting
The below config has to be configured both in primary & remote metastores?
The answer is yes. In waggle-dance , we need to use one token to access all metastore (include primary & remote metastores) .
DBTokenStore
mean using mysql to store token , it only share the token who using the same mysql. So it need to change the token sotre to ZKtokenstore.It should be noted that you need to pay attention to the token storage capacity. By default, the storage limit of a single znode in zk is about 50,000 tokens.
Thanks for ur comment. PROD metastore already using DBTokenStore. Changing it to ZooKeeperTokenStore may not be the right choice. Shall I use the same MySQL database where the PROD metastore is using? Will tht help to resolve the issue?
@sivaponting
Shall I use the same MySQL database where the PROD metastore is using?
Using the same mysql mean you just use the same metastore beacause DBTokenStore
is link with other interfaces(like get_table , get_partition) .Then there is no need to use waggle-dance.
We also switched from DBTokenStore
to ZkTokenStore
, which is a feasible solution.
@sivaponting
Shall I use the same MySQL database where the PROD metastore is using?
Using the same mysql mean you just use the same metastore beacause
DBTokenStore
is link with other interfaces(like get_table , get_partition) .Then there is no need to use waggle-dance.We also switched from
DBTokenStore
toZkTokenStore
, which is a feasible solution.
Sorry I misunderstood. Yes purpose to access to all remote metastores. So we can't keep the token along with it. As u said ZooKeeperTokenStore is the only solution.
Hi @patduin , In my use case, I have some metastores have the same database name. How to handle this in WD?
Please open new discussion for such questions that has nothing todo with original issue. Please see the readme: https://github.com/ExpediaGroup/waggle-dance/blob/main/README.md#database-resolution
Hello, @zzzzming95 . If our primary metastore and federation metastore use different KDCs, how should we configure them in wd?
Do you mean that these configurations are the same in both WD, primary ms, and federation ms.
That is to say, for example,
hive. cluster.delegation. token. store. zookeeper. connectString
, are they all the same?
Are their values are all zk1:2181, zk2:2181, and zk3:2181
.
`
<value>org.apache.hadoop.hive.thrift.ZooKeeperTokenStore</value>
https://github.com/ExpediaGroup/waggle-dance/pull/313 @sivaponting Perhaps my PR can meet your needs.
Pasted the snippet of config from WD doc and have some doubt. The below config has to be configured both in primary & remote metastores?
In addition, all metastores need to use the Zookeeper shared token: