BELUGA BEHR created SENTRY-2163: ----------------------------------- Summary: Many Instances of DefaultFS Logging Observed Key: SENTRY-2163 URL: https://issues.apache.org/jira/browse/SENTRY-2163 Project: Sentry Issue Type: Improvement Components: Hive Binding Affects Versions: 1.8.0 Reporter: BELUGA BEHR
https://github.com/apache/sentry/blob/92a183f663c16fc8daf806dcb4a0b264dc811376/sentry-binding/sentry-binding-hive-conf/src/main/java/org/apache/sentry/binding/hive/conf/HiveAuthzConf.java#L180 Seeing many instances of the following in the HiveServer2 log files: {code} 2018-02-26 07:04:57,318 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:04:57,471 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:04:57,488 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:03,430 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:03,447 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:03,582 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:03,599 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:44,203 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:44,221 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:44,364 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:44,381 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:50,178 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:50,200 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:50,374 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:50,391 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:56,715 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:56,768 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 2018-02-26 07:05:56,913 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [HiveServer2-Handler-Pool: Thread-65]: DefaultFS: hdfs://nameservice1 {code} I'm not really sure why the same thread is loading so many instances of this class, but spamming this log message is not helpful. We need to load fewer instances, lower logging to _debug_, remove the logging altogether, or cache the _hiveAuthzSiteURL_ and only log the message once per URL instance instead of once per object instantiation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)