Set minimum level to DEBUG in log4j.properties #201
Merged
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
|
👍 |
merlimat
approved these changes
Feb 23, 2017
merlimat
changed the title
sijie
pushed a commit
to sijie/pulsar
that referenced
this pull request
Mar 4, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Currently you can't print DEBUG level logs even if you change the configuration.
a. Open ./bin/pulsar and change INFO to DEBUG
b. try running ./bin/pulsar standalone -> You will still get only INFO logs
c. Play around with WARN and ERROR levels to understand the problem better
Modifications
Changed the thresholds to DEBUG as per
http://stackoverflow.com/questions/15086818/log4j-debug-messages-not-showing-in-console-despite-isdebugenabled-being-true
Result
Can go upto DEBUG level logs.