This repository has been archived by the owner on Feb 8, 2019. It is now read-only.
[Pirk-65] Debug Logging Not Working within Distributed Applications #104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can't seem to get the debug to work even in the local tests (?) Didn't try to troubleshoot more than a couple of minutes. What log settings are you using to test the debug? Are we making the decision to role back to a .properties file instead of a .xml file for the logging properties? |
|
@ellisonanne didn't we test this in distributed mode IIRC when we retired the old LogUtils and moved to slf4j ? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes distributed logging.
In order to do so, we need to use the log4j2-1.2 bridge, and reassert our own log4j properties after hadoop/yarn start. We also need to make sure that our log4j1-style properties file is not named log4j.properties, as that name is eaten by hadoop because hadoop has a file of the same name earlier in the classpath than our properties file.