GOBBLIN-836: Expose container logs location via system property to be… #2694
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.
… used in log4j configuration for Gobblin-on-Yarn applications
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA
Expose container logs location via system property to be used in log4j configuration for Gobblin-on-Yarn applications
Description
This task exposes container log directory and container log file name via Java System properties, so that they can be referenced in log4j properties. This in turn allows configuring log rotation of container logs based on size and maximum number of back ups.
Tests
Tested by deploying a Gobblin-on-Yarn application
Commits