Hi,
Raised https://issues.apache.org/jira/browse/HBASE-27635 for the same.Some
how setting the ERROR log level at
shell(jar-bootstrap.rb) and log4j2 and log4j is not taking effect and still
see lot of logs. Looking into it.
Thanks,
Rajeshbabu.
On Wed, Feb 8, 2023, 8:54 PM Bryan Beaudreault
I sort of wonder if you have a log4j.properties and log4j2.properties on
the classpath. I think I remember having an issue when both existed, where
I'd see a lot more logs than I expect. Check for a log4j.properties and
remove it.
On Wed, Feb 8, 2023 at 4:51 AM 张铎(Duo Zhang) wrote:
> These are
These are all normal logs for ReadOnlyZkClient, but the problem is we
should not output these logs when running hbase shell.
I'm not a ruby expert but we have this in the entry point of hbase
shell(jar-bootstrap.rb)
# Set logging level to avoid verboseness
hello,
i am using the latest hbase version (2.5.3)
it gets the following logs in hbase shell,
hbase:002:0> 2023-02-08 10:09:08,805 INFO
[ReadOnlyZKClient-127.0.0.1:2181@0x3611153f] zookeeper.ZooKeeper
(ZooKeeper.java:close(1422)) - Session: 0x100e7dbb2a40007 closed
2023-02-08 10:09:08,806 INFO
