Re: [DISCUSS] Replace log4j with reload4j for branch-2.x

> In the new release version we will provide a new log4j2 format properties file How can we assume users have not changed their log4j properties file? I have done it quite often in production. I can't be the only one. > Even if users have provided their own version of log4j.properties, we have

Re: [DISCUSS] Replace log4j with reload4j for branch-2.x

If eg 2.4.9 binaries could be replaced with 2.5.0 and configuration files won’t need updating, there is no concern. > On Feb 14, 2022, at 7:35 PM, 张铎 wrote: > > The new file format is for log4j2, which has a different name, > log4j2.properties. > > When you have log4j.properties and

Re: [DISCUSS] Replace log4j with reload4j for branch-2.x

The new file format is for log4j2, which has a different name, log4j2.properties. When you have log4j.properties and log4j-1.2-api.jar on the classpath, the log4j1 bridge will take charge and initialize the logging system based on your log4j.properties. This is my point. So in general, if you

[jira] [Created] (HBASE-26755) HBase website generation should show error details on failure

Sean Busbey created HBASE-26755: --- Summary: HBase website generation should show error details on failure Key: HBASE-26755 URL: https://issues.apache.org/jira/browse/HBASE-26755 Project: HBase

[DISCUSS] operator tools, HBase 3 and StoreFileTracking

Hi Folks! While working on adding tools to handle potential FileBased StoreFileTracker issues to HBCK2 (HBASE-26624 ) I ran into multiple problems I'm unsure how to solve. First of all the tools would rely on files not yet available in any of

[jira] [Resolved] (HBASE-26740) migrate ARM specific build

[ https://issues.apache.org/jira/browse/HBASE-26740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-26740. - Resolution: Fixed I changed the job's label from {{arm2}} to {{arm}} after moving it to

[jira] [Created] (HBASE-26756) remove disabled hbase jobs from ci-hadoop

Sean Busbey created HBASE-26756: --- Summary: remove disabled hbase jobs from ci-hadoop Key: HBASE-26756 URL: https://issues.apache.org/jira/browse/HBASE-26756 Project: HBase Issue Type: Sub-task