Reply
Highlighted
Explorer
Posts: 17
Registered: ‎01-11-2018

Hive Safety Valve configuration is not applied, HiveConf of name does not exist

[ Edited ]

We had an issue we hive delegation tokens and following suggestion desribed in https://community.cloudera.com/t5/Web-UI-Hue-Beeswax/Potential-misconfiguration-detected-Hue-Hive-Ed... we applied following configuration HS2 and HMS, and to Hive service entirely:
 <property>
    <name>hive.cluster.delegation.key.update-interval</name>
    <value>31536000000</value>
  </property>
  <property>
    <name>hive.cluster.delegation.token.renew-interval</name>
    <value>31536000000</value>
  </property>
  <property>
    <name>hive.cluster.delegation.token.max-lifetime</name>
    <value>31536000000</value>
  </property>
  <property>
 
However after restart we see in the logs:


WARN org.apache.hadoop.hive.conf.HiveConf: [main]: HiveConf of name hive.cluster.delegation.key.update-interval does not exist

WARN org.apache.hadoop.hive.conf.HiveConf: [main]: HiveConf of name hive.cluster.delegation.token.max-lifetime does not exist

WARN org.apache.hadoop.hive.conf.HiveConf: [main]: HiveConf of name hive.cluster.delegation.token.renew-interval does not exist

We are using CDH 5.9.3. Is this parameter still supported in this version? I see these constants exist in the code with default values. However, searching for solution in the Internet I found that there is another parameter hive.conf.validation that checks if 'hive.' variables are accepted: https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties

Default Value: true

Added In: Hive 0.10.0 with HIVE-2848

Enables type checking for registered Hive configurations. As of Hive 0.14.0 (HIVE-7211), a configuration name that starts with "hive." is regarded as a Hive system property. With hive.conf.validation true (default), any attempts to set a configuration property that starts with "hive." which is not registered to the Hive system will throw an exception.

 Is it our case? Or maybe warnings we see in the logs are misleading and actually hive.cluster.delegation.key.* are updated? But we still see in Hlogs MS messages about new tokens being created/cancelled. I'll be thankful for any clarifications.

Cloudera Employee
Posts: 308
Registered: ‎03-23-2015

Re: Hive Safety Valve configuration is not applied, HiveConf of name does not exist

Those settings should be available in Hive.

Can you share the hive-site.xml from both HiveServer2 and HiveMetaStore, as well as the log that contains the error?

Is the error from HiveServer2 or HiveMetaStore logs, or both?
Announcements