-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-24373 Implement JvmMetrics in HBase instead of using the one in hadoop #1714
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Copied the code in hadoop to hbase directly with the same package name, and also added some dummy log4j classes in hbase-logging, it basically worked when running UTs. But I'm afraid it may not work when starting a cluster, as in tests, maven will make sure that the classes from the project will be loaded before the dependency jars, but when starting a cluster, there is no guarantee which one will be loaded first... |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
| * Just for making hadoop work without log4j | ||
| */ | ||
| @InterfaceAudience.Private | ||
| public class Logger { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't end up in our client facing artifacts right?
| import org.apache.yetus.audience.InterfaceAudience; | ||
|
|
||
| /** | ||
| * Just for making hadoop work without log4j |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If these are for making Hadoop work, they should be in the hadoop-compat module?
|
Finally I found it really hard to force JVM to load a specific class when there are conflicts, one possible solution is to add a bootstrap jar but it does not work for java11? So the solution in #1708 is that, we still have log4j jar on classpath so hadoop is fine, and make sure that there is no slf4j-log4j12 jar on our classpath so all logs will go to log4j2. PTAL. Thanks. |
No description provided.