-
Notifications
You must be signed in to change notification settings - Fork 28
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
Update log4j configuration to current master #70
Conversation
Specific revision is 0d3cebe812080ea153d124b313fb2c184c7df75b.
{% if verbose_imc_logging_enabled is defined and verbose_imc_logging_enabled %} | ||
logger.verbose_imc.name = org.elasticsearch.indices.IndexingMemoryController | ||
logger.verbose_imc.level = debug | ||
# don't spam console | ||
# logger.verbose_imc.appenderRef.console.ref = console | ||
logger.verbose_imc.appenderRef.rolling.ref = rolling | ||
logger.verbose_imc.appenderRef.rolling_old.ref = rolling_old | ||
logger.verbose_imc.additivity = false | ||
{%- endif %} |
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 block is why we have this file in the first place. However, verbose_imc_logging_enabled
is no longer a thing.
appender.deprecation_rolling.layout.type = ECSJsonLayout | ||
# Intentionally follows a different pattern to above | ||
appender.deprecation_rolling.layout.dataset = deprecation.elasticsearch | ||
appender.deprecation_rolling.filter.rate_limit.type = RateLimitingFilter |
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 is the line that should save us from any future deprecation spam
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.
Thanks! LGTM
In general there is no need for dedicated PR for backports and you can push straight to the branch. Also, the procedure looks fine to me. |
This is a stopgap until elastic/rally#1371 is implemented.
If merged, I'll backport this pull request to the following rally-teams branches:
I don't intend to open pull request for backports (should I?), so please review the procedure below.
For each branch:
However, the main Elasticsearch repo does not have a branch named
7
. Based on my understanding of https://esrally.readthedocs.io/en/stable/track.html#track-repositories-branch-logic, the7
branch could be picked up if we test7.0
, so I'll use the config file from the7.0
Elasticsearch branch.