Skip to content
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

Install and configure Log4j JUL adapter for Lucene 9.4 #4753

Closed
nknize opened this issue Oct 12, 2022 · 0 comments · Fixed by #4754
Closed

Install and configure Log4j JUL adapter for Lucene 9.4 #4753

nknize opened this issue Oct 12, 2022 · 0 comments · Fixed by #4754
Labels
enhancement Enhancement or improvement to existing feature or request v2.4.0 'Issues and PRs related to version v2.4.0'

Comments

@nknize
Copy link
Collaborator

nknize commented Oct 12, 2022

Described in #4637

Make sure that Opensearch also redirects stuff logged via java.util.logging (JUL) to its own log file, so they do not land in console. This can be done with log4j by adding the log4j-jul 
adapter and install it using a system property in the Bootstrapclasses. I have not checked if this is already done. The reason for this is that Apache Lucene now logs some events 
using java.util.logging since Lucene 9.0. Some of those events are MMapDirectory messages (e.g., when unmapping was not working) or few others like some module system 
settings are incorrect. Logging is very seldom, but for this feature it will definitely log using JUL, so it would be good to make sure Opensearch redirects JUL logging correctly to 
its own loggers. This could be a separate issue!
@nknize nknize added enhancement Enhancement or improvement to existing feature or request v2.4.0 'Issues and PRs related to version v2.4.0' labels Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement or improvement to existing feature or request v2.4.0 'Issues and PRs related to version v2.4.0'
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant