Member since
07-06-2022
3
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1102 | 11-29-2023 10:40 PM |
12-08-2023
05:00 AM
Hi @akshaydalvi , I am not sure if you are using Cloudera Manager or not. Please confirm. Make sure your log4j.properties reflects what you are trying to change. You could add "hadoop.security.logger=ERROR,RFAS" line under the log4j safety valve. Be sure that you are using the right RollingAppender name RFA or RFAS. We generally use RFAS for SecurityLogger as shown below snippet. hadoop.security.log.file=SecurityAuth-${user.name}.audit
log4j.appender.RFAS=org.apache.log4j.RollingFileAppender
log4j.appender.RFAS.File=/var/log/hadoop-hdfs/SecurityAuth-${user.name}.audit Here is how we configure the log4j safety valve in Cloudera Manager under HDFS -> Configuration @
... View more
11-29-2023
10:40 PM
Thanks. I was able to resolve it by updating the location in hive meta store. /usr/bin/hive --service metatool -updateLocation new-location old-location
... View more