The problem had to do w/ putting hbck2-1.1.0.jar in the HBase lib directory. This was causing a conflict and moving it out of that directory solved the issue.
On Mon, Mar 7, 2022 at 10:01 AM Claude M <claudemur...@gmail.com> wrote: > Hello, > > I recently upgraded HBase from 1.3.2 to 2.3.5 in an environment and the > logging is not working properly. I've configured the logging to go to > /var/log/hbase/hbase.log yet the log messages are going to syslog. Looking > at the process, it does show the log configuration is set correctly: > > opt/java/oracle/jre1.8.0_271/bin/java -Dproc_master > -XX:OnOutOfMemoryError=kill -9 %p -Djava.net.preferIPv4Stack=true > -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:-ResizePLAB > -XX:MaxGCPauseMillis=100 -XX:ParallelGCThreads=6 -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:/extra/gc.out > -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false > -Dcom.sun.management.jmxremote.authenticate=false -Xmx768m > -Dcom.sun.management.jmxremote.port=10102 -Dhbase.log.dir=/var/log/hbase > -Dhbase.log.file=hbase.log -Dhbase.home.dir=/opt/hbase-2.3.5 > -Dhbase.id.str= -Dhbase.root.logger=INFO,RFA > -Djava.library.path=/opt/hbase-2.3.5/lib/native/Linux-amd64-64 > -Dhbase.security.logger=INFO,RFAS org.apache.hadoop.hbase.master.HMaster > start > > In another environment in which I have HBase 1.3.2 installed, the logging > is going to the correct location /var/log/hbase/hbase.log. What has > changed in HBase 2.3.5 to cause the logging to behave this way? > > > Thanks >
